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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Failure Scenario Analysis.
Engineering
Failure Scenario Analysis
Purposedifferent
For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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 critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage.
Complexitysame
MediumMediumMedium
Timedifferent
30-90 min2-6 h1-3 h
Participantsdifferent
1-62-83-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Decision Tree, Option Map, Assumption ListEvent Model, UI Flow, Commands, Read ModelsFailure Scenarios, Risk Notes, Control Gaps, Test and Response Actions
Tagsno overlap
DecisionTreeOptions
EventsBlueprintDomain-Driven DesignBehavior
FailureResilienceRisk
Add more methods

Often compared together

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

A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
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