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 PDCA Cycle |  Decision Making Three-Point Estimation |  Delivery Value Stream Mapping |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode. | 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. | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 1 h bis mehrere Wochen | 10-30 min je Item | 1-3 h | Ongoing |
Participantsdifferent | 1-8 | 1-8 | 4-10 | 2-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Three-Point Estimate, Risk Range, Assumption Notes | Current-state map, Future-state map, Bottleneck list | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | Continuous improvementLeanExperiments | EstimationUncertaintyForecasting | LeanFlowWasteDelivery | FlowVisual managementDelivery |