A Better Alternative to Dot Voting

01

What Dot Voting Is and Why Teams Default to It

Dot voting is simple. Write your options on a whiteboard or sticky notes, give everyone three to five dots, and let them place their dots on the options they prefer. The option with the most dots wins. It takes five minutes, requires no special tools, and feels satisfyingly democratic. Every facilitator learns it, every workshop uses it, and most teams never question whether it actually works.

The appeal is understandable. Dot voting is visual — you can see the result forming in real time. It's fast — no lengthy discussions, no complicated scoring rubrics. And it's participatory — everyone gets to vote, which feels fair. Most teams encounter dot voting in their first agile retrospective or design workshop and adopt it as their default group decision method from that point forward.

The problem is that dot voting produces systematically biased results. Not occasionally, not in edge cases, but as a predictable consequence of how the method works. Understanding why requires looking at the specific failure modes.

02

The Failure Modes

The Bandwagon Effect

When people can see where dots are accumulating, they unconsciously adjust their own choices. This is not a theoretical concern — it's one of the most well-documented biases in group decision-making. The first two or three people to place their dots have disproportionate influence over the final result, because everyone who follows can see the emerging pattern. People gravitate toward options that already have dots, partly because they assume others know something they don't, and partly because voting for a winner feels better than wasting a vote on a long shot. In practice, this means the final dot count doesn't reflect what the group actually thinks — it reflects what the first few voters thought, amplified by conformity.

Seniority Bias

When the VP places their dots first, everyone in the room sees it. Even if the vote is nominally anonymous, people know who went first and where the dots landed. Junior team members are unlikely to place all their dots in direct opposition to their manager's choices, even if they genuinely disagree. This isn't cowardice — it's rational behaviour in organisations where career advancement depends on alignment with leadership. The result is that dot voting in hierarchical teams tends to reproduce the senior person's preferences with a thin veneer of democratic participation.

No Intensity

Every dot is equal. But preferences aren't. When someone places a dot on an option, you can't tell whether they mean "This is absolutely critical and I'll be deeply frustrated if we don't do it" or "I needed to put my dots somewhere and this seemed fine." A lukewarm vote counts the same as a passionate one. This means dot voting consistently undervalues items that a minority feels strongly about and overvalues items that everyone thinks are vaguely acceptable. You end up prioritising the least objectionable option rather than the most impactful one.

Strategic Voting

Once people realise that dots are a finite resource, they start gaming. The most common strategy is dumping all your dots on a single option to maximise its chances, even if you have genuine preferences across multiple items. More sophisticated players split their dots strategically — one on their actual top choice, the rest on options they think will pull votes away from things they don't want. The outcome reflects strategic calculation, not genuine preference. And the people who are best at this kind of manoeuvring tend to be the ones who are already most politically savvy — further skewing the result toward those who already have the most influence.

“

Dot voting consistently undervalues items that a minority feels strongly about and overvalues items that everyone thinks are vaguely acceptable.

03

What a Better Method Requires

If dot voting is broken, what would an unbroken alternative look like? A genuinely good group prioritisation method should prevent people from seeing others' choices while they're making their own. It should force genuine trade-offs so that every choice has a real cost. It should capture intensity of preference, not just binary yes/no votes. It should work asynchronously, so you're not limited to whoever can be in the room at the same time. And it should produce a defensible result — something that stands up to scrutiny, not just a count of stickers on a wall.

04

Pairwise Comparison: Why It Fixes Each Problem

No Bandwagon

In a pairwise comparison, everyone votes independently. You see two items at a time and pick the one you think is more important. You can't see what anyone else has chosen, and you can't see the aggregate results until everyone is done. There are no early dots to follow, no emerging patterns to anchor to. Every person's ranking is genuinely their own.

No Seniority Bias

Because comparisons happen privately, on each person's own device, there's no way to know what the VP picked. There's no moment where a senior leader's preference is publicly visible and implicitly pressuring everyone else to conform. The CEO's comparison between items A and B carries exactly the same weight as the newest hire's comparison. This doesn't prevent the CEO from having an opinion — it prevents that opinion from contaminating everyone else's input before they've had a chance to think for themselves.

Captures Intensity

In pairwise comparison, an item that consistently wins against every other item has strong consensus behind it. An item that wins some comparisons and loses others has mixed support. The method naturally distinguishes between "everyone sort of likes this" and "a core group feels passionately about this." You don't need a separate scale or rating — the pattern of wins and losses across all comparisons reveals the shape of the group's preferences with far more nuance than a dot count ever could.

No Strategic Voting

You can't game pairwise comparison the way you can game dot voting, because you only ever see two options at a time. You can't dump all your votes on one item — each comparison is a forced choice between exactly two things. You can't see the running totals, so you don't know which strategic vote would help your preferred outcome. And because the mathematical aggregation considers all pairwise relationships, a single dishonest comparison has minimal effect on the final ranking. The system is robust against exactly the kind of manipulation that dot voting is vulnerable to.

05

Comparison: Dot Voting vs Pairwise Ranking

Criterion	Dot Voting	Pairwise Ranking
Speed	Very fast (2-5 minutes)	Fast (5-10 minutes)
Fairness	Biased by visibility and order	Equal — all input is private
Gaming Resistance	Low — easy to stack votes	High — can't see or influence totals
Intensity Capture	None — every dot is equal	Built in — win patterns show strength
Async Support	Poor — needs everyone in the room	Strong — vote from any device, any time
Group Size	Works for 3-15 people	Works for any group size

06

When Dot Voting Is Still Fine

This isn't a case for never using dot voting. It has legitimate uses, and pretending otherwise would be dishonest. Dot voting works well for quick temperature checks — "Which of these 20 retro items should we discuss first?" It's good for shortlisting a very long list down to a manageable number, because the biases matter less when you're just narrowing the field. And it's fine for genuinely low-stakes decisions where speed matters more than accuracy — picking a restaurant for the team lunch, choosing which icebreaker to do, selecting a colour scheme for the office.

The trouble starts when teams use dot voting for decisions that actually matter. If the outcome will affect strategy, budget, headcount, or what people work on for the next quarter, dot voting's failure modes become real costs. You'll prioritise the wrong things, and you'll do it in a way that feels fair but isn't — which is worse than an openly autocratic decision, because at least then people know who to push back against.

For anything with real consequences, use a method that was designed to handle the complexity of genuine group preferences. Pairwise comparison takes a few minutes longer than dot voting. The results are worth the wait.