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
Paper illustration for Bottleneck Analysis.
Operations
Bottleneck Analysis
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 a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput.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
1-3 h2-6 h1-3 h
Participantsdifferent
3-82-83-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Bottleneck Map, Flow Metrics, Improvement Options, Follow-up MeasuresEvent Model, UI Flow, Commands, Read ModelsFailure Scenarios, Risk Notes, Control Gaps, Test and Response Actions
Tagsno overlap
FlowMeasurementConstraints
EventsBlueprintDomain-Driven DesignBehavior
FailureResilienceRisk
Add more methods

Often compared together

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

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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Theory of Constraints.
Operations
Theory of Constraints
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping