Watch out for the HiPPO

Way back in 2008 when I wrote chapter three of HWTSAM, I briefly mentioned the HiPPO in the context of ship room (war room) meeting structure:

Everyone’s voice is important. A phrase heard in many war rooms is “Don’t listen to the HiPPO”—where HiPPO is an acronym for highest-paid person’s opinion.

It was a term I came across, but could not find attribution. I discovered fairly recently that Ronny Kohavi (whom I’ve stolen  / borrowed from liberally when discussing A/B testing and experimentation) who came up with the term in 2006.

My old colleague Seth Eliot also discussed the HiPPO in a blog post in a post last year.

While many organizational leaders aspire to become the next Steve Jobs, just about all of them will fail (as an aside, I was in a meeting once where a very senior person said that they made a critical decision, because “it’s what Steve Jobs would do, , and I’m like Steve Jobs”). What I’ve discovered is that no matter how strongly someone feels they “know what’s best for the customer”, without data, they’re almost always wrong.

It can be a big step to use data over organizational rank to make decisions, but if you care about pleasing your customers, the choice is obvious.

Similar Posts

  • The Fallacy of Now

    A long time ago (for most of us), we built products over a long period of time, and hoped that customers liked what we built. It was important to give them all of the features they may need, as we wouldn’t be able to get them new features until the next release, which was usually at…

  • Scaling Code Coverage

    I’m going to do one more (I think) post on this subject. Markus asked the following about my latest post: But how do I answer the question for “what’s the coverage of your testing?” for a multiple component-based application, consisting of a C/C++ major component, an application server, and customized business logic? The answer is…

  • An Interlude

    As you may have noticed, I’ve had to take a bit of a break from blogging. I’ve kicked out at least a post or two a week for a few years now, but I’m not dry on ideas, and I definitely want to follow up on my recent Test This post (before a follow up…

  • Unity

    For those of you who missed it on Twitter or in the AB Testing Podcast, my unemployment lasted (as planned) just a bit over week. On January 30, I started work at Unity, heading up quality for their various services. I spent most of last week trying to learn as much as I can and…

4 Comments

  1. “no matter how strongly someone feels they “know what’s best for the customer”, without data, they’re almost always wrong.”

    Wow… that is so profound, did you coin that term of phrase yourself, or read it somewhere cause that is awesome!

      1. Alan,

        Nice post.

        You mentioned that Kohlhavi coined the term HiPPO. I absolutely loved the talk he gave called “Practical Guide to Controlled Experiments on the Web: Listen to Your Customers not to the HiPPO.” http://videolectures.net/kdd07_kohavi_pctce/ He gave it in 2008 or 2009 but it’s still very relevant.

        I’d highly recommend it. I’m confident you’d like it. But if you don’t have 22 minutes to spare, I created an executive summary of sorts in a blog post I wrote in 2009:

        https://hexawise.com/posts/in-praise-of-data-driven-management-aka-why-you-should-be-skeptical-of-hippos

        Good luck with your talk tomorrow’s talk back at your old firm.

        Justin

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.