Efficiency and Experience Are One Investment, Part 2: One Budget

"Tell me how you measure me, and I will tell you how I will behave." Eliyahu Goldratt

Part 1 described how insurers came to fund efficiency and customer experience as separate programs and what that costs. This part looks at the evidence and at what changes when the two are treated as one investment.

What the Data Says About the Overlap

The overlap is not only a theory. McKinsey's model of a digitized auto claims journey reports both outcomes from the same redesign: net promoter score up 10 to 15 points and claims adjustment expenses down 20% to 30%. The redesign reduces handoffs, speeds up decisions, and delivers more consistent claim outcomes, and those changes produce both results.

From an operations perspective, these improvements lower expenses. From a business perspective, they improve customer satisfaction and retention. The value is the same. Only the way organizations choose to look at it differs.

Why the Core Platform Is Where This Gets Decided

This argument lands on the core platform, rather than on culture or governance, because it is the only place where both agendas physically touch the same data. A policy record that underwriting, billing, servicing, and claims all read from and write to is the precondition for internal efficiency. It is also the precondition for a customer who is not asked to repeat themselves. There is no version of one without the other.

That is why the portal built beside the core system fails while the portal built on it succeeds. It is why analytics programs stall for eighteen months on data preparation when the underlying records were never unified. And it is why the choice of core system is a strategic decision rather than an IT procurement, however it appears on the capital request.

The implication for carriers running fragmented estates is that neither agenda is fully available until the core question is settled. Improvements at the edges can be bought for years without touching the source of the constraint. Many organizations have done exactly that, which is why their satisfaction scores and expense ratios have both proven stubborn.

What Changes If You Fund It as One Thing

Four practical shifts follow from treating this as a single investment.

Build the Business Case on Both Ledgers. Most core platform business cases are written entirely in expense terms, because that is the language the sponsoring function speaks. That undersells the investment and shapes the implementation. A program justified purely on cost will sequence internal workflows first and defer customer-facing surfaces, which is the sequencing that produces disconnected portals later. Put retention, quote conversion, and complaint volume into the same case as handling time and straight-through processing rate, and the sequencing decisions change with them.

Measure the Handoff, Not the Function. Functional metrics hide the problem. Claims measures cycle time within claims. Service measures resolution within service. Nobody owns the seam between them, which is where customers experience delay. Instrument the end-to-end journey from first notice to settlement, or from quote request to bind, and the shared nature of the two agendas becomes visible in the reporting. Anything measured only within a function will be optimized only within a function.

Make Communication Part of the Automation. In the claims triage example, efficiency gains are captured internally and never reach the policyholder, because notification was scoped as a communications task rather than a workflow step. If an automated decision does not trigger an automated update, half the value of the automation stays inside the building. Building the notification into the workflow, rather than into a separate campaign tool, is a small design choice with a disproportionate effect on whether the investment shows up in customer metrics.

Give the Journey a Single Owner. If no individual is accountable for the whole journey, the seams belong to nobody by design, and no platform capability will compensate. Ownership does not require reorganizing the company. It requires one named person with the authority to arbitrate between functional priorities when they conflict, and a mandate written in journey terms rather than functional ones.

The Counterargument

Some efficiency work has no customer-facing dimension. Reinsurance reporting automation does not touch a policyholder. Some experience work does not pay back operationally. A brand campaign does not reduce handling time. Not everything collapses into one investment, and a leader who insists otherwise will justify projects with benefits they cannot evidence, which erodes the credibility of the whole argument.

There is also a sequencing objection with real force. Core platform replacement is expensive, slow, and risky, and an organization under competitive pressure may reasonably choose visible edge improvements first while it builds the case for the harder work. That is a defensible decision. It becomes indefensible when the temporary choice quietly becomes the permanent strategy, which is the more common outcome.

Those are the edges and the timing. The center of the operating model, which is policy administration, underwriting, servicing, and claims, does not divide into a cost half and an experience half. Pretending that it does has produced a generation of programs that delivered against their own scorecards while customer experience stayed flat and the expense ratio moved a fraction of what was promised.

The question worth asking in the next planning cycle is not which of the two initiatives to fund. It is why they were ever presented as two.

Contributed by Faheem Shakeel, VP for Insurance, Damco Solutions.

← Previous: Part 1