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 Concept Mapping |  Agile Starfish Retrospective |  Knowledge Modeling Knowledge Mapping |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-2 h | 45-90 min | 1-3 h | 45-60 min |
Participantsdifferent | 1-8 | 4-12 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Starfish Board, Practice Changes, Experiments | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | RetrospectiveImprovementExperimentsTeam | KnowledgeMappingRisk | AssumptionsRiskExperimentsValidation |