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
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Purposedifferent
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.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.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.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.
Complexitydifferent
MediumHighLowLow
Timedifferent
2-6 hHalf day1-2 h45-90 min
Participantsdifferent
2-83-122-83-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsLeverage Map, Action StrategyDIBB document, Belief list, Bet list, Learning reportForce Field Map, Change Levers, Risk Notes
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
Systems thinkingChangeStrategy
StrategyDecisionAssumptionsHypothesis
ChangeDecisionStrategy
Add more methods