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.

How to understand your product and your market

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.

30 Sep 2020

Once you’re measuring your product-market fit though the end-user satisfaction question you will want to know "why?" Why do the people who love your product love it?

It sounds strange, but most product people don’t understand their products. They know the product features. They know who they think the market is. But they don’t know who loves their product. They don’t know what those people love about it. And this can often be something different than what the product set out to be.

You can ask your end-users another question if you want to understand your product through the eyes of your biggest fans. Ask them what their favorite parts of your product are. You need to phrase this in a way that doesn’t ask about features, or you’ll get a boring list of functional features that doesn’t tell you much. Your product is more than a list of features. Your product feedback needs to be more than a list of features, too. You want feedback to be a mix of functional and non-functional things.

Ask, "What do you like best about the product?"

Phrased this way, some users may mention their favorite feature. Some will talk about how it makes them feel. Some will talk about what problem it solves for them. They might mention your customer service. Your pricing. Or even how fast and responsive the product is.

Cluster the responses. There will be outliers. Someone probably just loves that one of your buttons is purple. But the biggest clusters of responses coming from your biggest fans are the reason that your target customer loves your product. The people that fall into those clusters represent the target customer for the product you have today. There’s a growth opportunity in finding customers that are looking for a product that fills those same needs.

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.