View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Decision Making Three-Point Estimation |  Operations After-Action Review |  Operations Theory of Constraints |
|---|---|---|---|---|
Purposedifferent | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. | 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. | 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 | Ongoing | 10-30 min je Item | 20-45 min | 2-4 h Analyse, laufend |
Participantsdifferent | 2-12 | 1-8 | 3-12 | 3-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Three-Point Estimate, Risk Range, Assumption Notes | Lessons learned, Action items, Event summary | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | FlowVisual managementDelivery | EstimationUncertaintyForecasting | LearningOperationsImprovement | OperationsConstraintsFlowImprovement |