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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
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.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.
Complexitydifferent
MediumLow
Timedifferent
2-6 h20–45 min
Participantsdifferent
2-8Small cross-functional group
Formatdifferent
Workshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsRisk list, Mitigation plan, Assumption log
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
RiskDecisionFailurePlanning
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
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 Failure Scenario Analysis.
Engineering
Failure Scenario Analysis