View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Systems Thinking Leverage Points |  Architecture arc42 |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | 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. | 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. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 15-45 min | Half day | 1-2 Tage | 45-90 min |
Participantsdifferent | 1-3 | 3-12 | 1-4 | 3-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Leverage Map, Action Strategy | Architecture Document, Context View, Runtime View, Deployment View | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Systems thinkingChangeStrategy | ArchitectureDocumentationCommunication | ChangeDecisionStrategy |