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 Bottleneck Analysis |  Knowledge Modeling Knowledge Mapping |  Agile Starfish Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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 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 | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 1-3 h | 45-90 min | 45–75 min |
Participantsdifferent | 3-8 | 3-12 | 4-12 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | FlowMeasurementConstraints | KnowledgeMappingRisk | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |