Dot Voting & Confidence Voting
The fastest way to prioritize options, gauge team confidence, or close a retrospective. The perfect companion to planning poker for end-to-end agile facilitation.
What Is Dot Voting?
Dot voting is an agile prioritization technique where each participant places a fixed number of dots (or stickers, or upvotes) on the options they prefer. The options with the most dots win. It is one of the simplest, fastest, and most-used facilitation patterns in scrum, kanban, design sprints, and workshop work.
Unlike planning poker, which produces a numeric estimate of effort, dot voting produces an ordering — a ranked list of priorities, ideas, or actions. The two techniques are complementary. Planning poker tells you how big the work is. Dot voting tells you which work to do. A healthy sprint planning meeting uses both: dot voting to pick the stories, planning poker to size them.
Confidence voting is a closely related variant that asks "how confident are you in this decision/commitment/plan?" on a 1–5 scale. It is the default sanity check at the end of a sprint planning meeting. Anyone voting below a 4 explains why, and the team adjusts before committing.
When to Use Dot Voting
Dot voting earns its keep in any moment that needs a fast, fair, low-overhead group decision. The most common settings:
- Retrospectives — picking which improvement actions to commit to next sprint
- Backlog prioritization — ordering a list of feature candidates
- Sprint planning — confidence vote on the proposed sprint commitment
- Brainstorming — clustering and ranking ideas after a generative phase
- Risk identification — ranking which risks the team should mitigate first
- Working agreements — checking whether the team buys in to a proposed norm
Variants You Should Know
"Dot voting" is a family of techniques. The four most-used variants are below — pick whichever fits the question you are trying to answer.
Classic Dot Voting
Each participant gets N stickers (typically 3–5). They place stickers on the items they want to prioritize. Items can receive multiple dots from the same person if you want intensity signals.
BEST FOR: Retrospectives, prioritization, brainstorm clustering
Confidence Voting (1–5)
Each person rates their confidence in a sprint commitment (or any decision) on a 1–5 scale. Reveal simultaneously. Discuss anything below 4. Re-vote.
BEST FOR: Sprint commitment, release readiness, decision check-ins
Roman Voting
Thumbs up = yes, thumbs sideways = neutral, thumbs down = no. Used for fast yes/no consensus checks. The simplest voting variant.
BEST FOR: Quick consensus, decision checkpoints, working agreement votes
Fist of Five
Hold up 0 to 5 fingers. 5 = full support, 0 = strong objection. A more granular variant of Roman voting.
BEST FOR: Decision quality checks, retrospective action item commitment
How to Run a Dot Voting Session
1Define what you are voting on
Be specific. "What should we work on next?" is too vague. "Which of these 12 retrospective improvement actions should we commit to next sprint?" is votable. The clarity of the question determines the quality of the vote.
2Generate the options
Brainstorm, write user stories, list improvement ideas — whatever the format calls for. Get every option visible on the board before any voting starts. No late additions once voting begins.
3Choose the dot count
Common rule: each voter gets N/3 dots, where N is the number of options. So 12 options means 4 dots per person. Adjust based on how concentrated or spread you want the result. Fewer dots forces sharper choices.
4Decide on stacking rules
Can a voter put all their dots on one item, or only one dot per item? Stacking allowed = intensity-weighted. One per item = breadth-of-support signal. Both are valid; choose deliberately.
5Vote (silently and simultaneously)
Like planning poker, the magic is in simultaneous reveal. Block view of dots until everyone has voted, or use stickers placed face-down. Anchoring bias kills dot voting just like it kills planning poker.
6Read the result and act
Top item gets prioritized. Items with zero dots are deprioritized or dropped. Anything close in the middle is worth a brief discussion before deciding. Capture the outcome in your tool of choice immediately — votes get forgotten by next sprint.
Pairing Dot Voting With Planning Poker
The most common production-grade workflow looks like this. The product owner brings a list of candidate stories to sprint planning. The team dot votes to rank them. They take the top-ranked stories one at a time and run them through planning poker for Fibonacci story point estimation. They keep pulling stories into the sprint until they hit their capacity.
At the end of the meeting, the team runs a confidence vote (1–5 scale) on the sprint commitment as a whole. Anyone below a 4 raises concerns. The team adjusts — drops a story, splits one, or accepts the risk explicitly — and re-votes until everyone is at 4 or 5. That is a sprint commitment the team will actually hit.
The combination of dot voting (priority) plus planning poker (effort) plus confidence voting (commitment) is a complete sprint planning toolkit. Each technique handles a different question, and using all three eliminates the most common sprint planning failures: priority churn, effort surprises, and silent dissent.
Common Mistakes to Avoid
Letting people vote in sequence
If voter #1 places dots on the highest item visible, voter #2 anchors. Always reveal simultaneously, exactly like planning poker. In digital tools, hide the count until everyone has submitted.
Voting on options nobody understands
Dot voting amplifies clarity and amplifies confusion. If half the team is unsure what an option means, the result is meaningless. Spend two minutes per option clarifying before voting starts.
Skipping the discussion on close results
When the top three options are within one dot of each other, that is not a result — that is a tie. Discuss why the team is split before forcing a winner.
Treating low confidence votes as personal complaints
A 2 on a confidence vote is data, not drama. The team should welcome low scores because they surface risk early. Punish low-confidence voters and you train the team to vote 5 regardless of how they actually feel.
Voting on too many options
Dot voting on 50 items produces a ranking nobody trusts. Cluster first, eliminate obvious non-starters, then vote on a shortlist of 8–15.
Decide together. Estimate together.
Dot voting picks the stories. Planning poker sizes them. The combination is the most efficient sprint planning workflow your team can run.