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 |  Knowledge Modeling Knowledge Mapping |  Product Discovery Assumption Mapping |  Agile Start Stop Continue |
|---|---|---|---|---|
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. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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 | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | 1-3 h | 45-60 min | 30-60 min |
Participantsdifferent | 4-12 | 3-12 | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Assumption map, Test backlog, Risk ranking | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | KnowledgeMappingRisk | AssumptionsRiskExperimentsValidation | RetrospectiveImprovementTeamReflection |