The missing link between data and better decisions
AI doesn't resolve misalignment. It operationalizes it.
In this Insights episode of The Experience Edge, Jochem van der Veer opens with a story from inside Lufthansa. The ancillary team saw baggage revenue drop and did everything right: root cause analysis, roadmap space, solution design. They were close to shipping a fix for a problem that didn't exist. A promotion launched upstream had included a free bag. Revenue hadn't disappeared, it had moved. Without shared context, they nearly optimized hard for a measurement artifact. The episode builds from that story into a case for why context is infrastructure, and why adding AI before you have it only accelerates fragmentation.
Main takeaway: Fragmented context isn't a coordination problem. It's a structural risk. When you automate before aligning, you don't get faster insights. You get faster fragmentation. Shared context anchored to the customer journey is the only thing that fixes it.
The data myth
Most organizations assume CX scales with more visibility: more metrics, more dashboards, more feedback loops. It doesn't. The problem isn't data shortage. It's context shortage.
Ask five teams what "friction" means and you'll get five different answers, all correct inside their own model of reality:
Support: customers are confused
Product: adoption is low
Ops: cycle time is too high
Finance: margins are shrinking
CX: scores are down
Everyone is right. Nobody is aligned.
AI amplifies the gap
CX teams feed tens of thousands of survey rows into an AI model, expecting insight to come out the other side. Topics emerge. They look plausible. But AI reflects the structure that's already there, not the meaning that's missing.
If the input is unstructured or siloed, the output is too. Apply that across teams using different classification systems and you don't just have silos. You have siloed systems running at machine speed.
The fix isn't a better journey map
Building shared context isn't a taxonomy project or another workshop. It's a structural answer to one question: where in the customer journey does this signal live?
The sequence:
Start with the customer journey as the anchor, not touchpoints, channels, or departments
Layer in operational metrics by where they sit in the journey, not by which team owns them
Add feedback and signals positioned where they actually occur in the experience, not just where you measure them
Connect each stage to business outcomes: retention, cost to serve, conversion, margin
That structure turns a collection of local metrics into a shared model of reality.
What changes when context is shared
Three things shift that are hard to get any other way:
Definitions stop being debated. Friction, churn, conversion drop are anchored to specific places in the experience with measurable impact. The question shifts from "what does this mean?" to "where in the journey does this happen?"
Prioritization becomes journey-based, not political. Instead of "my metric dropped, give me roadmap space," the conversation becomes: "we structurally underperform here and it costs all of us."
Strategy connects to lived experience. Instead of "improve baggage booking," you can say: between booking and day of flight, we see a 5% revenue decrease tied to this experience. Here are the teams that own parts of it. That's something you can act on.
Context is infrastructure
CX doesn't fail because people don't care. It fails because smart, well-intentioned teams operate in different models of reality, looking at the same customer and drawing completely different conclusions, sometimes working against each other without knowing it.
Dashboards don't fix that. More AI doesn't fix that. What fixes it is shared context anchored to the customer journey. The Lufthansa ancillary team didn't need more data. They needed someone to ask: what does the full journey look like?
That's a context question. And the answer is infrastructure.
Want to hear the entire conversation? Watch or listen to this episode of The Experience Edge: