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 PARA Method | ![]() Agile Starfish Retrospective | ![]() Knowledge Modeling Feynman Technique | ![]() Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | 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. | 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 wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h Setup, laufend | 45-90 min | 20-60 min | 30-60 min |
Participantsdifferent | 1 | 4-12 | 1 | 3-12 |
Formatdifferent | Async | Workshop | Async | Workshop |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Starfish Board, Practice Changes, Experiments | Plain-language Explanation, Knowledge Gaps, Study Notes | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | KnowledgeProductivityOrganization | RetrospectiveImprovementExperimentsTeam | LearningKnowledgeUnderstanding | RetrospectiveImprovementTeamReflection |



