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 A3 Problem Solving |  Knowledge Modeling Feynman Technique |  Knowledge Modeling Domain Storytelling |
|---|---|---|---|---|
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 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. | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 45-90 min | 20-60 min | 1-2 h |
Participantsdifferent | 3-10 | 2-5 | 1 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | A3 Report, Action Plan, Root Cause Analysis | Plain-language Explanation, Knowledge Gaps, Study Notes | Domain Story, Glossary Notes, Process Narrative |
Tagsno overlap | ProcessOperationsImprovement | LeanProblem solvingCoachingOperations | LearningKnowledgeUnderstanding | KnowledgeDomain-Driven DesignProcess |