Perspectives - 05 · IXA
Interlocking Architecture: How Structural Context Brings Every Layer to Life
Every team focuses on its particular stretch of the journey. Almost no one has the macro end-to-end view.
By Luke Miles · Global CXO, geniant
The problem
Why does a well-run organization still feel disjointed?
Most large organizations don't have one true view of the journey their customers and employees take. They have several. Each team sees its own stretch of the experience clearly, and none of those views are wrong. They just don't join up through a single lens.
The cost of this is often visible at the handovers, or through a disjointed conversation between customer and brand: repeating key information to the next person in the chain, or when a decision is made during one stage of the journey, which inadvertently makes the next stage harder. Each team can be doing its job well, but the experience still comes apart at the seams.
Luke Miles, Global CXO at geniant, has seen this from both sides, first as a client-side employee during large change programs and later as a consultant. His answer is the Integrated Experience Architecture, or IXA: a single blueprint of the whole journey, built around how key moments relate to each other. AI makes this interlocking architecture more urgent, because it can act on any moment in a journey and needs to know what surrounds it.
Several views, no single lens
“Thinking in isolation creates hairline fractures and unforgiving seams across the journeys we all take.”
Luke Miles
The blueprint
IXA: one blueprint for the whole journey
IXA helps a business understand the full context of an experience across the customer, the operation, and the employee, and how physical, human, and digital elements can come together to support each moment. In practice, it is a detailed blueprint.
That journey can be narrow, like the experience of being in a car for a set stretch of time. Or it can be broad. In aviation, for example, it runs from first awareness through advertising to booking a ticket, packing a bag, moving through the airport, and boarding the aircraft.
For each moment, the blueprint asks where the customer is functionally and emotionally, what their attitude and behavior are, and where there is an opportunity to design out friction. Teams also get a shared language for three things. Friction points are where the experience works against the person in it. Signature moments are peaks of excellence that are unmistakably on brand and stay in a customer's memory. Service recovery is what happens when something goes wrong. If a bag is lost in an otherwise smooth airport experience, how does the organization turn that into something positive?
One airline journey, six moments
The framework
IXA as a framework
Unlike a feature, which is built into a product, IXA is a tool any organization can deploy, and it shows most clearly how the moments in a journey interrelate and compound over time. It maps every moment at a chosen level of fidelity, then works through each one to see how it could be improved.
That matters more with AI. Because AI can augment a moment or take it over entirely, you need to know how you are deploying it and what surrounds it. Luke's analogy is the orchestration of music: you need to know how each instrument works together to build the whole, what the tempo is, and how the piece feels end to end, which means context is critical.
Going AI-first makes sense, but the system has to be mapped before the technology goes in. Agents can't just be layered on top of a system nobody has mapped, and this can lead to negative compounding. An agent supporting staff on an airline journey needs to know what is happening at that moment, how the staff are reacting, and where the customer is. Without that context, it can fall over.
Every moment, across every layer
Handovers
What happens when moments are treated in isolation
Take an airline journey: the app, the call center, check-in, security, the lounge, boarding. Each stage often runs in a slightly siloed way, with no view of the customer's emotional state as they move across spaces. Yet how a call center agent treats a customer directly affects the colleagues further down the journey. A lounge experience sets the customer up for boarding, which essentially makes each stage a handover.
When nobody can see those handovers, fractures appear. When everyone understands their place in the journey, they serve the customer well and also create a chance for greater onward continuity. That takes a master blueprint everyone can look at, so a person working in one section can see what it means for the people further down the line, for the digital layer, or for an AI agent working alongside them.
At the level of whole journeys and organizations, Luke describes the failure as less a dramatic break than a misfire, where the organization isn't getting the most out of everyone delivering to the customer. Closer in, where a team is working at the level of AI flows or wireframes, a misfire can show up very quickly.
Inside out
Inside out: the employee journey counts equally
IXA maps the employee journey with the same rigor and care as the customer journey, so there is greater symmetry. Where is the employee under high pressure? Where are they understaffed, or not supported by the technology they need? Reading the two journeys side by side lets a team design out these internal challenges before they show up in the external experience.
Signals
How to tell when context is missing, even when things look fine
Large organizations work, just not always seamlessly. The tell usually shows up when someone walks the journey as a customer would. The classic one is a conversation that doesn't continue: you explain a tricky connection to one person, and the next one in the chain has no idea, so you're forced to re-explain it. Critical knowledge that could pass from one customer-facing agent to another is lost.
Training is another signal. Staff who are equipped to read a customer, and to be preemptive and empathic, deliver far better service. Gaps across the journey often come down to how well staff were equipped.
The work starts with careful mapping. Populate the framework, get as granular as possible to understand what is happening where and when, then interview customers, staff, and stakeholders, and walk the journey yourself. The step that makes it most useful is synthesis: turning all those perspectives into something the team can solve against.
The trade-off
Tightening the right moments
Tightening a journey for efficiency is not always the same as improving it, and IXA's job is to show which moments to tighten, why, and when.
For example, an airline on a cost drive often makes cuts to amenities and crew headcount to help create broad efficiencies. However, there can be small moments that actually have larger “emotional footprints” for the customer. These need to be treated with greater care and attention, but may not be visible when viewed as part of a broader cost drive.
“Without knowing what's meaningful to the customer and the employee, you can miss an opportunity to re-shape a moment so you retain impact, but in a more cost-effective way.”
Luke Miles
That is why the blueprint tracks the emotional arc of the journey, with a neutral midpoint, so that moments that land well sit above the line and moments that don't sit below it, which helps visualize the emotional buoyancy of the customer and employee. Cost reductions can then be weighed against how the customer feels, instead of quietly spending down loyalty and trust.
Where a journey stops landing
Depth
How deep is deep enough
IXA reads from macro to micro. Each moment can carry multiple layers: the journey moment itself, such as pre-purchase education or digital discovery, then the customer's behavior and emotional state, the opportunity to intervene intentionally, the signature moment, the service recovery mechanic if things go wrong, and the AI layer. That AI layer can be fully autonomous and zero touch, or assisted, with a human in the loop and the AI acting as a co-pilot.
Any of those layers can be expanded into more detail. But there is a limit: go so molecular that the people it is meant to help can't use it, and it stops being useful. When a moment turns out to matter far more than the others, the better move is to break it out into its own brief, run by its own team, while IXA stays as the origin of truth for the full journey. The sub-briefs and sub-workflows all ladder up into the top-layer blueprint. This also helps with investment planning, because teams can see what will be completed where and what each piece costs.
The structure works across sectors because every journey unfolds over time. Picture a timer running across the journey, with specific moments coded along it. In healthcare, that timeline might stretch across long waits for diagnosis or treatment. For buying a first home, it might span months, and a bank or mortgage broker could intervene at clever moments along the way. The layers can expand and the journey can be linear or cyclical, but there is always a chronology.
Conclusion
Where this leads
“Context is critical, even more so now with the advent of AI. Because AI is so powerful and it can do so much, you need to know where you're deploying it, how you're deploying it, and why you're deploying it.”
Luke Miles
Context is all about relationships: across the journey, between technology, people, space, and product, between the customer and the employee, and between the employee and the business. IXA gives a team a high-fidelity view of the journey from end to end and inside out, so that judgments and interventions happen at the right moment, with the right spend, in the right context.
As tools, journey maps are not new, but with the advent of AI, teams are now taking another, fresh look at them.
Next in the series
Dynamic Symbiosis
Once the structure is in place, the next question is how intelligence is embedded in the workflow itself: continuous feedback loops from customer to employee to organization, with AI acting as connective tissue. In that role, AI relieves cognitive load on the front line and lets an organization spot where things are falling over and fix them in real time.
← All Perspectives