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 Theory of Constraints |  Knowledge Modeling Knowledge Mapping |  Decision Making Pre-Mortem |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | 2-4 h Analyse, laufend | 1-3 h | 20–45 min | 20-45 min |
Participantsdifferent | 3-12 | 3-12 | Small cross-functional group | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Risk list, Mitigation plan, Assumption log | Lessons learned, Action items, Event summary |
Tagsno overlap | OperationsConstraintsFlowImprovement | KnowledgeMappingRisk | RiskDecisionFailurePlanning | LearningOperationsImprovement |