View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Evaporating Cloud |  Engineering Kanban |  Facilitation Dot Estimation |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 60-120 min | Ongoing | 5-20 min | 45-60 min |
Participantsdifferent | 2-8 | 2-12 | 3-20 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Kanban board, WIP policies, Flow metrics | Effort Heatmap, Risk Signals, Discussion Targets | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | FlowVisual managementDelivery | EstimationEffortRisk | AssumptionsRiskExperimentsValidation |