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
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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
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.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.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.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.
Complexitydifferent
LowMediumMediumLow
Timedifferent
20–45 min45-90 min1-3 h30-90 min
Participantsdifferent
Small cross-functional group3-82-82-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Risk list, Mitigation plan, Assumption logImpact Map, Outcome Hypotheses, Delivery OptionsContext Map, Integration Patterns, Boundary NotesConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
RiskDecisionFailurePlanning
OutcomesStrategyBehaviorPlanning
Domain-Driven DesignBoundariesStrategy
ConstraintsDecisionPlanningOptions
Add more methods