HiPPO

What is HiPPO?

HiPPO, short for highest paid person's opinion, is a label for decisions settled by the seniority of whoever holds a view rather than by data or testing. The term spread through the online experimentation community in the 2000s.

Updated November 2026 · 4 min read


HiPPO stands for "highest paid person's opinion." It describes a decision made because the most senior person in the room prefers it, not because evidence supports it. The label is light-hearted, but the pattern it names is costly: when rank settles arguments, teams stop testing ideas, customer data gets set aside and the organization keeps repeating whatever its leaders already believe.

The acronym dates from the mid-2000s and is often credited to analytics author Avinash Kaushik, though Ron Kohavi's experimentation team traces an earlier "HiPO" coinage to Intuit in 2006. It spread through the online experimentation community, helped by a 2007 paper by Ron Kohavi, Randal Henne and Dan Sommerfield titled "Practical Guide to Controlled Experiments on the Web: Listen to Your Customers not to the HiPPO." The point of the paper, and of the term, is not that senior people have bad ideas. It is that any idea, including a senior person's, should be checked against what customers actually do.

Why HiPPO decisions happen

  • Authority gradients. People hesitate to contradict someone who controls their budget, promotion or project. Silence gets read as agreement.
  • Missing or slow data. When there is no quick way to test an idea, the loudest or most senior opinion fills the gap.
  • Experience that no longer applies. Leaders often rose on instincts that were right for an earlier market, product or customer base.
  • Time pressure. Deferring to the boss is faster than gathering evidence, especially near a deadline.
  • Unclear decision ownership. If nobody knows who decides, the most senior attendee decides by default. Clear decision rights reduce this.

Signs of a HiPPO culture

A few patterns show up repeatedly in organizations where opinion outranks evidence:

  • Roadmap items appear after an executive meeting with no problem statement or data attached.
  • Experiments are run, but results that contradict a leader's view are explained away or quietly dropped.
  • Meetings end when the senior person speaks, and junior team members rarely present findings.
  • Success metrics are chosen after launch, so any outcome can be called a win.
  • Teams pre-check ideas with leadership before they talk to customers.

HiPPO vs. executive judgment

Not every leadership call is a HiPPO decision. Leaders are paid to make decisions under uncertainty, and many choices, such as entering a market or making an acquisition, cannot be A/B tested. The difference is whether the decision is open to evidence.

AspectHiPPO decisionSound executive judgment
BasisPersonal preference or seniorityStated reasoning plus the best available evidence
DissentDiscouraged or ignoredInvited before the decision is made
TestabilityTestable questions go untestedTestable questions are tested; untestable ones are reasoned through
ReviewRarely revisitedSuccess criteria set in advance and checked later

How to avoid HiPPO decisions

  1. Agree on the metric before the debate. If everyone accepts in advance what success looks like, the conversation shifts from "who is right" to "what would show us."
  2. Make testing cheap. Feature flags, prototypes and A/B testing lower the cost of checking an idea, so testing becomes the default response to disagreement.
  3. Frame ideas as hypotheses. "We believe X will increase Y by Z" invites evidence. "We should do X" invites a vote.
  4. Have the senior person speak last. Collecting views before the leader shares theirs surfaces information that would otherwise stay hidden.
  5. Record decisions and revisit them. A decision log with expected outcomes makes it easy to check later whether the call was right.
  6. Get leaders to model it. When an executive publicly changes their mind because of data, the rest of the organization learns that evidence wins.

A hypothetical example

Consider a hypothetical B2B software company whose CEO wants to replace the "Start free trial" button on the pricing page with "Talk to sales," believing enterprise buyers prefer a conversation. The product manager does not argue the point. Instead, she proposes a four-week A/B test, with the CEO's agreement that the deciding metric will be qualified leads, not clicks.

The test splits 20,000 pricing-page visitors evenly. The control, with the trial button, produces 240 qualified leads from 10,000 visitors, a 2.4% rate. The "Talk to sales" variant produces 180 from 10,000, or 1.8%. That is 60 fewer qualified leads, a 25% relative drop, and the difference is statistically significant at this sample size. The CEO keeps the trial button and asks the team to test a version that offers both options. The outcome matters less than the process: the CEO's idea was treated as a hypothesis, tested on agreed terms and decided by the result.

Common pitfalls

  • Using "HiPPO" as an insult. Calling a leader a HiPPO in a meeting creates defensiveness. The goal is a better decision process, not winning an argument.
  • Swapping one HiPPO for another. Replacing an executive's opinion with a product manager's opinion is the same problem with a lower salary.
  • Testing only what is easy. If teams test button colors but strategy decisions stay opinion-driven, the culture has not changed.
  • Treating data as infallible. Poorly designed experiments or vanity metrics can mislead as badly as opinion. Evidence needs scrutiny too.

Moving away from HiPPO decisions is part of building a broader habit of data-driven decision making. It works best alongside a shared product experimentation framework, clear decision-making practices and an outcome focus that judges work by its results rather than by who proposed it.

Frequently asked questions

Where does the term HiPPO come from?

HiPPO dates from the mid-2000s and is often credited to analytics author Avinash Kaushik, though an earlier HiPO coinage has been traced to Intuit in 2006. It spread through the online experimentation community, helped by a 2007 paper by Ron Kohavi and colleagues that urged teams to listen to customers rather than the HiPPO.

How can a team avoid HiPPO decisions?

To avoid HiPPO decisions, agree on the success metric before debating, frame ideas as testable hypotheses and make testing cheap with prototypes, feature flags or A/B tests. Have the most senior person share their view last, and keep a decision log with expected outcomes. Leaders who visibly change their minds based on data reinforce the habit.

Is every executive decision a HiPPO decision?

No. Leaders are expected to make calls under uncertainty, and choices such as entering a market often cannot be tested directly. A decision becomes a HiPPO decision when it rests on seniority or preference, dissent is discouraged and testable questions go untested. Sound executive judgment invites challenge, uses the best evidence available and sets success criteria in advance.