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 |  Product Discovery Assumption Mapping |  Facilitation Dot Estimation |  Growth A/B Testing |
|---|---|---|---|---|
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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | Ongoing | 45-60 min | 5-20 min | 1-4 Wochen |
Participantsdifferent | 2-12 | 2-8 | 3-20 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Assumption map, Test backlog, Risk ranking | Effort Heatmap, Risk Signals, Discussion Targets | Experiment results, Decision log, Learning summary |
Tagsno overlap | FlowVisual managementDelivery | AssumptionsRiskExperimentsValidation | EstimationEffortRisk | ExperimentsGrowthAnalyticsValidation |