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 Systems Mapping | ![]() Architecture Architecture Decision Record | ![]() Systems Thinking Leverage Points |
|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | 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. |
Complexitydifferent | Medium | Low | High |
Timedifferent | 1-3 h | 15-45 min | Half day |
Participantsdifferent | 3-12 | 1-3 | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | System Map, Dependencies, Leverage Points | ADR File, Decision Log, Rationale | Leverage Map, Action Strategy |
Tagsno overlap | Systems thinkingMappingBoundariesChange | ArchitectureRationaleDocumentationGovernance | Systems thinkingChangeStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






