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 a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Constraint Analysis.
Decision Making
Constraint 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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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 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
MediumMediumLowLow
Timedifferent
2-6 h45-60 min20–45 min30-90 min
Participantsdifferent
2-82-8Small cross-functional group2-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsAssumption map, Test backlog, Risk rankingRisk list, Mitigation plan, Assumption logConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
AssumptionsRiskExperimentsValidation
RiskDecisionFailurePlanning
ConstraintsDecisionPlanningOptions
Add more methods