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 | ![]() Agile Planning Poker |
|---|---|---|---|
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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 5-20 min | 1-2 h | 2-5 min je Item |
Participantsdifferent | 3-20 | 1-8 | 3-9 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Effort Heatmap, Risk Signals, Discussion Targets | Concept Map, Relationship Labels, Knowledge Gaps | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | EstimationEffortRisk | KnowledgeConceptsMappingSensemaking | EstimationAgileRelative sizingTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






