Linear journey maps break down when real customer experiences depend on messy, interconnected systems
The Pattern Behind Customer Experience Failures
Over the past six months, I’ve noticed something interesting. Across three different customer experience engagements — covering airline passenger journeys, retail logistics, and customer service operations — we’ve consistently reached for the same analytical approach, one that reveals why beautifully designed customer experiences can fail in practice. We’ve used it to map how operational roles interact, how customer data flows between systems, and how service decisions cascade through organisations. Each time, it revealed patterns that traditional customer journey mapping had missed entirely.
The approach? Systems thinking.
Here’s what makes this noteworthy: systems thinking isn’t new. It emerged in the 1950s, was popularised for business in the 1990s by Peter Senge’s The Fifth Discipline and has sold over half a million copies of Donella Meadows’ Thinking in Systems. Yet despite this pedigree, it remains surprisingly underused in customer experience (and other) work.
But I feel that’s changing. In September 2025, Harvard Business Review published “Why You Need Systems Thinking Now.” In November, Forbes argued that digital transformation and AI specifically demand systems approaches. Cornell’s 2025 Systems Thinking Conference drew over 9,000 participants, making it the largest thinking conference of its kind. And in March 2026, leading institutions representing different systems thinking methods will converge for the first time at Hull University.
The timing isn’t coincidental for customer experience professionals. Global investment in digital transformation is expected to reach $4 trillion by 2027, with a significant portion aimed at enhancing customer experience; however, up to 70% of these initiatives fail. The fundamental problem? Applying linear, siloed thinking to customer experiences that depend on complex, interconnected operational systems.
This disconnect has become critical as organisations race to integrate AI into customer experiences. While 88% of companies now use AI in at least one function, yet only about one-third have begun scaling across the enterprise. Most remain stuck in pilot mode, deploying AI chatbots, recommendation engines, and predictive analytics in isolation, without redesigning the operational workflows that actually deliver customer value.
Why Traditional CX Approaches Fail for Complex Transformation
The Customer Journey Mapping Trap
Most customer experience methodologies follow a familiar pattern: map the customer journey, identify pain points at each stage, design improvements for each touchpoint, then hand specifications to IT and operations to implement. This works when touchpoints are genuinely independent. If you’re redesigning your website checkout flow and it doesn’t depend on other systems, linear improvement is effective.
But what happens when customer experiences depend on interconnected operational systems?
Consider a recent airline passenger experience transformation. Traditional customer journey mapping would optimise each touchpoint independently: better booking experience, improved airport check-in, enhanced in-flight service, smoother baggage collection.
But we discovered that passenger frustration wasn’t caused by poor individual touchpoints. It emerged from the invisible coordination failures between operational teams. When a flight is delayed, the ground crew needs updates from crew planning, who rely on maintenance for status, which in turn depends on coordination with airport operations. Passengers experience this as “no one knows what’s happening” and “different staff tell me different things.”
The customer journey map showed the problem (inconsistent communication during disruptions), but it couldn’t reveal the root cause: operational teams working with disconnected systems, unable to coordinate because information that should flow doesn’t. Optimising each customer touchpoint independently would have made this worse, not better. Each touchpoint would have had better tools, but would still be disconnected from the broader operational reality.
The AI Personalisation Challenge
This trap becomes acute with AI-powered customer experiences. Organisations ask “Where can AI improve customer experience?” and get back a list of use cases: AI chatbots for service, AI recommendations for products, AI sentiment analysis for feedback, AI personalisation for marketing. Each sounds compelling for improving specific customer interactions.
But AI doesn’t just improve individual touchpoints, it creates new dependencies between systems. The AI chatbot needs access to order data, inventory systems, customer history, and agent notes. AI recommendations depend on accurate product catalogues, pricing systems, and availability data. AI personalisation requires connecting marketing platforms to transaction systems to service interactions.
Deploy AI at individual touchpoints without understanding these system dependencies, and you create new customer experience failures: chatbots that can’t access order status, recommendations for out-of-stock items, personalisation that contradicts service interactions, or worse, AI systems that give customers conflicting information because they’re drawing from disconnected data sources.
The Forbes article on digital transformation and AI puts it bluntly: without a systems approach, AI implementations become “another expensive failure in the transformation graveyard.” For customer experience, this means delivering AI-powered touchpoints that frustrate rather than delight.
Why This Matters for CX Professionals Now
Customer experience complexity hasn’t suddenly appeared. Omnichannel journeys have always involved multiple systems. What’s changed is the pace and interconnectedness of customer expectations. Customers expect real-time consistency across channels, personalisation that remembers context across interactions, and service that coordinates seamlessly behind the scenes. Linear CX improvement that optimises touchpoints in isolation can’t deliver these expectations because they fundamentally depend on operational systems working together.
What Systems Thinking Actually Means for Customer Experience
Peter Senge defined systems thinking as “a discipline for seeing wholes, as a framework for seeing interrelationships rather than things, for seeing patterns of change rather than static snapshots.”
That’s elegant but abstract. What does it mean when you’re actually designing and delivering customer experiences?
Three Core Shifts in CX Approach
First, relationships between operational capabilities become as important as customer touchpoints. In a recent customer service transformation, we didn’t just map what customers needed at each interaction; we also mapped how service agents relied on sales data, how sales relied on inventory visibility, and how inventory relied on timely updates from the supply chain. The operational dependencies created the customer experience constraints, not the other way around.
In a previous CustomerThink article, I explored how operational personas reveal the “backstage reality” that makes or breaks customer experience delivery. Systems thinking takes this further: it’s not just about understanding operational constraints, but about mapping how operational systems connect — and either enable or block — the customer experience you’ve designed.
Second, you look for feedback loops rather than linear customer journeys. Traditional CX analysis asks: “What causes this customer pain point?” Systems thinking asks: “What reinforces this pattern?” When customer service gets information late, interactions suffer. Those poor interactions trigger more complaints, which drive up volume, overwhelm agents, and push information even further behind. It’s a reinforcing loop that degrades the experience, not a single cause you can fix at one touchpoint.
Third, you design for how customer data and operational capabilities interact, not just what each delivers independently. A three-layer customer experience architecture (customer‑facing, orchestration, operational execution) isn’t three separate systems; it describes how customer interactions should trigger coordinated operational responses. Any change to the customer‑facing layer has to account for its impact on operational delivery, and vice versa.
The Practical CX Test
Here’s a simple way to tell if you’re thinking systemically about customer experience:
- Can you draw how customer data flows between the systems that deliver the experience you’ve designed?
- Can you identify what customer experiences break if you optimise one touchpoint without considering operational dependencies?
- Can you spot feedback loops where improving one customer interaction might make others worse?
- Can you trace how operational constraints cascade into customer experience failures?
If the answer is no, you’re probably still thinking in linear customer journeys rather than interconnected customer experience systems.
When Systems Thinking Actually Matters for CX (and When It Doesn’t)
Not Every CX Initiative Needs Systems Thinking
This is important: systems thinking isn’t always the right approach for customer experience work. Some improvements genuinely can be made at individual touchpoints without considering broader systems.
Redesigning your website navigation? If it’s truly a front-end change with no backend dependencies, standard UX methodology works fine. Updating email templates? Linear approach. Improving call centre scripts? Probably doesn’t need systems analysis.
The question isn’t “should we always think systemically about CX?” Instead, it’s “when does systems thinking reveal customer experience constraints that journey mapping misses?”
Three Clear Triggers for CX Professionals
Systems thinking becomes critical for customer experience when:
- Customer experiences depend on cross-functional coordination. If delivering the experience requires sales, service, operations, and logistics to work together, you’re dealing with a system. You can’t optimise the customer’s experience by function because the customer doesn’t experience functions; they experience the orchestrated (or uncoordinated) outcome.
- Customer data needs to flow between multiple systems. AI-powered personalisation, omnichannel consistency, and real-time service all require customer data to move seamlessly between systems. You’re not just adding features. You’re connecting data flows between marketing platforms, service systems, transaction databases, and customer profiles. The World Economic Forum’s recent work on AI governance emphasises this: you can’t secure customer data and deliver AI experiences through separate workstreams because they’re inherently interconnected.
- Changes in one channel reliably ripple into others. In a recent retail transformation, we mapped how online ordering choices affected in‑store fulfilment, which shaped delivery promises, which altered returns handling, which fed back into satisfaction and future channel preference. Linear customer journey mapping would miss these cross-channel feedback loops entirely.
The Recognition Test for CX Leaders
If you find yourself saying ‘yes, but operations can’t deliver that’ repeatedly during CX design, that’s a signal. The operational constraints aren’t scope limitations. They’re system interdependencies that need to be designed for, not designed around.
If different operational teams keep highlighting conflicting requirements for the same customer experience feature, that’s another signal. The conflict usually isn’t about requirements. It’s about different parts of the operational system needing different things from shared customer data or processes.
What Comes Next
Understanding why systems thinking matters for customer experience is one thing. Building the capability to actually apply it when designing and delivering CX transformations is another.
In Part 2, I’ll explore the practical reality of developing systems thinking as a customer experience capability: what the skill gap actually looks like for CX professionals, how to build the capability beyond just learning frameworks, and what this means strategically for organisations navigating customer-centric transformation.
Because in a world where 70% of transformation initiatives fail due to linear thinking applied to complex customer experiences, systems thinking isn’t just an analytical technique for CX professionals.
Systems thinking is becoming essential for delivering customer experiences that actually work in operational reality.
References
Bansal, T. & Birkinshaw, J. (2025). “Why You Need Systems Thinking Now.” Harvard Business Review, September-October 2025.
Cushnie, K. (2025). “Why Digital Transformation And AI Demands Systems Thinking.” Forbes, November 2025.
McKinsey (2025). “The State of AI in 2025: Agents, Innovation, and Transformation.” November 2025.
Meadows, D.H. (2008). Thinking in Systems: A Primer. Chelsea Green Publishing.
Senge, P.M. (2006). The Fifth Discipline: The Art and Practice of the Learning Organisation. Doubleday.
AI Disclosure
This article was developed through collaboration between human expertise and AI assistance. The core insights, real-world examples from customer experience consulting engagements, and strategic perspective come from my 25+ years of transformation consulting experience. AI was used to research current trends, identify relevant citations, structure arguments for clarity, and refine prose. All analytical frameworks, client examples, and practical recommendations reflect actual consulting work and professional judgement.