Your Product Roadmap Is a Brilliant Solution to a Problem Your Customers Don't Have

Here is an exercise worth running in your next product leadership meeting. Ask the room: in the last quarter, how many hours did your product team spend talking directly to customers, not in structured usability sessions, not reviewing support tickets, not reading NPS commentary, but in genuine, open-ended conversation about the customer’s world?

Then ask: how many hours did they spend in internal roadmap planning, sprint ceremonies, stakeholder alignment meetings, and prioritisation sessions?

The ratio in most businesses is not close. And it explains, more precisely than any other single factor, why most product roadmaps are technically impressive and commercially disappointing.

The Inside-Out Problem

Product development has a structural bias that is almost impossible to eliminate through good intentions alone. It is built into the process.

The people who build products are, by definition, experts in the product. They understand its architecture, its constraints, its potential, and its current limitations better than anyone. They have strong, well-reasoned views on what it should do next. And they are spending most of their professional lives inside the building — in standups, in design reviews, in technical discussions rather than outside it, in the world their customers actually inhabit.

This creates what might be called the inside-out product: a product whose roadmap reflects what the team finds interesting to build, what the existing architecture makes feasible to build, and what internal stakeholders have requested rather than what customers actually need, value, and would pay more for.

The inside-out product is not a failure of intelligence or effort. It is a failure of orientation. The team is facing the wrong direction. And no amount of customer satisfaction surveys, analytics dashboards, or quarterly business reviews will correct it, because all of those mechanisms are filters; they tell you what customers think about what you have already built, not what they need that you have not yet imagined.

What Customer Discovery Actually Is

The solution to the inside-out problem has a name, customer discovery, and it is one of the most consistently underinvested activities in product-led businesses.

Customer discovery is not user research. It is not a focus group. It is not a Net Promoter Score programme. It is the practice of spending extended, unstructured time with customers in their actual working context, asking questions whose answers you cannot predict, listening for the things they say that surprise you, and building a genuine understanding of the world they inhabit, the pressures they face, the workarounds they have built, the problems they have normalised, the outcomes they are actually trying to achieve.

The output of this process is not a feature list. It is a shift in perspective; a genuine reorientation from the inside view to the outside view. And that shift, in product terms, is worth more than any amount of roadmap refinement.

Consider the university essay parallel. The essay itself, the deliverable, the document, is almost worthless as a standalone object. What the essay produces is fifteen hours of genuine immersion in a subject: sources that contradict each other, arguments that had to be constructed rather than assumed, an understanding that only comes from having to explain something clearly. The essay is the excuse. The thinking is the point.

Customer discovery works the same way. The formal output, the insight document, the persona update, the jobs-to-be-done framework is the essay. What matters is the shift in understanding that the process generates in the people who conduct it. A product manager who has spent two days in the field with customers understands the product differently. They ask different questions in sprint planning. They push back differently when an internally-generated feature request conflicts with what they have seen. They notice things in the data that their colleagues miss.

That shift cannot be manufactured by proxy. It requires direct, unhurried, genuine contact with the world the product is supposed to serve.

A product manager who has spent two days in the field with customers understands the product differently. That shift cannot be manufactured by proxy.

The Normalisation Trap

One of the most valuable things that genuine customer discovery reveals is the gap between what the organisation believes its customers experience and what customers actually experience.

This gap is almost always larger than expected. And it opens in a predictable direction: organisations consistently underestimate the friction in their product and overestimate the value of their features.

The friction becomes invisible internally because the team has normalised it. The onboarding flow that takes forty-five minutes and requires three handoffs between departments feels, to the team that built and uses it daily, like a reasonable process. To a new customer encountering it for the first time, under real-world time pressure, with competing priorities and no institutional knowledge of why the steps exist, it is a significant barrier. Not significant enough to trigger a support ticket. Significant enough to generate the quiet doubt — is this worth the effort? — that contributes to eventual churn.

The features, meanwhile, are overvalued internally because the team built them and believes in them. The last major development cycle produced something technically sophisticated. Internal stakeholders are pleased with it. It features prominently in sales presentations. Customers, in honest conversation, cannot describe what it does without prompting, have not used it in the past quarter, and would not notice if it disappeared.

Both of these discoveries, the normalised friction and the invisible features, are available to any organisation willing to conduct honest customer conversations. Neither is visible from inside the building.

The Structural Fix: Customer Proximity as a Design Principle

The businesses that consistently build products their customers value and pay for are not the ones with the best product managers or the most sophisticated development processes. They are the ones that have made customer proximity a structural commitment rather than a periodic activity.

This means product leaders spending meaningful time in the field on a regular cadence, not when there is a specific research question to answer, but as a continuous practice of staying oriented toward the outside world. It means sales and customer success conversations being systematically fed back into product thinking, not filtered through a feature request queue. It means the metrics of product success being defined in terms of customer outcomes (are customers achieving the thing the product is supposed to help them achieve?) rather than engagement metrics that can be gamed by product decisions that create friction.

And it means, structurally, that the question “what does the customer need?” is asked before the question “what is feasible to build?” rather than after it. This sounds obvious. In practice, in most organisations under delivery pressure, it works the other way around: feasibility defines the scope, and customer need is then used to justify the decision already made.

What This Means for PE-Backed Product Businesses

For any PE operating partner overseeing a product-led portfolio company, customer discovery investment is one of the highest-returning activities available, and one of the most commonly cut when the business is under pressure to demonstrate near-term efficiency.

The argument for cutting it is superficially compelling. Customer research does not produce a deliverable that appears in the next sprint. Its output is qualitative, hard to attribute, and impossible to put in a dashboard. Against a cost reduction mandate, it loses every argument.

What it produces, invisibly, is the difference between a product that customers love and one they merely use. That difference shows up in NPS, in churn, in willingness to pay at renewal, in the reference calls that close enterprise deals, and in the exit multiple that a buyer is prepared to justify. It does not show up in the quarter the investment was made.

The businesses that arrive at exit with a product genuinely loved by its users, not just adopted, loved, command a premium that is disproportionate to any other factor in the value creation plan. Building that product requires sustained, genuine investment in understanding the customer’s world. And that investment has to be protected even when, especially when, the pressure is toward short-term efficiency.

The Uncomfortable Conclusion

The product roadmap that has been developed without sustained, genuine customer contact is a sophisticated piece of internal fiction. It reflects what the organisation believes about its customers rather than what is true. And the gap between those two things, between the inside view and the outside view, is where products lose their relevance, features accumulate without value, and growth slows in ways that analytics dashboards diagnose too late to correct.

The fix is not a research programme. It is a reorientation; a structural commitment to spending enough time in the customer’s world that the inside-out bias is continuously corrected. That commitment cannot be delegated to a research function or replaced by a survey cadence. It requires the people who make product decisions to be, regularly and genuinely, in direct contact with the people those decisions affect.

The essay is not the point. The thinking it demands is the point. And there is no shortcut to the thinking.

---

If you need an independent perspective on whether your product strategy is genuinely customer-oriented or internally driven, or if your operating model needs recalibrating around customer proximity, talk to us.