View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Leverage Points |  Architecture Architecture Decision Record |  Architecture C4 Model |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | High | Low | Low | Low |
Timedifferent | Half day | 15-45 min | 1-4 h | 45-90 min |
Participantsdifferent | 3-12 | 1-3 | 1-5 | 3-12 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Leverage Map, Action Strategy | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | Systems thinkingChangeStrategy | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | ChangeDecisionStrategy |