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 |  Knowledge Modeling IBIS |  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. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 1-3 h | 1-2 Tage | 15-45 min |
Participantsdifferent | 3-12 | 2-8 | 1-4 | 1-3 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Issue Map, Positions, Argument Notes | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale |
Tagsno overlap | ChangeDecisionStrategy | RationaleKnowledgeDecision | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance |