View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Dot Estimation |  Knowledge Modeling Concept Mapping |  Engineering Kanban |  Agile NoEstimates |
|---|---|---|---|---|
Purposedifferent | 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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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 estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 5-20 min | 1-2 h | Ongoing | laufend |
Participantsdifferent | 3-20 | 1-8 | 2-12 | 2-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Effort Heatmap, Risk Signals, Discussion Targets | Concept Map, Relationship Labels, Knowledge Gaps | Kanban board, WIP policies, Flow metrics | Throughput Data, Flow Forecast, Slicing Rules |
Tagsno overlap | EstimationEffortRisk | KnowledgeConceptsMappingSensemaking | FlowVisual managementDelivery | EstimationForecastingFlow |