View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Systems Thinking Systems Mapping |  Architecture Architecture Decision Record |  Systems Thinking Leverage Points |
|---|---|---|---|---|
Purposedifferent | 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. | 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 | Medium | Low | High |
Timedifferent | 1-3 h | 1-3 h | 15-45 min | Half day |
Participantsdifferent | 2-8 | 3-12 | 1-3 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | System Map, Dependencies, Leverage Points | ADR File, Decision Log, Rationale | Leverage Map, Action Strategy |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Systems thinkingMappingBoundariesChange | ArchitectureRationaleDocumentationGovernance | Systems thinkingChangeStrategy |