What needs to be finished first
Participants are familiar with the Dot Voting principle or are introduced in 2 minutes; point meaning is clarified in advance (effort, risk, or uncertainty).
What needs to be ready before start
Whiteboard or Miro board with all items visible; sticky dots (physical) or voting tool (Mentimeter, Miro, FigJam); point meaning definition visible on the wall; timer.
One facilitator who defines point meaning and evaluates heatmap; 3-20 participants with context on the items; one scribe for cluster notes and follow-up tasks.
List of items as cards or stickies; point meaning definition (for example, 'points for effort, more points = more effort'); number of points per person (typically 5-10).
5-20 min
Place items in rows or groups on the wall. Make point meaning visible as a banner: 'Place points on items you assess as [effortful/risky/unclear]'. Set points per person. Enforce silence during distribution.
The one question this method answers
Which items does the group indicate as especially effortful, risky, or unclear, and where are clusters or outliers that need discussion or discovery?
Marker: Minute
| Step | Duration | Action | Hint |
|---|---|---|---|
10-3 min: Clarify point meaning | 3 min | Facilitator explains: points represent one concrete dimension (effort, risk, uncertainty, not preference). Announce points per person. Clarify questions. | If meaning is unclear, participants mix dimensions. It is better to run two rounds with different colors (red=risk, blue=effort) than one mixed-meaning round. |
23-8 min: Distribute points | 5 min | Everyone distributes their points simultaneously and silently. Points may be stacked (multiple on one item) or spread across items depending on the rule. | If someone places points before everyone else, this influences the group when everyone distributes simultaneously. For online boards: use hidden voting mode if available. |
38-13 min: Interpret heatmap | 5 min | Order items by point count. Identify top-3 heat points and clusters. Mark items with 0 points as 'unestimated.' | Top items are discussion candidates, not automatically real risks. A high point count is a signal of perception, not objective reality. |
413-20 min: Discuss top items | 7 min | Briefly for each top item: who assigned points and why. Capture assumptions or concrete risks. Name follow-up action (spike, splitting, additional discovery). | If discussion goes beyond 5 minutes per item, the method is over-stretched. Dot Estimation is triage, not deep analysis. Go deeper with Planning Poker or Three-Point afterward. |
What comes out at the end
Heatmap as photo or board export plus a markdown list with top items, point count, identified assumptions or risks, and follow-up action (spike, splitting, discovery).
Archive heatmap as dated snapshot. For repeated triage, create a new heatmap as a new version; do not overwrite. Move follow-up actions into backlog with status.
Compact working template for Dot Estimation with context, input, output artifacts, and next step.
What is this method used for?
Which question should be answered at the end?
Which data, observations, or materials are available?
Owner, date, success signal.
Concrete filled scenario, fictional example
Concrete filled scenario, fictional example
Point meaning: Effort. 5 points per person. 8 participants (engineering and product).
Heatmap top-5
Items with 0 points: 4 items, all from the UI polish area. Expected, no action needed.
Follow-up actions
Recognize symptoms and steer against them
Some participants place points for effort, others for preference or importance, resulting in mixed heatmap.
Repeat meaning three times before distribution and write it on the wall. If heatmap is unclear, start again with a clear definition. One dimension per round.
Stakeholder reads point count as effort value ('14 points = 14 days').
Communicate clearly: points are team perception, not effort value. Top items are estimated in a dedicated sizing method (Planning Poker, Three-Point).
Everyone has 2 points, all land on the three most prominent items, heatmap shows only knowns.
5-10 points per person are typical. Adjust count to item volume (rule of thumb: 25-50% of item count). Too few points create echo effects.
Early participants place points and others see points and follow the trend.
All participants place points at the same time (on facilitator signal) or use hidden voting in the tool. Sequential placement produces bandwagon effects, not honest estimation.
Heatmap is created, hangs in the wiki, and no follow-up tasks are triggered.
Before workshop end, name an owner and due date for each top item. A heatmap without follow-up actions wastes energy. At least three actions with dates before workshop close.
Done signals checkable in under a minute
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.