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 |  Systems Thinking Evaporating Cloud |  Knowledge Modeling Teach-back |  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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations. | 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 | Low | Low |
Timedifferent | 20-60 min | 60-120 min | 5-20 min | 20-45 min |
Participantsdifferent | 1 | 2-8 | 2-8 | 3-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Understanding Check, Clarification Notes, Learning Gaps | Lessons learned, Action items, Event summary |
Tagsno overlap | LearningKnowledgeUnderstanding | Theory of ConstraintsAssumptionsSystems thinking | LearningUnderstandingCommunication | LearningOperationsImprovement |