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 |  Architecture arc42 |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 1-4 h | 1-2 Tage | 15-45 min |
Participantsdifferent | 3-12 | 1-5 | 1-4 | 1-3 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale |
Tagsno overlap | ChangeDecisionStrategy | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance |