View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Force Field Analysis |  Architecture C4 Model |  Decision Making Assumption Surfacing |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 1-4 h | 45-90 min | 1-2 Tage |
Participantsdifferent | 3-12 | 1-5 | 2-8 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Context Diagram, Container Diagram, Component Diagram | Assumption List, Critical Assumptions, Learning Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ChangeDecisionStrategy | ArchitectureCommunicationVisualization | AssumptionsRiskDecisionDiscovery | ArchitectureDocumentationCommunication |