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 Process Mapping |  Operations Getting Things Done |  Operations After-Action Review |
|---|---|---|---|---|
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. | 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. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. | 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 | Low | Medium | Medium | Low |
Timedifferent | 20-60 min | 1-3 h | 1-2 h Setup, laufend | 20-45 min |
Participantsdifferent | 1 | 3-10 | 1 | 3-12 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | Process Map, Handoff List, Improvement Backlog | Action Lists, Project List, Review Routine | Lessons learned, Action items, Event summary |
Tagsno overlap | LearningKnowledgeUnderstanding | ProcessOperationsImprovement | ProductivityPlanningTasksExecution | LearningOperationsImprovement |