Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

The KPI that measures Product-Market Fit

Freshness Warning
This blog post is over 3 years old. It's possible that the information you read below isn't current and the links no longer work.

9 Sep 2020

Asking the users of your software, “How disappointed would you be if you could no longer use this product” is a great way to gauge satisfaction. It’s also a good way to measure product-market fit.

The answers aren’t going to tell you if you’re there yet. But the trend of answers will tell you if you’re moving in the right direction.

If you ask this question to a different small group of your users every week, you can measure trends over time in those that say they’d be extremely disappointed to lose your product.

The answer scale I prefer is a simple three-point scale. Users can answer “extremely disappointed,” “somewhat disappointed,” or “I don’t care.” This makes it simple to answer and also makes it a simple metric to track.

Using this scale, the percentage of people that pick the “extremely disappointed” option is your product-market fit performance indicator. The larger percentage of your users that feel this way, the more likely you’re delivering the right product to the right market.

There’s no such thing as a good or a bad percentage. Comparing your numbers to another company’s won’t be useful. The only useful measurement is if your number is going up or down. As long as it’s trending up you’re achieving or retaining your product-market fit.

Recently Written

Too Big To Fail (Apr 9): When a company piles resources on a new product idea, it doesn't have room to fail. That keeps it from succeeding.
Go small (Apr 4): The strengths of a large organization are the opposite of what makes innovation work. Starting something new requires that you start with a small team.
Start with a Belief (Apr 1): You can't use data to build products unless you start with a hypothesis.
Mastery doesn’t come from perfect planning (Dec 21): In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27): Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13): Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17): You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?
How I use OKRs (Oct 13): A description of how I use OKRs to guide a team, written so I can send to future teams.