Back to blog
Product companies don't struggle with customer-centric strategy because nobody is listening to customers. They struggle because the loudest voice in the strategy room almost always belongs to whoever understands the product best. Customer insight still gets collected — surveys run, interviews happen, journey maps get built — but by the time it reaches the room where decisions actually get made, the direction has usually already been set by what's technically feasible, what the factory can produce, or what last year's roadmap assumed.
That's the product-led trap, and it's a sharper problem than simply "not being customer-centric enough." The company hasn't stopped caring about customers. It's built an organisation where product logic wins by default, every time it matters. This is what we mean by inside-out thinking; for the fuller contrast with its alternative, see What is Outside-In Strategy? A Practical Guide.
The product-led trap
There's nothing wrong with being good at making things. Product capability is a legitimate competitive asset, and companies that have built genuine technical depth have earned it. The trap isn't the capability itself — it's what happens when that capability becomes the primary lens through which strategy gets made.
We've seen this repeatedly in product-led organisations: the strongest voice in the room tends to belong to the people who understand the product best. Customer insight enters the conversation, but it enters late; after the fundamental decisions have already been shaped by what's technically feasible, what the manufacturing line can support, or what the last three years of margin data suggests is worth pursuing. Customers validate options that were already on the table. They rarely change what's on the table in the first place.
"Customers validate options that were already on the table. They rarely change what's on the table in the first place."
This is inside-out thinking in its most comfortable form. It doesn't feel like arrogance, it feels like rigour. Companies operating this way often have sophisticated market research functions and detailed customer segmentation. The problem isn't that they're not looking at customer data. It's that the data rarely changes the direction of travel. It confirms what's already been decided. The consequence shows up slowly: products shaped around internal assumptions rather than genuine customer priorities start to lose relevance, the market drifts, and the organisation doesn't drift with it. It's the same drift we describe in Inside-Out vs Outside-In Strategy, just seen from the product organisation's side of the table.
What customer-centric strategy means
There's a version of customer focus that looks good in presentations but doesn't change much. Companies gather insight, run surveys, conduct interviews, build journey maps. Leadership reviews the findings and nods in agreement. Then the strategy discussion happens, and the familiar internal logic reasserts itself. The insight is absorbed but not acted on.
Genuine customer-centric strategy works differently. The starting point for strategic discussion isn't internal capability or past performance, it's an honest, specific account of what customers actually value, what problems they're trying to solve and where the current offer falls short of their reality. From that foundation, you work backward to capabilities, investments, and priorities. The organisation shapes itself around what matters to the customer, rather than asking customers to fit what the organisation finds comfortable to deliver.
Three shifts tend to mark the companies that have made this move. First, they stop using internal performance as a proxy for market relevance. Year-on-year comparisons tell you whether you're improving against yourself, they don't tell you whether customers still find you the best available answer to their problem. The more useful question is where customers are heading, not how well you're performing against where they used to be. Second, they bring customer insight into the room before strategic options have been narrowed. If insight only enters after the shortlist has been formed, it will almost always confirm something on the list — which makes it feel rigorous without being generative. Third, they test ideas with customers early, in rough form, rather than refining internally until something is polished enough to present. The discipline of early exposure is uncomfortable for product-led organisations, but it catches misalignment when it's still cheap to correct.
What this looks like in practice
We worked with a manufacturer whose customer insight operation was, on paper, exemplary. Quarterly satisfaction surveys, an annual NPS cycle, a market research team that produced detailed reports. What they didn't have was any mechanism for that insight to reach the product roadmap before decisions were already made. By the time customer feedback moved through the research function, into a presentation, onto the leadership agenda, and eventually into a conversation with the product team, it was typically nine to twelve months old. The product decisions being made in that meeting had been shaped by a picture of the customer that no longer reflected the market.
The fix wasn't more research. It was restructuring which conversations happened in which order. For manufacturers specifically, that restructuring usually starts with mapping the buyer's full journey rather than relying on a single insight snapshot — see How Customer Journey Mapping Works in Manufacturing. Customer insight moved upstream into the early stages of product planning, before the shortlist of options had been formed, with commercial and product leads in the same room. The first few cycles were uncomfortable. Customer feedback challenged assumptions that had felt settled. Some roadmap investments that looked solid internally turned out to address problems customers had already solved another way. Catching that early was significantly cheaper than catching it at launch.
The same structural fix shows up in consumer-facing product companies, just with a different cast of characters. A consumer goods manufacturer we've worked alongside ran retail-shelf research religiously — but it sat with a category insights team that reported into marketing, three steps removed from the product development committee that actually decided what got built next year. By the time a shelf insight reached that committee, the range plan was usually locked. The fix was structural, not additive: a standing seat for category insight inside the product planning meeting itself, not a report that got read afterwards.
The structural challenge no one wants to talk about
Building a customer-centric strategy isn't primarily a mindset problem. Mindset matters, but most leadership teams we work with already believe in the principle. The harder challenge is structural.
Product roadmaps, commercial planning, and customer insight tend to run in parallel rather than in sequence. Insight is gathered on one cycle, product decisions are made on another, and commercial planning happens on a third. By the time customer reality has moved through those stages, it's often six to twelve months old. Decisions are being made on a customer insight that no longer reflects how demand is shifting and what's happening in the market.
The organisations that close this gap create shared forums where customer insight and strategic decisions happen in the same conversation, not handed off between functions. They build accountability structures that reward decisions made in response to customer signals, not just decisions that protect existing revenue. And they invest in continuous customer contact that gives commercial and product leaders a current read on the market, rather than a snapshot from last quarter's research cycle. This asks product and commercial teams to share ownership of decisions they've historically made separately. It means tolerating the discomfort of discovering, regularly, that what you thought customers valued isn't quite right.
On why that shared ownership so often breaks down in practice — and what a real mandate for the outside-in perspective requires — see Customer Focus Has No Owner.
That discomfort is the point. It's the signal that the outside-in feedback loop is working.
"That discomfort is the point. It's the signal that the outside-in feedback loop is working."
Key takeaways
Customer-centric strategy means starting from what customers truly value and working backward to capabilities and investments — not the reverse. Most product companies do the reverse without realising it.
The product-led trap is real: strong technical capability tends to become the dominant lens for strategic decisions, with customer insight entering late and validating options already on the table rather than changing them.
Gathering customer insight and letting it change strategic direction are different things. If insight doesn't have the power to alter what's on the agenda, it's market research, not strategy.
Bringing customer reality into strategic discussion before options have been narrowed is one of the highest-leverage moves a product company can make — but it requires disrupting how planning processes currently work.
The structural gap between insight, product planning, and commercial strategy is where customer centricity breaks down in practice — in B2B and consumer product companies alike. Closing it requires shared forums and shared accountability, not just shared values.
FAQ
What is the product-led trap?When strong technical and engineering capability becomes the dominant lens for strategic decisions, so customer insight enters late and validates options already on the table rather than shaping what's on it.
How is customer-centric strategy different from having a CX team or running surveys?Having the infrastructure isn't the same as it changing anything. The real test is whether customer insight enters before strategic options are narrowed — not whether it's collected at all.
What are the three shifts that mark companies who've made this change?They stop treating internal year-on-year performance as a proxy for market relevance, they bring customer insight in before options are shortlisted, and they test ideas with customers early rather than polishing internally first.
Why does this feel uncomfortable even when leadership agrees with the principle?Because it requires product and commercial teams to share ownership of decisions they've historically made separately, and it means regularly discovering that assumed customer priorities were wrong — while there's still time to correct course cheaply.
Is this primarily a mindset problem?No. Most leadership teams already believe in the principle. The harder challenge is structural — product roadmaps, commercial planning, and customer insight typically run on separate cycles rather than in the same conversation, in consumer product companies as much as in B2B manufacturing.
