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 |  Operations Getting Things Done |  Agile Starfish Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|---|
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. | 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. | 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 sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h Setup, laufend | 1-2 h Setup, laufend | 45-90 min | 45–75 min |
Participantsdifferent | 1 | 1 | 4-12 | Team members involved |
Formatdifferent | Async | Async | Workshop | Workshop |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Action Lists, Project List, Review Routine | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | KnowledgeProductivityOrganization | ProductivityPlanningTasksExecution | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |