What Product Managers Want Customers to Know
There is a version of the PM-customer relationship that product managers engage in publicly — empathetic, responsive, forward-leaning — and a version that exists internally, full of context and constraints that never quite make it into the stakeholder conversation. This gap between the public and private versions of the relationship creates frustration on both sides.
What follows is a candid articulation of what most product managers genuinely wish their customers understood — not to excuse product decisions, but to enable more productive collaboration between the people building products and the people using them.
We Are Simultaneously Serving Hundreds of Customers
When a customer presents a feature request as urgent and obvious, they’re presenting it from the perspective of their specific context, their specific workflow, and their specific priorities. From inside that context, the request may seem like it should be obvious to build.
From the product manager’s perspective, every active customer has presented requests that seem equally obvious and urgent from their context. The product team’s job is to find the investments that serve the most users most significantly — not to serve each individual user optimally.
This doesn’t mean any individual request doesn’t matter. It means that each request must be evaluated as a potential investment serving many customers, not just the one who asked for it.
“On the Roadmap” Doesn’t Mean “Coming Soon”
The product roadmap represents current best thinking about priorities and direction, not a queue of committed deliverables. When something is “on the roadmap,” it means the team has identified it as worth addressing at some point — not that it’s confirmed for a specific sprint.
Product priorities change as teams learn from users, as market conditions shift, and as business strategy evolves. An item that was planned for Q3 when the roadmap was last reviewed may be deprioritized by Q3 when something more significant has emerged. This is how good product management is supposed to work, not a failure of planning.
Your Feature Request Often Points to Something More Important Than the Feature
Customers are experts at identifying friction in their own workflows. They’re not usually experts at designing the best solution to that friction — and neither are product managers, until they understand the friction deeply.
The most valuable thing a customer can share is the specific workflow problem they’re experiencing, not the specific feature they’ve imagined as the solution. The problem description opens solution possibilities; the feature description forecloses them. Product managers who understand the real problem often find solutions that serve the customer better than the requested feature would have.
We Care More About Your Success Than We Communicate
The gap between how much product managers care about their customers’ success and how well they communicate that care is significant and creates unnecessary distance in the relationship. Most product managers chose this work because they want to build things that make people’s work easier, better, and more meaningful. Customer frustration with the product is genuinely painful to the people who built it.
This care doesn’t always translate into doing exactly what customers ask for — because doing exactly what each customer asks would produce an incoherent product that serves no one well. But it does translate into taking every customer’s underlying needs seriously, even when the specific request can’t be accommodated.
Key Takeaways
The PM-customer relationship works best when customers understand that product decisions reflect the full complexity of serving many users simultaneously, that roadmap commitments are directional rather than contractual, that problem descriptions are more valuable than feature requests, and that the product team’s investment in customer success is real even when specific requests can’t be immediately accommodated.