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 hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
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
Purposedifferent
In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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.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.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.
Complexitydifferent
LowMediumLowMedium
Timedifferent
20–45 min2-6 h1-2 h45-90 min
Participantsdifferent
Small cross-functional group2-82-83-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Risk list, Mitigation plan, Assumption logEvent Model, UI Flow, Commands, Read ModelsDIBB document, Belief list, Bet list, Learning reportImpact Map, Outcome Hypotheses, Delivery Options
Tagsno overlap
RiskDecisionFailurePlanning
EventsBlueprintDomain-Driven DesignBehavior
StrategyDecisionAssumptionsHypothesis
OutcomesStrategyBehaviorPlanning
Add more methods