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 Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
LowLowLowHigh
Timedifferent
1-2 h30-60 min30-120 min2-6 h
Participantsdifferent
2-82-82-63-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeFishbone Diagram, Cause Categories, Investigation BacklogObservation Notes, Improvement IdeasFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
Root causeQualityOperations
LeanObservationProcessOperations
RiskQualityOperationsRoot cause
Add more methods