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 Start Stop Continue |  Knowledge Modeling Concept Mapping |  Knowledge Modeling Knowledge Mapping |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Low | Medium | Medium | Low |
Timedifferent | 30-60 min | 1-2 h | 1-3 h | 45-90 min |
Participantsdifferent | 3-12 | 1-8 | 3-12 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Concept Map, Relationship Labels, Knowledge Gaps | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveImprovementTeamReflection | KnowledgeConceptsMappingSensemaking | KnowledgeMappingRisk | RetrospectiveImprovementExperimentsTeam |