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
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Paper illustration for Evaporating Cloud.
Systems Thinking
Evaporating Cloud
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
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 domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict.DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report.
Complexitydifferent
HighMediumMediumLow
Timedifferent
Half day2-8 h60-120 min1-2 h
Participantsdifferent
3-125-122-82-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Leverage Map, Action StrategyEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsConflict Cloud, Assumption List, Breakthrough Ideas, Next ExperimentsDIBB document, Belief list, Bet list, Learning report
Tagsno overlap
Systems thinkingChangeStrategy
Domain-Driven DesignEventsDiscoveryWorkshop
Theory of ConstraintsAssumptionsSystems thinking
StrategyDecisionAssumptionsHypothesis
Add more methods