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 illustration for Root Cause Analysis.
Operations
Root Cause Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for Standard Work Analysis.
Operations
Standard Work 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 keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.When the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude.
Complexitydifferent
LowMediumLowMedium
Timedifferent
1-2 h1-4 h15-30 min1-3 h
Participantsdifferent
2-83-82-62-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanRoot cause notes, CountermeasuresStandard Work Sheet, Deviation List, Improved Standard, Training Needs
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
Root causeProblem solvingQualityIncident
Root causeIncidentLeanProblem solving
LeanProcessQuality
Add more methods