View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Balanced Scorecard |  Decision Making Force Field Analysis |  Architecture C4 Model |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | Halber Tag bis mehrere Wochen | 45-90 min | 1-4 h | 1-2 Tage |
Participantsdifferent | 4-12 | 3-12 | 1-5 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Balanced Scorecard, Strategic Measures, Initiative Map | Force Field Map, Change Levers, Risk Notes | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | StrategyMetricsExecution | ChangeDecisionStrategy | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication |