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 Intervention Mapping | ![]() Architecture C4 Model | ![]() Systems Thinking Leverage Points |
|---|---|---|---|---|
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. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | 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. | 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. |
Complexitydifferent | Low | High | Low | High |
Timedifferent | 15-45 min | 1-5 Tage | 1-4 h | Half day |
Participantsdifferent | 1-3 | 4-12 | 1-5 | 3-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Context Diagram, Container Diagram, Component Diagram | Leverage Map, Action Strategy |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ChangeSystems thinkingCapability | ArchitectureCommunicationVisualization | Systems thinkingChangeStrategy |



