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 a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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.When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.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
HighMediumMediumMedium
Timedifferent
Half day45-90 min2-6 h1-3 h
Participantsdifferent
3-123-82-82-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Leverage Map, Action StrategyImpact Map, Outcome Hypotheses, Delivery OptionsEvent Model, UI Flow, Commands, Read ModelsContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
Systems thinkingChangeStrategy
OutcomesStrategyBehaviorPlanning
EventsBlueprintDomain-Driven DesignBehavior
Domain-Driven DesignBoundariesStrategy
Add more methods