View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Sailboat Retrospective |  Knowledge Modeling Concept Mapping |  Decision Making Argument Mapping |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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 | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | 1-2 h | 1-3 h | 45-90 min |
Participantsdifferent | 4-12 | 1-8 | 1-8 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Concept Map, Relationship Labels, Knowledge Gaps | Argument Map, Evidence Gaps, Decision Rationale | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveTeamImprovement | KnowledgeConceptsMappingSensemaking | SensemakingDecisionRationale | RetrospectiveImprovementExperimentsTeam |