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 |  Decision Making Argument Mapping |  Architecture Architecture Decision Record |  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. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. | 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 | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 1-3 h | 15-45 min | 1-2 Tage |
Participantsdifferent | 3-12 | 1-8 | 1-3 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Argument Map, Evidence Gaps, Decision Rationale | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ChangeDecisionStrategy | SensemakingDecisionRationale | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |