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 |  Team Design Team Cognitive Load Assessment |  Agile Starfish Retrospective |  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 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 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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h Setup, laufend | 60-90 min | 45-90 min | 30-60 min |
Participantsdifferent | 1 | 3-12 | 4-12 | 3-12 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Cognitive Load Profile, Action List | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | KnowledgeProductivityOrganization | TeamComplexityImprovementDiagnosis | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection |