What Harvard Business Review Says About Customer Centricity

Most organisations say they are customer-centric. A smaller number have built the processes to prove it. A smaller number still have genuinely restructured around the customer rather than around internal convenience. The gap between the first group and the third is where most CX transformations quietly die — not from lack of intent, but from a misunderstanding of what customer centricity actually requires.

Harvard Business Review has published some of the most rigorous and practically useful thinking on this subject over the past two decades. What emerges from that body of work is not a feel-good manifesto about "putting the customer first." It is a structural argument: that customer-centric companies are built differently, measured differently, and led differently — and that the difference is observable in their financial performance, particularly under stress.

Customer centricity is not a value statement. It is an operating model — one that requires deliberate architecture, not just good intentions.

What Does "Customer Centricity" Actually Mean?

Defining customer centricity with precision matters, because vagueness is how organisations convince themselves they already have it. A working definition: customer centricity is the systematic alignment of a company's strategy, structure, processes, and culture around delivering value to customers — not around internal functions, products, or short-term revenue targets.

The critical word is "systematic." A single brilliant customer service team does not make an organisation customer-centric. A well-designed app does not either. Customer centricity is present when the organisation's default decisions — budget allocation, product prioritisation, hiring criteria, success metrics — consistently favour the customer's outcome over internal convenience.

This distinction matters because most organisations optimise for the latter while believing they are doing the former. They measure call handle time rather than resolution quality. They design onboarding flows around compliance requirements rather than the customer's job-to-be-done. They run NPS surveys and then use the scores to report upward rather than to change anything downstream. These are not customer-centric behaviours dressed up as customer-centric intentions — they are the opposite.

What the HBR Evidence Actually Shows

The most cited empirical anchor in this conversation comes from Ranjay Gulati's longitudinal research, published in the March 2010 issue of Harvard Business Review under the title "Silo-Busting." Gulati's central finding was that "outside-in" customer-centric companies — those that organise around customer needs rather than internal product or functional logic — are significantly more resilient during economic downturns and recover faster when conditions improve.

The mechanism Gulati identified is structural. Companies that have broken down internal silos in service of the customer are, by definition, more integrated. That integration means they can respond to shifting customer needs without the coordination drag that slows silo-based organisations. When a downturn forces rapid adaptation, the customer-centric company has already built the connective tissue. The product-centric company has to negotiate it under pressure.

This is not a soft finding. It is an argument about organisational design as a source of competitive advantage — and it has direct implications for how leaders should think about the business case for customer centricity. The return is not only in customer satisfaction scores; it is in structural resilience.

Why Most Customer Centricity Efforts Fail

The common customer centricity mistakes are remarkably consistent across industries and geographies. Understanding them is more useful than a list of best practices, because the failure modes are where the real diagnostic work lives.

• Mistaking measurement for management. Deploying NPS or CSAT surveys creates the appearance of customer focus without the substance. Scores that are not connected to specific operational decisions, owner accountability, or closed-loop action are decorative. They tell you something is wrong; they do not fix it.
• Confusing customer service with customer centricity. Customer service is a function. Customer centricity is a strategy. An organisation can have an excellent contact centre and still design products that frustrate customers, price in ways that feel exploitative, or make it genuinely difficult to leave — all of which are anti-customer-centric behaviours happening upstream of the service team.
• Silo-based ownership of the customer. When "the customer" belongs to Marketing, or to a CX team with no budget authority, the organisation has not committed to customer centricity — it has created a function to perform it symbolically. Real customer centricity requires that every function — Finance, Operations, Legal, IT — has a stake in customer outcomes.
• Treating culture as a communications project. Announcing a customer-first culture through internal campaigns is not the same as building one. Culture is the residue of repeated decisions. If the decisions that get rewarded are the ones that hit internal targets at the expense of the customer, the culture will reflect that regardless of what the values poster says.
• Optimising individual touchpoints instead of the journey. A touchpoint that scores well in isolation can still sit inside a journey that is exhausting or confusing. Customers do not experience touchpoints; they experience sequences. Fixing individual moments without mapping the whole is the CX equivalent of repainting a room in a structurally unsound building.

How to Measure Customer Centricity Properly

Measuring customer centricity requires a broader instrument panel than most organisations currently use. The standard trio — NPS, CSAT, and CES — captures customer sentiment at specific moments. It does not capture whether the organisation is structurally oriented toward the customer or merely performing well at surveyed touchpoints.

A more complete measurement framework operates at three levels:

1. Outcome metrics — the customer's actual result. Did the customer achieve their goal? Did the product or service deliver the value promised? Retention, repeat purchase, and referral behaviour are proxies here, but the cleanest measure is goal completion: did the customer accomplish what they came to do?
2. Experience metrics — how the customer felt during the journey. NPS, CSAT, and CES belong here, but they should be mapped against specific journey stages rather than collected as aggregate scores. A high overall NPS that masks a terrible onboarding experience is not useful intelligence.
3. Organisational metrics — whether the company is structurally capable of being customer-centric. This includes: the proportion of senior leadership time spent on customer insight, the speed of closed-loop action on complaints, the degree to which customer data is shared across functions, and whether customer outcomes appear in executive incentive structures.

The third level is where most organisations have the largest gap. They measure what customers feel; they rarely measure whether the organisation is structurally capable of acting on it. A CX maturity assessment that covers governance, data infrastructure, and cross-functional accountability gives a more honest picture of where an organisation actually sits than any sentiment survey alone.

What Real Examples of Customer Centricity Look Like

Abstract principles become actionable when grounded in observable behaviour. Examples of customer centricity worth studying share a common characteristic: the customer's outcome is built into the operating model, not bolted on as an afterthought.

In banking, customer centricity means designing products around the customer's financial job-to-be-done — saving for a specific goal, managing cash flow, reducing debt — rather than around the bank's product margin targets. It means proactively alerting a customer when they are about to incur a fee, rather than waiting for the complaint. It means making it as easy to close an account as to open one, because an organisation confident in its value does not need to trap customers. The banking and finance sector provides some of the most instructive contrasts between organisations that have genuinely restructured around the customer and those that have not.

In retail, customer centricity is visible in returns policies, in the way staff are trained and incentivised, and in whether the organisation treats loyalty as a mutual relationship or as a points-accumulation mechanism. A retailer that makes returns effortless is not being generous — it is applying the endowment effect intelligently: customers who trust a returns policy buy with less hesitation, and the lifetime value gain outweighs the returns cost.

In public services, customer centricity means designing processes around the citizen's context — their time constraints, their literacy levels, their access to technology — rather than around administrative convenience. The organisations that have made the most progress here have typically done so by mapping the citizen journey end-to-end and identifying where the process serves the institution rather than the person it is meant to serve.

The Behavioral Economics Dimension

One of the most underused tools in achieving customer centricity is behavioral economics — specifically, the insight that customers do not make decisions the way organisations assume they do. Richard Thaler and Cass Sunstein's work on choice architecture (developed in their 2008 book Nudge and extensively cited in subsequent HBR writing) demonstrates that the way options are presented shapes decisions as powerfully as the options themselves.

A customer-centric organisation uses this knowledge to design experiences that work with human cognition rather than against it. Default settings that protect the customer. Processes that reduce cognitive load at moments of complexity. Communications that present information in the order a customer needs it, not in the order that is convenient to produce. These are not manipulative interventions — they are the application of accurate knowledge about how people actually behave, in service of their genuine interests.

The contrast with a non-customer-centric approach is stark. An organisation that buries cancellation options, presents pricing in ways that obscure the true cost, or designs renewal flows that rely on customer inertia is also using choice architecture — but against the customer. The behavioral economics lens makes this visible and gives leaders a principled basis for auditing their own experience design against the question: whose interests does this choice architecture actually serve?

Embedding this kind of thinking into behavioral economics practice is one of the highest-leverage moves available to a CX team — because it addresses the gap between what organisations intend and what customers actually experience.

Customer Centricity Strategies That Hold Under Pressure

The strategies that distinguish genuinely customer-centric organisations from those that perform customer centricity during good times share several structural features. These are not tactics — they are design choices that compound over time.

• Customer insight embedded in decision-making, not reported to it. The difference between an organisation that commissions quarterly customer research and one that has customer insight woven into weekly operational decisions is enormous. The former treats the customer as an input to strategy; the latter treats the customer as a continuous constraint on every decision.
• Cross-functional journey ownership. Assigning a single owner — typically a CX or Marketing function — to the customer journey without giving that owner authority over the contributing functions is a structural failure. Effective CX governance requires that journey ownership carries real accountability, including the ability to challenge operational decisions that degrade the experience.
• Feedback loops that close. A customer feedback management system that collects data and reports it upward is not a feedback loop — it is a monitoring system. A genuine loop requires that feedback triggers specific actions, that those actions are tracked, and that the customer is informed of the outcome. Closing the loop is both operationally important and a trust-building signal in its own right.
• Employee experience as a leading indicator. Customer-facing employees who are disengaged, under-equipped, or incentivised on the wrong metrics will not deliver customer-centric experiences regardless of what the strategy document says. The employee experience is the upstream determinant of the customer experience — this is not a motivational claim, it is an operational one.
• Long-term value metrics alongside short-term revenue. Organisations that measure customer lifetime value, retention rates, and referral behaviour alongside quarterly revenue targets make structurally different decisions than those that do not. The customer-centric strategy is almost always the one that sacrifices short-term margin for long-term relationship quality — and that trade-off only gets made consistently when the long-term metrics are on the same dashboard as the short-term ones.

How to Improve Customer Centricity: A Practical Sequence

For organisations that have diagnosed the gap and want to close it, the sequence matters as much as the actions. Implementing customer centricity as a wholesale transformation programme tends to stall. Implementing it as a sequence of structural changes — each one building the capability for the next — tends to hold.

1. Map the current state honestly. Before designing the future, understand what the organisation actually delivers today — not what it intends to deliver. A rigorous customer journey mapping exercise, conducted with real customer data rather than internal assumptions, typically surfaces a significant gap between the designed experience and the lived one.
2. Identify the structural causes of the gap. Most experience failures are not front-line failures — they are upstream design failures. A process that forces a customer to repeat information across channels is not a training problem; it is a data architecture problem. Fixing the symptom without addressing the cause is the most common reason CX improvement programmes produce temporary gains and then plateau.
3. Establish cross-functional accountability. Assign specific journey stages to specific functional owners, with clear metrics and review cadences. This is where governance design earns its value — not in the creation of a CX committee, but in the structural connection between customer outcome data and operational decision-making authority.
4. Build the measurement infrastructure. Instrument the journey so that experience data is continuous, not periodic. This does not require large technology investment at the outset — it requires clarity about which signals matter and a commitment to acting on them.
5. Align incentives. Review what behaviour is actually rewarded at every level of the organisation. If front-line staff are measured on throughput and managers are measured on cost, the organisation will optimise for throughput and cost regardless of what the customer centricity strategy says. Incentive alignment is the last step because it requires the credibility of the previous steps to be politically viable — but it is the step that makes the transformation durable.

The Organisational Design Question HBR Keeps Returning To

Across the HBR canon on customer centricity — from Gulati's structural argument to subsequent work on customer-centric leadership and organisational design — one question recurs: is the organisation built around what it sells, or around the customers it serves?

This is not a rhetorical question. It has a structural answer. A product-centric organisation has P&L lines organised by product, leadership titles that reference products, and success metrics that measure product performance. A customer-centric organisation has P&L lines that, at least in part, reflect customer segments or lifetime value pools, leadership accountability that spans the customer journey, and success metrics that include customer outcomes alongside financial ones.

Most organisations sit somewhere between these poles. The practical work of customer centricity best practices is not to achieve some theoretical ideal state — it is to move deliberately along that continuum, making structural choices that shift the organisation's default orientation from inside-out to outside-in.

The organisations that have done this most effectively share one further characteristic: they treat customer centricity as a permanent discipline rather than a transformation project. Projects end. Disciplines compound. The question is not whether to launch a customer centricity initiative — it is whether to build an organisation that structurally cannot make decisions without asking what they mean for the customer.

That is a harder question than it sounds. It is also the only one worth asking.

If you want to understand where your organisation currently sits on that continuum, the most honest starting point is a structured assessment of your CX maturity — not a survey of customer sentiment, but an audit of the structural conditions that determine whether customer centricity is possible at all. Renascence's customer experience practice is built around exactly that diagnostic, and the work that follows it.