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 arc42 |  Decision Making Assumption Surfacing |  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. | 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. | 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. | 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-2 Tage | 45-90 min | 15-45 min |
Participantsdifferent | 3-12 | 1-4 | 2-8 | 1-3 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Architecture Document, Context View, Runtime View, Deployment View | Assumption List, Critical Assumptions, Learning Plan | ADR File, Decision Log, Rationale |
Tagsno overlap | ChangeDecisionStrategy | ArchitectureDocumentationCommunication | AssumptionsRiskDecisionDiscovery | ArchitectureRationaleDocumentationGovernance |