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
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration for Delegation Poker.
Facilitation
Delegation Poker
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Purposedifferent
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.When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice.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.
Complexitydifferent
MediumHighLowMedium
Timedifferent
1-3 hHalf day45-90 min1-3 h
Participantsdifferent
3-123-123-102-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
System Map, Dependencies, Leverage PointsLeverage Map, Action StrategyDelegation Board, Decision Boundaries, Role AgreementsContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
Systems thinkingMappingBoundariesChange
Systems thinkingChangeStrategy
AutonomyRolesTeam
Domain-Driven DesignBoundariesStrategy
Add more methods