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 |  Agile Mad Sad Glad |  Operations After-Action Review |  Agile Start Stop Continue |
|---|---|---|---|---|
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. | When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. | 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. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 20-60 min | 30-60 min | 20-45 min | 30-60 min |
Participantsdifferent | 1 | 3-10 | 3-12 | 3-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | Emotion Board, Themes, Action Items | Lessons learned, Action items, Event summary | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | LearningKnowledgeUnderstanding | RetrospectiveTeamReflection | LearningOperationsImprovement | RetrospectiveImprovementTeamReflection |