View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Accountability Ladder |  Knowledge Modeling Knowledge Mapping |  Agile Starfish Retrospective |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 20-45 min | 1-3 h | 45-90 min | 45-60 min |
Participantsdifferent | 1-8 | 3-12 | 4-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Ownership Reflection, Action Commitment, Coaching Notes | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Starfish Board, Practice Changes, Experiments | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ResponsibilityLeadershipTeam | KnowledgeMappingRisk | RetrospectiveImprovementExperimentsTeam | AssumptionsRiskExperimentsValidation |