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 Starfish Retrospective |  Decision Making Argument Mapping |  Knowledge Modeling Concept Mapping |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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 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 | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | 1-3 h | 1-2 h | 45–75 min |
Participantsdifferent | 4-12 | 1-8 | 1-8 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Argument Map, Evidence Gaps, Decision Rationale | Concept Map, Relationship Labels, Knowledge Gaps | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | SensemakingDecisionRationale | KnowledgeConceptsMappingSensemaking | RetrospectiveLearningReflectionTeam |