View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Domain Storytelling |  Operations PDCA Cycle |  Operations Kepner-Tregoe |  Operations 5 Whys |
|---|---|---|---|---|
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 an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 1-2 h | 1 h bis mehrere Wochen | 2-8 h | 15-30 min |
Participantsdifferent | 2-8 | 1-8 | 2-8 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Problem Analysis, Decision Analysis, Risk Plan | Root cause notes, Countermeasures |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | Continuous improvementLeanExperiments | Problem solvingRoot causeDecisionOperations | Root causeIncidentLeanProblem solving |