methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration of Business Model Stress Test with its method-specific working model.
Business Strategy
Business Model Stress Test
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
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.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.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.
Complexitydifferent
HighHighMediumMedium
Timedifferent
Half dayHalf day1-3 h1-3 h
Participantsdifferent
3-123-82-83-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Leverage Map, Action StrategyStress Test Report, Action Plan per ScenarioContext Map, Integration Patterns, Boundary NotesSystem Map, Dependencies, Leverage Points
Tagsno overlap
Systems thinkingChangeStrategy
StrategyBusiness modelRiskDiagnosis
Domain-Driven DesignBoundariesStrategy
Systems thinkingMappingBoundariesChange
Add more methods