Tomas Lykke
Senior Partner
Executive summary
A customer experience strategy should explain why customers choose a business, what they can consistently expect from it and how those expectations will be met in daily work. The difficult part is connecting customer understanding to decisions about service, people and resources. At Eve, we start with the drivers of customer loyalty. We then translate the insight into a small number of customer promises, clear goals, practical service priorities and an action plan. Each element must reinforce the others. The strategy becomes valuable when leaders use it to make trade-offs, employees know what it changes in their work and customer outcomes are measured alongside commercial performance. Digital tools and AI can extend the experience, but they cannot resolve a promise the organisation has never made operational.
Start with what customers value
Customers can take their business elsewhere. That makes their experience a leadership matter, not simply a concern for marketing or customer service. Yet many organisations still express customer centricity as an ambition without specifying how it will influence their choices.
A customer experience strategy provides that direction. It should answer a practical question: how can the business improve loyalty in a way that creates value for customers and makes commercial sense? The answer begins with the customer’s perspective: the needs customers are trying to meet, the experiences that influence their decisions and the situations in which the current service falls short.
Driver analysis can show which attributes are most closely associated with satisfaction or loyalty across customer groups and products. Qualitative interviews add the context behind those patterns. Operational and commercial data reveal where the business can act and what an improvement may cost or contribute. These forms of evidence should be considered together. A low survey score alone does not establish an investment priority, and a vivid customer story alone cannot establish how widespread a problem is.
The resulting strategy normally brings together four elements: customer promises, goals and ambitions, service priorities, and an action plan. Its design should fit the organisation. Group strategy, business model, values and structure all influence which decisions the strategy must guide and how it should be developed.
Customer promises give the strategy its centre
The value proposition explains why a customer should choose the business. It describes the need the offering meets, the benefits it provides and the reason it is different from alternatives. Customer promises have a related but distinct role: they describe the experience that should reassure customers they made the right choice.
A useful promise expresses what a customer should consistently recognise when dealing with the organisation. It provides a shared point of reference for teams that otherwise see only their part of a journey. When employees understand the intended experience, they can make more coherent choices in sales, service, delivery and support.
Consider three illustrative promises: we communicate clearly; we give competent advice; we make it easy to get help. Each needs a specific meaning in the business. Clear communication may require timely explanations when a delivery changes. Competent advice may require a specialist to join a complex conversation. Easy access to help may depend on how a query is handed from one team to another. The promises become credible through those decisions, not through the wording alone.
Promises should be grounded in the value proposition and in the experiences that actually drive loyalty. Research needs to reveal what customers value most and which recurring points of friction can undo that value. If the organisation instead starts with assumptions or attractive language, the resulting strategy may direct investment towards an experience customers do not need.
Develop the promises with leaders and employees over several rounds. Bring customer findings into the room, explore the tensions in them and consolidate the themes into a small set of clear statements. The process should be demanding. A promise that can describe any competitor is unlikely to help the business decide where to differentiate. A promise that no one can translate into an action will struggle to survive contact with daily work.
Set goals that connect experience and economics
Customer goals give leaders a way to judge whether the strategy is working. The strongest goals link improvements in experience to the economics of the relationship, while recognising that customer and financial outcomes often move at different speeds.
At the strategic level, leaders may track overall loyalty and differences by segment or product. At the tactical level, they may examine churn by product, the share of customers with broader relationships, complaint incidence, first-time resolution, fulfilment of commitments and performance against customer promises at important touchpoints. Operational measures then describe what a team can influence directly in a particular journey.
The levels need to connect. A service team may improve the accuracy of a handover before that improvement becomes visible in retention. If the organisation measures only the final commercial result, it will learn too slowly. If it measures only activity, it may celebrate effort without improving the customer relationship.
Choose a manageable number of goals and define them precisely. Specify the customer group, the desired change, the baseline, the owner and the period for review. Targets should be achievable and relevant to the strategy, with an agreed way to interpret the result. This discipline makes customer measures useful in ordinary management decisions rather than a separate reporting exercise.
Translate promises into service priorities
Customer promises are directional. Service priorities describe the concrete actions that customers should experience across the business. They connect an intended feeling with a trigger, a response and a standard that employees can deliver and managers can assess.
If a business promises simplicity, a service priority could address a billing query that currently moves between departments. It might specify that the first team receiving the query owns its resolution, even when another function must provide the answer. A response-time commitment could be added where the customer need and operational capacity justify one. A 90-second phone threshold, for example, is an illustrative design choice, not a universal benchmark.
Keep the priorities selective. Several may support each promise, but a long list will dilute attention. Test whether each one applies to moments that matter to customers, can be understood across functions and has an owner. Service priorities should guide the design of journeys and processes, not sit beside them as a separate set of slogans.
They should also clarify where consistency matters and where employees need judgement. Some commitments should hold across every product and location. Others may differ by customer need, complexity or channel. The point is to make variation deliberate and understandable to the customer.
Make the action plan part of daily management
The strategy needs an action plan whether it is implemented through line management or a wider customer experience programme. Communication, capability development and management reporting all matter, but they work only when connected to actual decisions.
First, help employees interpret the promises in their own context. A central message can explain the direction, while teams in sales, operations, finance and service describe what each promise changes in their work. Ask them to identify situations where existing processes, targets or handovers prevent the intended experience. That discussion is more useful than a poster alone.
Second, develop the capabilities needed to deliver. Frontline staff may need to practise service recovery, difficult conversations or ways to recognise customers at risk of leaving. Back-office teams need to understand how their decisions reach the customer. Systems and information access should support those behaviours. Training has limited effect if an employee is asked to take ownership but lacks the authority or knowledge to resolve the issue.
Managers need attention as well. They shape what gets discussed in team meetings, how customer cases are reviewed and what good performance is recognised. Development conversations and coaching should reflect the customer strategy. Leaders also need time and a mandate to remove obstacles that one team cannot solve alone.
Finally, put customer goals and service priorities into regular management reporting. Give each measure an owner and a review rhythm. Executive leaders should see the strategic outcomes, while operational teams should have a small set of measures they can act on. The review must lead to decisions: what to improve, what to investigate and which commitment the business can no longer make credibly without changing its operating model.
The development process changes leadership thinking
A customer experience strategy should involve senior leaders and the extended leadership team across the relevant business units. Their involvement anchors the result, but the process also has value in its own right.
An outside-in view challenges familiar assumptions. Financial, operational and customer-driver evidence may show that a highly visible touchpoint is less important than a quiet, recurring source of friction. Different leaders may discover that they hold different beliefs about what customers value, what the company does well and where it fails.
Work through those differences openly. Establish a shared picture of the current experience and the few outcomes the business must protect. Then decide which promises to make, which service priorities deserve resources and which trade-offs follow. Leaders who participate in those choices are better placed to explain them, act on them in their own areas and sustain them after a programme ends.
The test of the strategy is what happens next. When promises shape processes, employee authority and investment, the business can deliver more consistent experiences. When goals connect customer outcomes with growth and cost, leaders can see whether that consistency creates value. As AI changes the speed and scale of interactions, that combination of customer understanding and disciplined execution becomes more important.
Senior Partner
Director, H&B