View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Process Mapping |  Operations Theory of Constraints |  Knowledge Modeling Domain Storytelling |  Operations A3 Problem Solving |
|---|---|---|---|---|
Purposedifferent | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. | 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 complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-3 h | 2-4 h Analyse, laufend | 1-2 h | 45-90 min |
Participantsdifferent | 3-10 | 3-12 | 2-8 | 2-5 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Constraint Map, Improvement Plan, Flow Metrics | Domain Story, Glossary Notes, Process Narrative | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | ProcessOperationsImprovement | OperationsConstraintsFlowImprovement | KnowledgeDomain-Driven DesignProcess | LeanProblem solvingCoachingOperations |