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 fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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
Purposedifferent
When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.
Complexitydifferent
LowMedium
Timedifferent
30-60 min2-8 h
Participantsdifferent
2-85-12
Formatsame
WorkshopWorkshop
Outputdifferent
Fishbone Diagram, Cause Categories, Investigation BacklogEvent Timeline, Ubiquitous Language, Boundaries, Open Questions
Tagsno overlap
Root causeQualityOperations
Domain-Driven DesignEventsDiscoveryWorkshop
Add more methods

Often compared together

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

Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe