Dot Voting

When to use

Any time a retro, brainstorm, or planning session has surfaced more options than the team can act on. Skip it for fewer than five items; at that scale, just talk it through. Skip the formal vote when the team already agrees — an unnecessary vote can manufacture disagreement that wasn't there.

How it runs

1. Decide dots-per-person before you start

   Three dots if you want clear winners. Five if you want a long list. Never more — six dots dilute the signal until everything is tied. State the number out loud before the vote opens.

2. Decide stacking up front

   Stacking (multiple dots on one item) produces a clear winner; spreading (one dot per item) produces a flatter ranking. Pick one rule and announce it. Quietly switching rules mid-vote is the most common way teams nuke their own results.

3. Vote silently and simultaneously

   All at once, without watching each other. If the boss votes first, the dots cluster on the boss's pick — the seniority anchor is the failure mode every dot vote should be designed around.

4. Reveal and pick the top one or two

   Highest-dotted item wins. Take the top one or two, not the top five — the point of the vote was to converge. Tie? Quick revote on just the tied items.

Why it works

Silent simultaneous voting kills the seniority anchor that ruins most group decisions. The dot count gives the team an explicit, shared signal of agreement that a discussion alone wouldn't produce — including the disagreement, which is often the more useful output. Three dots forces a real choice; five dots lets people hedge.

Variations

• $100 budget — give everyone an imaginary $100 to allocate across items. Forces stronger preferences than dots.
• Anonymous dot voting via a tool with hidden voting (Miro, Mural). Best variant for teams with strong seniority dynamics.
• Two-pass: first pass with five dots to surface, second pass with three to converge. Slower, but useful for big lists.
• Affinity-then-vote — group similar items first, then dot-vote on the clusters. Stops popular ideas from splitting their own votes.

Facilitator notes

Vote yourself, last, and pick something other than the obvious winner. That's not strategic; it's modelling the diversity of opinion the rest of the team should feel safe expressing. If you can see who's voting in real time, look away or close your eyes — letting the team see you watch the vote is identical to voting first.

Pitfalls

• Switching the stacking rule after people have started voting. Reset and redo if you have to.
• Letting the boss vote first. The dots cluster on the boss's pick and the rest of the vote is theatre.
• Six or more dots per person. Everything ties; the vote produces no signal.
• Dot-voting fewer than five items. The vote is overhead — just talk through them.

Remote tips

In Miro or Mural, use the hidden-voting feature so people can't see each other's dots until the reveal. In a doc, run a 60-second window where everyone adds their emoji at the same time. The simultaneity matters more than the tool — the goal is everyone votes without seeing each other.

Example outputs

• Twelve cards from a retro, three dots per person, eight people. Top item: 7 dots ('staging environment is ours alone'). Second: 4. Pick the top two — you've got a result.
• A scattered vote: 1-2 dots on every item. Read it as a signal: the team didn't have strong preferences. Don't pick a winner; reframe and revote, or take the conversation back upstream.
• A spike on one item: 11 dots on a single Stop card, nothing else above 1. Skip the rest of the agenda; that's the meeting.

FAQ

How many dots per person?

Three for clear winners. Five for a longer list. Never more. Three is the default unless you have a specific reason for five.

Should I allow stacking?

If you want a clear winner, yes — stacking lets people express strong preferences. If you want a fairer ranking, no. Pick one and announce it before the vote opens, and don't change it mid-flight.

Dot voting or $100 budget?

Dot voting is faster and good enough for most retros. The $100 method forces stronger preferences and is worth using when the decision is high-stakes — a roadmap pick, a hiring choice, a tooling decision the team will live with for a year.

Related activities

Recommended use cases