Framework · Facilitation techniques · 2 min read
Dot voting
Each person gets 3–5 dots to vote silently, and everyone reveals together to avoid group-think. A fast way to narrow a long list.
- Set up
Show the options and the voting criterion; give 3–5 dots each
- Vote silently
Each person picks privately, without watching the others
- Reveal
Everyone places dots at the same time
- Read the result
Name the top items and what happens to them next
About 10 minutes in total · works with 3–20 people
Use it when
- After an affinity map or a brainstorm, you have 15–40 options and need to narrow them to a few in 10 minutes.
- A senior person is in the room, and you don't want everyone to follow their choice.
- You want to see quickly whether a group already leans one way before a longer discussion.
How to use it
- Show the options and the criterion. Make sure every option is visible and clearly worded. Say what people are voting on: "Which problem hurts users most?" is different from "Which idea is easiest?". Output: a clear list and one voting question. About 2 minutes.
- Give each person 3–5 dots. Use the same number for everyone. Agree if people may put more than one dot on the same option. Output: dots and rules everyone knows.
- Vote silently. Each person picks privately, without watching the others. On paper, people write their picks first; in FigJam or Miro, use the hidden voting feature. Output: private votes. About 3 minutes.
- Reveal simultaneously. Everyone places their dots at the same time, or you reveal the hidden votes at once. Output: a visible heat map of votes. About 1 minute.
- Read the result and decide what's next. Name the top items and check for surprises: "Is anything important missing from the top?" Then use the agreed method to decide, for example a Consent decision or the Approver. Output: a short list and the next step. About 4 minutes.
Worked example
In a 90-minute listening workshop, 7 designers on an internal operations platform have clustered their pain points into 9 themes. The UX lead gives each person 3 dots and asks, "Which problems slow down your design work most?". The votes are hidden in FigJam until everyone is done.
| Theme | Dots |
|---|---|
| Designs reach developers too late in the sprint | 7 |
| No shared components for data tables | 5 |
| Research access to real users is slow | 4 |
| Unclear who approves design decisions | 3 |
| Five other themes | 2 in total |
The lead takes the top three into the next activity (15% Solutions on the top problem) and notes the rest in the workshop summary, so nothing is lost.
Watch out for
- Visible voting. If people see others' dots before voting, they follow the crowd or the most senior person. Vote first, reveal together.
- Treating dots as a decision. A vote does not show cost, risk or evidence. Use it as input and decide with the agreed method.
- Too many or too few dots. One dot each hides second choices; ten each makes everything look popular. 3–5 dots usually works.
- A vague voting question. If some vote for "most important" and others for "easiest", the result means nothing. Say the criterion first.
Template
Write these rules on the board before you start.
DOT VOTING About 10 min
Voting question: Which ___________________________________?
Dots per person: 3 / 4 / 5 More than 1 dot per option? yes / no
1. Read all options (2 min)
2. Choose silently, write your picks down (3 min)
3. Reveal together (1 min)
4. Read the result: top items, surprises (4 min)
This vote is input. The decision is made by: ___________
Next step for the top items:
- SprintJake Knapp, John Zeratsky & Braden KowitzBook · 2016