How to prevent the HiPPO effect in software selection
The Highest-Paid Person's Opinion shouldn't determine your platform. Independent scoring, aggregated anonymously, is the only way to surface genuine consensus.
The HiPPO effect — where the Highest-Paid Person's Opinion determines the outcome of a decision — is one of the most destructive forces in any evaluation process. In software selection, it typically looks like this: the CTO liked the demo from Vendor B, so suddenly everyone has concerns about Vendor A that they didn't voice before the break.
Why it happens
It's not malice. It's social psychology. People in organisations naturally adjust their stated views to align with authority. In a room where the most senior person has clearly formed a preference, it requires significant social capital to push back. Most people don't spend that capital on a vendor demo.
The result is consensus that isn't really consensus — it's convergence around the most powerful opinion in the room.
The solution: structural separation
You can't fix social dynamics with encouragement. Telling people to "speak up freely" doesn't work because the incentive not to is structural, not a matter of willingness.
The only reliable solution is to structurally separate the scoring phase from the discussion phase. If every evaluator submits their scores before any discussion begins, you capture authentic independent signal. Once the scores are in, no subsequent pressure can change them.
This isn't a new idea — it's the same principle behind anonymous peer review, double-blind studies, and closed-ballot voting. The insight is that you need to make the scoring infrastructure support independence, not just encourage it.
What independent scoring actually looks like
In practice, this means:
- Each evaluator has their own scoring form, completed individually
- Scores are submitted before group discussion takes place
- Aggregated scores are shared with the group only after all individual scores are locked
- Individual scores remain accessible to the project lead for accountability, but are not shared between evaluators during the scoring phase
When you reveal the aggregated scores, disagreement becomes visible and useful rather than suppressed and unresolved. If the CTO scored Vendor B highly but three out of five other evaluators scored it poorly, that disagreement is data. It's something to discuss. It might surface concerns the CTO didn't consider, or it might surface misconceptions the evaluators had. Either way, you're having a better conversation.
Beyond the demo: stakeholder testing
The HiPPO effect operates most strongly at the decision-making level. But the people best positioned to evaluate a software platform are often the people who will use it every day — and they have the least power in the room.
Stakeholder testing, where actual end-users score their own workflows during a sandpit or trial period, is the strongest antidote to both HiPPO bias and to the evaluation team's own blind spots. The operations manager who runs the approval workflow six times a day has expertise about what she needs that no project team member can replicate. Structured, independent scoring captures that expertise.
The combination — independent scoring at every stage, aggregated transparently — produces decisions that are genuinely defensible. Not because the process is bureaucratic, but because it surfaces real signal from people with real expertise.