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 A3 Problem Solving |  Knowledge Modeling Feynman Technique |  Operations Weekly Review |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | 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. | In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 45-90 min | 20-60 min | 30-60 min | 20-45 min |
Participantsdifferent | 2-5 | 1 | 1 | 3-12 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Plain-language Explanation, Knowledge Gaps, Study Notes | Updated Task System, Weekly Focus, Next Actions | Lessons learned, Action items, Event summary |
Tagsno overlap | LeanProblem solvingCoachingOperations | LearningKnowledgeUnderstanding | ProductivityExecutionPlanning | LearningOperationsImprovement |