Dot Voting

What is dot voting?

Dot voting is a prioritisation technique in which every participant is given a fixed number of votes and spends them on the options they care about most. The options with the most votes rise to the top, and the group gets a ranked list in a few minutes without a long debate. It is also known as multi-voting or dotmocracy, and it comes from workshop facilitation rather than from any single agile framework.

The value is not that voting finds the right answer — it does not. The value is that it collapses a discussion that would take an hour into a ranking that takes three minutes, so the group spends its remaining time discussing the two or three things that matter to most people instead of the one thing raised by whoever spoke first. Scarcity is what makes it work: five votes across twenty options forces people to reveal what they actually prioritise.

When to use dot voting

• Inside a retrospective, to pick which of thirty cards the team will actually discuss.
• Backlog grooming and roadmap sessions, to rank candidates before estimating any of them.
• After a brainstorm, when the group has more ideas than it can pursue and needs to narrow quickly.
• When one or two voices dominate — simultaneous voting gives quiet participants the same weight as the loudest person in the call.
• For large groups, where discussion does not scale but voting does equally well at eight people or forty.
• To check whether a disagreement is real: sometimes two people are arguing about something the other eighteen do not care about at all.

Do not use it to make a decision that needs expertise, carries legal or safety weight, or belongs to a single accountable owner. Dot voting measures how many people care about something, which is not the same as how important it is.

The board explained

The template is a single column that holds every option under consideration. Each card is one option, participants add them at the start of the session, and then everyone spends their votes across the board. A single column is deliberate — the ranking should come from the votes, not from how someone chose to group the cards beforehand.

Write options so that each card is self-contained and unambiguous. "Improve onboarding" and "Rewrite the onboarding docs for the new billing service" attract very different votes, and the vague version tends to win for the wrong reason: people vote for it because it could mean whatever they want it to mean. If two cards overlap, merge them before voting rather than after, since splitting the same idea across two cards buries it below a single clearly-worded alternative.

Example board

A team of twelve ran dot voting at the start of a quarterly planning session to rank engineering investments. Each person had four votes and could stack multiple votes on one card.

The result changed the agenda. Staging and test speed together took more than half the votes, and the framework upgrade — which two people had spent the previous three planning sessions advocating — attracted two votes from those same two people. That did not settle whether the upgrade matters; it settled that it was not going to be decided by group enthusiasm, and it moved to a written proposal with an owner instead of consuming another hour of discussion.

Timing for a team of 5–10

Facilitator prompts

• "We are ranking these by impact on the team over the next quarter, not by how interesting they are."
• "Before we vote: does any card mean two different things to two different people?"
• "Four votes each. You may put all four on one card if you feel that strongly."
• "Vote at the same time, and do not narrate what you are voting for while you do it."
• "There is a clear gap after the top two. Does anyone want to argue that the third one belongs above the line?"
• "This card got one vote from the person who wrote it. Should it go, or does it need a champion outside this meeting?"

Common mistakes

• Voting one at a time, in view of everyone. The first few votes anchor the rest. Everyone should vote in the same window, with results revealed together.
• Too many votes. If people have enough votes to cover most options, nothing is prioritised. One vote per three or four options is the working ratio.
• Voting on unclear cards. Vague options win votes because everyone reads their own meaning into them. Clarify and merge before the first vote is placed.
• Treating the ranking as a decision. A vote count tells you what the group cares about. Whether the top item is the right thing to do is still a judgement, and someone still has to own it.
• Ignoring the shape of the distribution. A clear gap after the top two means a real consensus; votes spread evenly across ten cards means the group does not agree and needs a discussion, not a ranking.
• Letting the loudest person explain each option before voting. Advocacy before the vote turns dot voting into a measure of persuasion, which is the thing it was chosen to avoid.

How to run dot voting in QRetro

1. Create a board from the Dot Voting template.
2. Share the link; participants join in the browser without an account.
3. State the question being prioritised, then give everyone six minutes to add options as cards.
4. Read the cards aloud, clarify wording and merge duplicates before opening voting.
5. Set the number of votes per person — roughly one per four options — and let everyone vote at once.
6. Sort by votes, discuss the top two or three, and record what happens next with an owner for each.