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 an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Purposedifferent
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.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.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
LowMediumHighMedium
Timedifferent
45-90 min1-3 hHalf day1-3 h
Participantsdifferent
2-82-83-123-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Assumption List, Critical Assumptions, Learning PlanContext Map, Integration Patterns, Boundary NotesLeverage Map, Action StrategySystem Map, Dependencies, Leverage Points
Tagsno overlap
AssumptionsRiskDecisionDiscovery
Domain-Driven DesignBoundariesStrategy
Systems thinkingChangeStrategy
Systems thinkingMappingBoundariesChange
Add more methods