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 |  Decision Making Assumption Surfacing |  Systems Thinking Leverage Points |  Systems Thinking Systems Mapping |
|---|---|---|---|---|
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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. | 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. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-3 h | 45-90 min | Half day | 1-3 h |
Participantsdifferent | 2-8 | 2-8 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Assumption List, Critical Assumptions, Learning Plan | Leverage Map, Action Strategy | System Map, Dependencies, Leverage Points |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | AssumptionsRiskDecisionDiscovery | Systems thinkingChangeStrategy | Systems thinkingMappingBoundariesChange |