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 Sailboat Retrospective |  Knowledge Modeling Knowledge Mapping |  Agile Starfish 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 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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h Setup, laufend | 45-90 min | 1-3 h | 45-90 min |
Participantsdifferent | 1 | 4-12 | 3-12 | 4-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Sailboat Board, Risks, Improvement Actions | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | KnowledgeProductivityOrganization | RetrospectiveTeamImprovement | KnowledgeMappingRisk | RetrospectiveImprovementExperimentsTeam |