Your Team Priorities Are Broken Because the Loudest Voice Always Wins

I once sat through a retrospective where a senior architect -- let's call him Dave -- spent forty-five minutes explaining why the team's number one priority should be migrating to a new message broker. Nobody asked. Nobody had put it on the board. He just started talking, and by the time the facilitator nervously asked the group to vote on priorities, every single hand in the room went up for Dave's item first. Was it genuinely the most important thing? Almost certainly not. Three other items on the board -- items people had actually spent time writing down -- quietly died without a single vote.

That's not a retrospective. That's a Dave show with a whiteboard as a backdrop.

And here's the uncomfortable truth: your team is probably doing the same thing, just with a different Dave.

The Problem Has a Name (Several, Actually)

What happened in that room is so common it has been formally studied and named. The most famous version is the HIPPO effect -- the Highest Paid Person's Opinion. The idea is simple and kind of depressing: when someone with obvious seniority or authority speaks first, everyone else's thinking collapses in their direction like wet cardboard. It doesn't matter how good your other ideas are. The gravitational pull of rank is genuinely hard to fight when you're sitting across a table from someone who controls your performance review.

But even without a formal hierarchy, two other forces make most team voting exercises basically useless: anchoring and bandwagoning.

Anchoring is what happens when someone names a number, a priority, or a direction, and then everyone else's judgment gets quietly distorted around that anchor point. The first person who says "I think this authentication bug is the most critical thing" has just reset everyone else's internal scale. Even if you disagree, you're now arguing against an anchor rather than making a fresh judgment.

Bandwagoning is the ancient art of noticing which way the wind is blowing and standing exactly there. Nobody wants to be the dissenting vote. Nobody wants to argue. So people vote for whatever seems popular, and the whole team walks out thinking they've reached genuine consensus when really they've just reached social comfort.

These aren't character flaws. They're deeply human tendencies that show up in boardrooms, sprint retros, and anywhere else groups try to make collective decisions under mild social pressure. The question is what you actually do about it.

Write First, Vote Later -- The Order Matters More Than You Think

The single most underrated fix is embarrassingly simple: make people commit their thoughts before they can see anyone else's.

This is sometimes called brainwriting, but a more practical framing is the "write first" approach. Before any grouping, before any discussion, before anyone can say a single word about what they think is important -- everyone writes their items down privately. In a good retrospective tool, those cards are hidden from other participants until the facilitator decides to reveal them.

This sounds like a small procedural thing. It isn't. When you write your priority down before Dave has a chance to evangelize his message broker migration, you're making an independent judgment. When the cards finally get revealed and grouped, the facilitator can suddenly see the actual distribution of concern across the team -- not the post-Dave, post-anchoring, socially adjusted version of it.

Tools like Parabol, Neatro, and Echometer have built this into their core workflow. Cards stay hidden, votes are anonymous, and the results show up without anyone being able to triangulate who voted for what. That last part matters more than most facilitators realize. If your team members can figure out that the quiet backend dev voted against the CEO's pet project, you haven't solved the HIPPO problem -- you've just moved it online.

If you're thinking about running better retros and want a framework for capturing what actually matters to your team, What's Your Fifty is worth a look as a starting point for structuring those co

...

Note: To run unbiased team retros and anonymous group voting sessions, get started with WhatsYourFifty today.