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 | ![]() Business Strategy Business Model Stress Test | ![]() Systems Thinking Systems Mapping | ![]() 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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. | 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. | 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 | High | Medium | High |
Timedifferent | 1-3 h | Half day | 1-3 h | Half day |
Participantsdifferent | 2-8 | 3-8 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Stress Test Report, Action Plan per Scenario | System Map, Dependencies, Leverage Points | Leverage Map, Action Strategy |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | StrategyBusiness modelRiskDiagnosis | Systems thinkingMappingBoundariesChange | Systems thinkingChangeStrategy |



