This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.

Product Management

Building the Customer-Informed Product

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

Your OKR Cascade is Breaking Your Strategy
Aug 1: Most companies cascade OKRs down their org chart thinking it creates alignment. Instead, it fragments strategy and marginalizes supporting teams. Here's what works better than the waterfall approach.
Your Prioritization Problem Is a Strategy Problem
Jul 23: Most teams struggle with prioritization because they're trying to optimize for everything at once. The real problem isn't having too many options—it's not having a clear strategy to choose between them. Without strategy, every decision feels equally important. With strategy, most decisions become obvious.
Behind schedule
Jul 21: Your team is 6 weeks late and still missing features. The solution isn't working harder—it's accepting that your deadlines were fake all along. Ship what you have. Cut ruthlessly. Stop letting "one more day" turn into one more month.
VC’s Future Lies In Building Winners
Jun 21: AI and megafunds are about to kill the traditional venture model, forcing smaller VCs to stop hunting for hidden gems and start rolling up their sleeves to fix broken companies instead.
Should individual people have OKRs?
May 14: A good OKR describes and measures an outcome, but it can be challenging to create an outcome-focused OKR for an individual.
10 OKR traps and how to avoid them
May 8: I’ve helped lots of teams implement OKRs or fix a broken OKR process. Here are the 10 most common problems I see, and what to do instead.
AI is Smart, But Wisdom Requires Judgement
May 3: AI can process data at lightning speed, but wisdom comes from human judgment—picking the best imperfect option when facts alone don’t point the way.
Decoding Product Leadership Titles
Mar 18: Not all product leadership titles mean what they sound like. ‘Head of Product’ can mean anything from a senior PM to a true VP. Here’s how to tell the difference.

Older...

What I'm Reading