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 Feynman Technique | ![]() Operations Runbook | ![]() Operations A3 Problem Solving | ![]() Operations Gemba Walk |
|---|---|---|---|---|
Purposedifferent | 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. | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | 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. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 20-60 min | 20-60 min | 45-90 min | 30-120 min |
Participantsdifferent | 1 | 1-4 | 2-5 | 2-6 |
Formatdifferent | Async | Async | Workshop + async | Workshop |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | Runbook, Checklist, Escalation Path | A3 Report, Action Plan, Root Cause Analysis | Observation Notes, Improvement Ideas |
Tagsno overlap | LearningKnowledgeUnderstanding | OperationsReliabilityDocumentation | LeanProblem solvingCoachingOperations | LeanObservationProcessOperations |



