View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Strategy Impact Mapping |  Decision Making Force Field Analysis |  Architecture Architecture Decision Record |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | 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. | 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 | Medium | Low | Low | Low |
Timedifferent | 45-90 min | 45-90 min | 15-45 min | 1-2 Tage |
Participantsdifferent | 3-8 | 3-12 | 1-3 | 1-4 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Impact Map, Outcome Hypotheses, Delivery Options | Force Field Map, Change Levers, Risk Notes | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | OutcomesStrategyBehaviorPlanning | ChangeDecisionStrategy | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |