Top CX Strategy Discussions Worth Following in 2026

Most CX strategy conversations are the same conversation recycled. Someone cites a well-worn statistic about the cost of losing a customer, someone else proposes a journey-mapping workshop, and the room nods. What's missing isn't enthusiasm — it's genuine intellectual friction. The discussions worth following are the ones where practitioners disagree, where a framework gets stress-tested against reality, and where the answer isn't obvious before the question is finished.

This article maps the debates that are actually moving the field forward in 2026 — not trend lists, but live tensions in how organisations think about customer experience strategy. If you lead CX, commission it, or are trying to build a career inside it, these are the conversations you should be in.

Why Most CX Strategy Debates Stay Shallow

The CX industry has a structural problem: its most visible forums reward consensus. Conference keynotes, LinkedIn posts, and vendor-sponsored research all tilt toward reassurance — "CX matters, here's why, here's how." The result is a field that produces enormous quantities of content and very little genuine argument.

The discussions that actually sharpen thinking happen in smaller rooms: internal strategy reviews where a CFO pushes back on the business case, academic journals where the measurement assumptions behind NPS get examined, and practitioner communities where someone is willing to say "that framework didn't work and here's what happened instead."

The debates below are drawn from those harder conversations. Each one has a real tension at its centre — not a question with an obvious answer, but a genuine fork in the road where intelligent people land differently.

Is NPS Still the Right Anchor Metric — or Has It Become a Management Comfort Blanket?

Net Promoter Score has been the dominant metric in CX strategy for two decades. It is simple, comparable across business units, and easy to report upward. It is also, increasingly, the subject of serious methodological challenge.

The core critique is not that loyalty measurement is wrong — it is that a single survey question, asked at a single point in time, cannot carry the weight organisations place on it. Researchers including Timothy Keiningham and colleagues published work in the Journal of Marketing examining whether NPS outperforms other satisfaction metrics in predicting actual growth, and found the relationship considerably more complicated than the original claim suggested. The debate has never fully resolved, but it has forced a more honest conversation about what any metric can and cannot do.

The more interesting practitioner question is what happens when NPS becomes a target rather than a signal. Goodhart's Law — the observation that when a measure becomes a target, it ceases to be a good measure — applies with particular force here. Teams learn to survey selectively, to time outreach after positive interactions, or to coach customers before they respond. The score improves; the experience does not.

"The metric isn't the problem. The problem is treating a lagging indicator as if it were a management lever — and then being surprised when the lever doesn't connect to anything."

The productive version of this debate is not "NPS versus CSAT versus CES" — it is about building a measurement architecture that triangulates rather than consolidates, and that keeps the signal honest by separating the team that owns the experience from the team that reports on it. A well-designed Voice of Customer strategy treats metrics as a portfolio, not a single score to defend.

Does Personalisation at Scale Actually Improve Experience — or Just Increase Surveillance Anxiety?

Personalisation is the dominant promise of CX technology investment right now. The argument is intuitive: if you know more about a customer, you can serve them better. The reality is more complicated, and the conversation around it is becoming sharper.

The behavioural mechanism matters here. Personalisation works when it reduces effort — when the system anticipates what you need before you have to ask. It backfires when it makes the customer aware of how much data has been collected, triggering what researchers call the "creepiness effect": a sudden, visceral discomfort that damages trust more than a generic experience would have. The affect heuristic is at work — a negative emotional signal overrides the rational recognition that the personalisation is technically helpful.

The B2B version of this debate is particularly live. In B2B customer experience, personalisation often means account-level intelligence — knowing the client's strategic priorities, their internal politics, their renewal timeline. Done well, this is indistinguishable from good relationship management. Done clumsily, it reads as manipulation. The line is thinner than most technology vendors acknowledge.

The discussion worth following is not "how do we personalise more" but "where does personalisation add value versus where does it add friction of a different kind?" That requires a much more honest audit of where data-driven intervention actually improves outcomes versus where it simply feels impressive in a product demo.

Is Employee Experience Upstream of Customer Experience — or Is That Just a Convenient Story?

The claim that employee experience drives customer experience has become close to axiomatic in CX circles. It is repeated so often, and with such confidence, that it has started to function less like an insight and more like a slogan.

The underlying mechanism is real. Frontline staff who feel supported, trusted, and equipped are more likely to exercise discretion in a customer's favour. They are less likely to be cognitively depleted — a state that, as Daniel Kahneman's work on System 1 and System 2 thinking makes clear, pushes people toward automatic, low-effort responses rather than considered ones. A burned-out agent defaults to the script; an engaged one reads the room.

But the relationship is not automatic, and the debate is about how direct the link actually is and under what conditions it breaks down. High employee satisfaction scores in a contact centre do not automatically produce high customer satisfaction scores if the processes those employees are working within are broken. A happy team following a bad script is still a bad experience. The honest version of the EX-CX argument is that employee experience is a necessary but not sufficient condition — and that organisations sometimes use it as a reason to focus on culture while avoiding the harder work of process and system redesign.

The productive question is: what specifically about the employee experience is connected to which specific customer outcomes? That requires a more granular analysis than "our people are our greatest asset." Renascence's work on employee experience treats this as an empirical question, not a values statement.

Should CX Strategy Be Owned by a Central Function or Embedded Across the Business?

This is one of the most practically consequential debates in the field, and it rarely gets the direct treatment it deserves because it is fundamentally a political question dressed as an organisational one.

The case for a central CX function is coherence. Without a single owner, customer experience becomes the responsibility of everyone and therefore no one. Standards drift. Journey ownership fragments. The CX team at least holds the map, even if they don't control all the territory.

The case against is equally strong. A central CX team with no budget authority and no line management over the functions that actually deliver the experience is a team that produces recommendations. It can influence, advocate, and measure — but it cannot compel. And in most organisations, the gap between a well-designed experience and the one customers actually receive is a governance gap, not a design gap.

"A CX strategy that lives in a PowerPoint and dies at the handoff to operations isn't a strategy — it's a wish list with a logo on it."

The emerging consensus — though it is contested — is that the answer is neither pure centralisation nor pure embedding, but a federated model: a small central team that owns standards, measurement, and the overall CX transformation agenda, with embedded CX capability in each major function that is accountable to both the function and the centre. This is harder to design and harder to sustain, but it is the only model that solves both the coherence problem and the authority problem simultaneously. A clear CX governance strategy is what makes the federated model work in practice rather than on paper.

Is Journey Mapping Still Useful — or Has It Become a Ritual That Substitutes for Action?

Journey mapping is the most widely used tool in the CX practitioner's kit. It is also, in many organisations, the most reliably inconclusive one. Teams spend weeks mapping the current state, produce a beautiful artefact, present it to leadership, and then watch it get filed. Six months later, a new team maps the same journey.

The critique is not that journey mapping is wrong — it is that it is often used as a substitute for the harder conversation about what will actually change and who is accountable for changing it. The map becomes the deliverable. The experience stays the same.

The discussion worth following is about what makes journey mapping actually drive action rather than just awareness. The practitioners who get the most out of it tend to share a few habits:

• They map to a specific decision, not to general understanding — "should we redesign the onboarding flow?" rather than "let's understand the customer journey."
• They include the service blueprint alongside the journey map, so the internal processes and system dependencies are visible at the same time as the customer experience — making it harder to admire the problem without confronting its causes.
• They assign a named owner to each moment of truth before the mapping session ends, not after.
• They treat the map as a living document with a review cadence, not a project output.
• They connect the map to a financial model — what is the cost of this friction point in churn, repeat contacts, or lifetime value? — so the prioritisation conversation has a basis beyond gut feel.

The goal-gradient effect from behavioural economics is relevant here: people work harder and faster as they perceive themselves to be closer to a goal. A journey map that shows the gap between current and desired state, with a clear roadmap of milestones, activates this effect. A map that simply documents the current state does not. The CX journey design work that produces lasting change is the kind that ends with a roadmap, not a report.

What Does Good CX Strategy Consulting Actually Look Like — and How Do You Tell It from the Expensive Kind That Doesn't Work?

This is the conversation that clients have privately and consultants rarely initiate. CX strategy consulting ranges from genuinely transformative to elaborately packaged common sense, and the external signals — firm reputation, slide quality, framework sophistication — are poor predictors of which you are getting.

The markers of consulting that actually works tend to be structural rather than stylistic. Does the engagement include a diagnostic phase that might produce an uncomfortable answer? Is the recommended approach connected to the client's specific operating model, or does it look like a template with the logo changed? Is there a clear theory of change — a specific account of how the recommended actions will produce the intended outcomes — or is the logic "best practice leads to better results"?

The B2B version of this is particularly important because B2B customer experience is genuinely different from B2C in ways that generic frameworks often miss. B2B relationships involve multiple stakeholders with different priorities, longer decision cycles, higher switching costs, and a much stronger role for the individual relationship alongside the institutional one. A framework built on consumer journey thinking will systematically underweight these dynamics.

The other marker is what happens after the strategy is written. A consulting engagement that ends with a strategy document and a handshake has, in most cases, produced a document rather than a transformation. The organisations that see lasting change are the ones where the consulting relationship extends into implementation — where the external team is present when the strategy meets the organisation's immune system and helps navigate the resistance rather than declaring victory before it arrives. This is precisely the kind of work covered under Renascence's CX consulting practice.

How Should Organisations Think About CX in an Era of AI-Mediated Interaction?

The most consequential live debate in customer experience strategy right now is about what happens to the experience when a significant proportion of customer interactions are mediated by AI systems rather than humans.

The optimistic case is well-rehearsed: AI can deliver consistent, fast, always-available service at a cost point that allows organisations to redirect human attention to complex and high-value interactions. The pessimistic case is equally familiar: AI systems fail in ways that are opaque and hard to recover from, and customers who encounter a bad AI interaction have no one to appeal to.

The more interesting and less-discussed question is about what AI-mediated interaction does to the emotional architecture of the customer relationship. The peak-end rule, identified by Daniel Kahneman, holds that people's memory of an experience is dominated by its most intense moment and its final moment — not its average. Human interactions, even imperfect ones, generate emotional peaks. AI interactions tend to be flat — competent, consistent, and emotionally inert. If most interactions become AI-mediated, organisations may find their aggregate satisfaction scores holding steady while the emotional connection that drives advocacy and loyalty quietly erodes.

"Efficiency and emotional resonance are not the same thing. Optimising for the former without accounting for the latter is how organisations build experiences that customers rate adequately and remember not at all."

The design question this raises is not "how much AI?" but "which interactions benefit from AI consistency and which ones require human emotional range?" That is a genuinely hard design problem, and the organisations working on it seriously are ahead of those still debating whether to deploy AI at all. For organisations wanting to understand where they stand on this and other dimensions of CX maturity, the CX Maturity Assessment provides a structured diagnostic across the building blocks that matter.

The Discussion That Ties All of These Together

Underneath each of these debates is a single, recurring tension: the gap between experience strategy as a design discipline and experience strategy as an organisational capability. The first is about knowing what good looks like. The second is about building the structures, systems, and culture that can consistently produce it.

Most organisations are better at the first than the second. They can describe the experience they want to deliver. They struggle to close the distance between that description and what customers actually encounter. The discussions worth following — on metrics, governance, AI, journey design, and the role of consulting — are all, at their core, about that gap.

The practitioners and organisations making real progress are the ones willing to sit with the discomfort of that gap rather than paper over it with a new framework. They are the ones asking harder questions: not "what is our CX strategy?" but "why does our strategy not survive contact with our operations?" Not "how do we improve our NPS?" but "what would have to be true about our processes and culture for that score to mean something?" For those ready to start with that kind of honesty, the customer experience strategy work begins not with a framework but with a clear-eyed look at where the distance between intention and reality is greatest — and why.

The best CX strategy conversations are the ones that make you uncomfortable. Follow those.