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 | ![]() Domain Modeling Context Map |
|---|---|---|---|
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. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. |
Complexitydifferent | High | Low | Medium |
Timedifferent | Half day | 15-45 min | 1-3 h |
Participantsdifferent | 3-12 | 1-3 | 2-8 |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Leverage Map, Action Strategy | ADR File, Decision Log, Rationale | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | Systems thinkingChangeStrategy | ArchitectureRationaleDocumentationGovernance | Domain-Driven DesignBoundariesStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






