Nobody Is Paid to Care

Reinventing consumer centricity, part 2: Empathy as organizational infrastructure

Last week, at a leadership day we helped design for a large Swiss financial group, some 160 senior leaders sat in front of an empty stage. On it: a single chair. For a quarter of an hour, nobody spoke to the room. Instead, the room listened to voices. Real customers, unnamed and unexplained, talking about their lives. About raising four children alone. About wanting to take a holiday with a child, for once. About the feeling that life has quietly become unaffordable.

And then one voice said a sentence that has not left me since: “I appear in no statistic. I’m in no book either.”

You could feel the room shift. When the leaders were asked afterwards what these voices demanded of them, the answers filled the screen faster than anyone could read them. Attention. Honesty. Time. Respect. The willingness was overwhelming, and I do not doubt for a second that it was real.

Which is exactly why I want to say something uncomfortable about it.

The question I carried out of that room

Who in your organization is paid to care about customers?

Not to serve them. Not to convert them, retain them, or process them. Paid to care: rewarded for understanding a customer better, recognized for acting on that understanding, promoted for it.

Walk your org chart with that question and watch it come apart. Sales is paid to close. Marketing is paid to convert. Product is paid to ship. Operations is paid to reduce cost per case. Finance is paid to protect margin. Compliance is paid to avoid risk. Even the customer insights team, the people professionally closest to your customers, are paid to produce research. Nobody is paid to believe it.

And caring? Caring is voluntary. Worse: it usually costs the person who does it. The advisor who takes an extra half hour with a recently widowed client misses her call targets. The product manager who delays a launch because customers do not understand the pricing gets to explain himself to the steering committee. The analyst who insists that one number in the deck hides a human being is told, kindly, to stick to the storyline.

In most organizations, empathy is a donation. Employees give it out of their own pocket, and the organization quietly collects the returns.

The topic nobody dares to name

Here is what makes this more than one company’s morning. In the past months, a car rental company, a retailer, a consumer goods group and a luxury hotel chain have each come to me circling the same subject. What strikes me is that some of them no longer dare to call it customer centricity. The word feels worn to them: announced too often, delivered too rarely. Customer centricity has become one of those unflushable topics, declared solved and returning anyway every few years, slightly embarrassed to be back.

I find the embarrassment revealing. Topics return for one of two reasons: they are either fashion or unfinished. This one is unfinished for a natural, almost forgivable reason. Organizations get busy with themselves. Transformations, reorganizations, cost rounds, now AI. Every internal priority is a small, reasonable step away from the customer, and the steps add up. Nobody decides to abandon their customers; they just stop deciding not to.

And when the word does survive, the conversation often escapes into a second refuge: the definitional debate. Who is the customer, actually? The end consumer or the end user? Surely not the shopper. Or is it the distributor, who technically buys from us? What about the brokers? The other stakeholders? The shareholders? And let us not forget the internal client. I have sat through many of these debates, and I have started to hear them for what they mostly are: a polite filibuster, a sophisticated way of not talking about a real person.

One executive at that leadership day ended the debate from the stage in a single sentence: last time he checked, a circle can only have one center. There is exactly one customer, the one who pays in the end. Everyone else is a channel, a stakeholder, or a colleague. If your organization needs a workshop to establish who sits at the center of its universe, that is not a definitions problem. It is a distance problem.

The topic keeps coming back because the capability was never built. Which raises the question of why we keep failing to build it.

We did this to ourselves with one word

Soft.

Somewhere along the way, we filed empathy under soft skills, and the filing decided the funding. Soft skills get workshops. They get a module in the leadership program, a persona poster in the hallway, an annual survey with a heartfelt all-hands. They get, in other words, budgeted like sentiments. And sentiments are the first thing a difficult quarter deletes.

We have run this experiment before, and we know how it ends. Quality was once a soft concern too, a matter of craftsmanship and good intentions, posters in the factory. It stopped being soft when it became statistical process control, inspection gates, and a cord any worker could pull to stop the line. Safety was appeals and warning signs until it became systems, and then it became culture, in that order. No executive today would call quality a soft skill. It earned its hardness by being built into the operating model.

Empathy in 2026 is where quality was decades ago: a poster on the wall and a department down the hall. We call it a soft skill, so we build it soft. Then we act surprised when it does not scale.

See. Believe. Act.

The day I described ran on a simple arc, which I borrow here with gratitude: see your customers as they are. Believe the insight together. Act on it.

Follow that arc through your own organization and notice where it thins. Seeing, we have industrialized: research budgets, panels, trackers, more customer data than any generation of managers before us. Believing happens occasionally, in rooms like that one, when a voice cuts through and a team recognizes something as true, together. But acting is where the arc quietly dies. Because seeing is a budget line. Believing is a meeting. Acting is a career decision, and it is the only step of the three that costs the person who takes it.

I can already hear the objection, from friends whose judgment I trust: that the real bottleneck is believing, not acting. That once a team genuinely believes an insight, action follows almost on its own, incentives or not. They are not entirely wrong, and believing deserves an article of its own; it will get one. But I have watched too many genuinely believed insights die somewhere between the workshop and the operating model. Belief moves people. Infrastructure moves organizations. This piece is about the second, precisely because it is the part we keep skipping.

An organization that funds the first step, hopes for the second and taxes the third has not built a capability. It has built an alibi.

What paying to care would look like

I am not talking about a bonus for smiling. Building empathy as infrastructure means wiring the organization so that understanding customers is rewarded, usable, and hard to ignore. Five places to look:

• Mandate and decision rights: A question a colleague passed on to me last week has stayed with me: where is the mandate for the customer team to have a voice in decision making? Most insights teams are in the room by invitation, when someone remembers to ask. A mandate puts them there by charter. Decision rights give the seat teeth: someone can say “the customer would not want this” and stop a launch, a price change, a script, on evidence, without career damage. The test is whether anyone can recall that happening. A seat without a veto is decoration.

• Plumbing: Customer signal reaches decision makers without being requested. Not a quarterly readout: a flow. And be honest about what your dashboards carry: they record that a policy lapsed, not the resignation behind it. The man from the opening said it better than any data strategist I have met: he appears in no statistic. Left to themselves, dashboards delete exactly the information empathy runs on. The honest metric here is latency, the time from a customer’s pain to a changed decision. Almost nobody has ever measured it.

• Rituals: Contact with customers that happens on a schedule, not by inspiration. A standing hour listening to service calls. A real customer story opening every leadership meeting. A rule that no quarterly review begins before the room has heard a voice nobody can average away. Rituals sound ceremonial; they are the opposite. They make seeing customers independent of anyone’s mood, calendar, or memory. The day I described was such a ritual. The harder question is what its weekly equivalent looks like in your organization.

• Incentives: Understanding shows up in what gets bonused, promoted, and celebrated. Imagine a meaningful slice of every leader’s variable pay depending on demonstrating that they understand their customers better this year than last. Notice how radical that feels, given what your strategy deck says. And it is not utopian: one global consumer goods group promotes nobody in a commercial function without twenty documented hours spent with customers. In years of asking around, it remains the only example of its kind I have collected. Which is rather the point.

• Leadership reflexes: Leaders who consume their own products and notice their own behavior as customers: who call their own hotline, sit through their own onboarding, try to cancel their own subscription. And who then bring that noticing into the meeting, where it gives everyone else permission to take the human seriously. I wrote about this last time: the most honest consumer lab you will ever visit is your own week. It is where the capability starts. It is emphatically not where it scales.

“You cannot pay people to care”

I know the objection, and it is half right. You cannot buy the feeling. No incentive plan has ever produced a moment of genuine human recognition, and a company that tries to manufacture warmth produces something worse than coldness.

But look again at that room. The willingness was already there. A hundred and sixty leaders, visibly moved, ready to act. The feeling has never been the bottleneck. The bottleneck is that between the feeling and the action stands an operating model that taxes caring at every step: targets it works against, meetings it slows down, careers it does not advance.

Infrastructure does not manufacture care. It stops punishing it. That is the whole idea, and it is enough.

Everyone’s business is nobody’s job

Two more details from that day. The group had done the seeing properly: cross-divisional teams had spent the whole summer getting close to its growth segments, and the day was where their findings met the wider leadership community. And two thirds of the leaders in that room work in functions with no direct customer contact at all. The stated ambition, and I think it is the right one, was that customer insight is everyone’s business. Whether you serve customers or serve the colleagues who do, your decisions eventually land in a customer’s life.

But in an incentive system, everyone’s business is nobody’s job. “Everyone’s business” becomes real at exactly the moment it enters somebody’s objectives, somebody’s stage gate, somebody’s agenda. Until then, it is a value. And values, unlike capabilities, do not survive contact with a quarterly target.

This is why I have stopped believing in customer centricity as a culture initiative. Culture is what infrastructure teaches people to expect. Build the mandate, the plumbing, the rituals, and the incentives, and the culture will follow them. Hang up posters instead, and the culture will follow the incentives you actually have.

The five-minute test

A reflex that lives in one leader’s head, however genuine, leaves the building every evening. It gets overruled by quarterly pressure. Eventually it retires, or resigns, or simply gets tired. If the last piece in this series argued that consumer understanding starts with you, this one argues that it must not end there. Empathy is not a soft skill. It is the hardest capability an organization can build, precisely because iit only scales as infrastructure: mandated, wired in, practiced, paid for, measured.

So here is a test that takes five minutes. Open next year’s incentive plan. Look for the line that rewards anyone, anyone at all, for understanding a customer better. If you find it, write to me: you would be the second example I have ever collected. If you do not find it, then your organization has already answered the question at the top of this article. Caring, where you work, is a donation.

And donations are not a growth strategy.

Tell me why I am wrong. I mean it: the strongest objection gets picked up in the next piece of this series.