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 Knowledge Mapping |  Operations Bottleneck Analysis |  Agile Sailboat Retrospective |  Operations Theory of Constraints |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-3 h | 1-3 h | 45-90 min | 2-4 h Analyse, laufend |
Participantsdifferent | 3-12 | 3-8 | 4-12 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Sailboat Board, Risks, Improvement Actions | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | KnowledgeMappingRisk | FlowMeasurementConstraints | RetrospectiveTeamImprovement | OperationsConstraintsFlowImprovement |