Most Dangerous Person in the Room is the One with the Most Power and the Least Context

Photo by Brett Jordan on Unsplash

Most product teams have a story they only tell internally, usually over drinks at a company offsite, about the time a senior executive showed up to a sprint review, asked one question, and accidentally killed three months of work. Nobody pushed back. The **data didn’t matter**. The roadmap shifted, the team rebuilt from scratch, and the thing they were building never made it to users.

This is not a rare story. It’s almost a universal one.

The HiPPO effect, shorthand for Highest Paid Person’s Opinion, is one of the most well-documented failure modes in product development, and also one of the most underaddressed. It’s underaddressed because the person causing it usually doesn’t know they’re doing it, and the people experiencing it don’t feel safe saying so.

What the HiPPO Actually Is

The term was popularized by Avinash Kaushik in his writing on analytics and decision-making, and it describes something simple: the tendency for organizations to defer to the opinion of the most senior or highest-paid person in the room, regardless of whether that person has the most relevant information.

This is not malice. It’s often not even ego. It’s authority bias: a deeply human tendency to treat seniority as a proxy for accuracy. **Dovetail’s research on managing the HiPPO effect** describes it as a natural consequence of how hierarchies function. Deference to leadership is often rewarded, and pushback is often costly, so teams learn quickly which way the pressure flows.

The result is a product organization where decisions look collaborative but aren’t. Where user research gets selectively surfaced. Where the roadmap reflects the executive’s intuition about what users need rather than what users have actually said.

Team That Stopped Sharing Bad News

One of the first teams I coached had this problem in a particularly visible form. Their VP of Product was brilliant, fast, and extremely opinionated. He’d built successful products before and he knew it. His team liked him personally. And they had completely stopped bringing him problems they didn’t already have solutions to.

The reasoning was sound from their perspective. If you showed up with a problem, he’d solve it himself. His solution would become the direction. And the team would spend the next quarter building something that came from his gut rather than from the discovery work they’d done.

UserVoice’s **analysis of HiPPO dynamics** in product teams frames this clearly: when leadership opinions consistently override user data, the team’s incentive to do rigorous discovery erodes. Why run the research if the outcome is already decided? Why surface the uncomfortable finding if it’ll be explained away in the next leadership meeting?

The team hadn’t become lazy. They’d become rational. They were adapting to the incentive structure they lived in.

What Makes It So Hard to Fix

The reason HiPPO dynamics persist is that they’re self-concealing. The senior leader usually has no idea it’s happening. Their meetings feel productive. Their teams seem aligned. The roadmap moves. What they can’t see is all the signal that got filtered before it reached them, all the dissent that turned into quiet compliance, and all the decisions that got made in their direction rather than in the direction of evidence.

UX Planet’s breakdown of the **HiPPO effect in design notes** that this filtering problem compounds over time. Teams learn to present information in frames that are already pre-approved. Research gets curated to support the direction leadership favors. Eventually the leader is operating on a carefully edited version of reality and making confident decisions with incomplete information.

I’ve coached leaders who genuinely believed their teams were high-context and data-driven. When we started looking at how decisions were actually made, the picture was very different. The data was there. It just hadn’t made it into the room.

What I Coach Instead

The first thing I do with any leader who’s creating HiPPO dynamics is help them see that the goal isn’t to have less influence. It’s to have their influence enter the process at the right moment.

There’s a difference between a senior leader who shapes the problem space and one who shapes the solution. The first is invaluable. The second is where the damage happens. Leaders who define the right questions, then step back and let the team develop answers, produce better outcomes than leaders who define both the question and the answer in the same meeting.

Jeff Gothelf’s writing on the **highest paid person’s opinion** argues that the best leaders learn to ask questions rather than make assertions in discovery-phase discussions. Not “I think we should build X” but “What would have to be true for X to be the right move?” That shift in language changes the dynamic entirely. It invites the team to bring their knowledge in rather than waiting for a direction to execute.

Corporate Rebels’ analysis of how HiPPO culture forms and persists adds another layer: psychological safety isn’t just nice to have. Without it, organizations can’t make good product decisions, because the information required for good decisions will never surface in an environment where sharing bad news is punished.

Protecting the Work

As a coach, my job is sometimes to be the buffer. To be the person who can say in a room: “That’s an interesting hypothesis. Let’s pressure-test it against what we know.” Not to dismiss the senior leader’s instinct, which often has real value, but to slow the momentum enough that the team’s context can enter the room.

The most dangerous thing about a HiPPO isn’t the opinion itself. It’s the speed at which the opinion becomes a decision before anyone has had a chance to evaluate it.

Good product teams treat leadership intuition as a starting hypothesis, not a conclusion. They build structures that make it normal and safe to challenge assumptions at any level of the org. They create space for the person with the most relevant context, not the most authority, to have the most influence on the outcome.

That’s not a threat to leadership. It’s the thing that makes leadership actually work.