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.

Building the Customer-Informed Product

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

Customers should not lead your product development. Product managers that function by taking every feature request from the customer, turning them into product requirements, and working to deliver that feature are going to end up building a product that is disjointed and has no strength of vision. They’ll likely have very satisfied customers, but little growth and ability to scale. Instead of building what the market wants, they’re building what specific customers want.

We see this pattern in companies that build based on feature voting, and in companies that don’t have a strong opinion about what needs to be built. They act almost as a custom development shop, with some common components and maybe a common codebase, but with little feature usage overlap across customers.

Strong products are guided by strong visions, and the execution of that vision is the primary focus of product development.

This doesn’t mean that you shouldn’t listen to your customers. But your product roadmap should be customer-informed, not customer-led.

To understand the difference, imagine a seafood restaurant. They have customers come in periodically that don’t eat fish, so those customers ask for different food items. Some ask for salads. There’s some requests for steak. One weirdo wants a tofu burger topped with chocolate ice cream.

All these customers are willing to pay for their requested items, and often they’re willing to pay a lot more than you’d expect.

If the restaurant blindly implements every requested dish, they’ll lose their identity as a restaurant. They’re no longer a seafood restaurant, they’re an anything goes café that happens to serve a lot of fish. But their customers are telling them something important. They’re telling them they have needs that aren’t being met by the restaurant, and for whatever reason, they like the restaurant enough to want them to fill those needs, instead of just going to another restaurant.

What a reasonable restaurant would do is look at all these requests and see what adjustments they could make, for all customers, to fulfill the needs of these customers. They might decide to add a vegetarian option or two in the form of a salad or a pasta dish. If most of their requests were for various steak dishes, they may pick a single steak to offer on the menu.

This is being customer-informed. They’re letting the customers as a group influence the menu, but they’re not letting any one customer dictate the menu.

Recently Written

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.
Build the whole product (Oct 6)
Your code is only part of the product
Input metrics lead to outcomes (Sep 1)
An easy to understand example of using input metrics to track progress toward an outcome.
Lagging Outcomes (Aug 22)
Long-term things often end up off a team's goals because they can't see how to define measurable outcomes for them. Here's how to solve that.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2024 Adam Kalsey.