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 |  Knowledge Modeling PARA Method |  Agile Starfish Retrospective |  Agile Sailboat Retrospective |
|---|---|---|---|---|
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 PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 20-60 min | 1-3 h Setup, laufend | 45-90 min | 45-90 min |
Participantsdifferent | 1 | 1 | 4-12 | 4-12 |
Formatdifferent | Async | Async | Workshop | Workshop |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | PARA Structure, Project Notes, Knowledge Archive | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | LearningKnowledgeUnderstanding | KnowledgeProductivityOrganization | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement |