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
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 Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree 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.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 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 problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.
Complexitydifferent
LowLowMediumMedium
Timedifferent
1-2 h15-30 min1-4 h1-3 h
Participantsdifferent
2-82-63-82-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeRoot cause notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanCause Tree, Evidence Notes, Countermeasures
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
Root causeIncidentLeanProblem solving
Root causeProblem solvingQualityIncident
Root causeTreeIncidentQuality
Add more methods