View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Three-Point Estimation | ![]() Systems Thinking Evaporating Cloud | ![]() Engineering Kanban |
|---|---|---|---|
Purposedifferent | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 10-30 min je Item | 60-120 min | Ongoing |
Participantsdifferent | 1-8 | 2-8 | 2-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Three-Point Estimate, Risk Range, Assumption Notes | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | EstimationUncertaintyForecasting | Theory of ConstraintsAssumptionsSystems thinking | FlowVisual managementDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






