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 |  Team Design Team Cognitive Load Assessment |  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. | 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 juggles too many domains, systems, or handoffs, it measures mental overload as an organizational problem. It clarifies responsibility, interaction, and load between teams. The result is captured as a cognitive-load profile and action list. | 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 | Low | Medium | Low |
Timedifferent | 1-3 h Setup, laufend | 45-90 min | 60-90 min | 45–75 min |
Participantsdifferent | 1 | 4-12 | 3-12 | Team members involved |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Starfish Board, Practice Changes, Experiments | Cognitive Load Profile, Action List | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | KnowledgeProductivityOrganization | RetrospectiveImprovementExperimentsTeam | TeamComplexityImprovementDiagnosis | RetrospectiveLearningReflectionTeam |