By Hadja Cherif, CCXP

A few weeks ago, I ordered a pair of shoes from an international retailer for an important event. They didn’t arrive on time.

On its own, that isn’t remarkable. Delays happen, and most customers understand that. What stayed with me wasn’t the delay itself. It was everything that happened afterwards.

The experience started exactly as I hoped it would. I received shipping confirmation, a tracking number, the name of the international logistics provider and the local courier responsible for the final delivery. Everything suggested that I would be able to follow my package throughout its journey, and for the first few days, that’s exactly what happened.

Then the updates stopped.

When I checked the local courier’s tracking page, it indicated they were still waiting to receive the package, while the international tracking suggested it had already reached Canada. I contacted the courier, the logistics provider and the retailer. Each interaction provided another piece of information, but none answered the question I actually needed answered:

One response explained that a “final batch release” was still pending. I’m sure that accurately described an internal operational process. As a customer, however, it didn’t help me understand what would happen next or whether I needed to make other plans.

Looking back, I realized something had shifted. I was no longer simply waiting for a delivery. I was trying to reconstruct the journey myself by comparing tracking systems, contacting multiple organizations and interpreting information that made sense operationally but not from a customer’s perspective.

That was the moment this stopped being a delivery story and became a Customer Experience story.

One observation kept coming back to me.

That may sound obvious, but I think it raises an important question for our profession. As organizations increasingly rely on logistics providers, payment platforms, technology vendors and other partners, who is accountable for the customer’s journey when it extends beyond the organization’s walls?

Operationally, every organization involved in my purchase appeared to be doing what it was responsible for. The retailer fulfilled the order. The logistics provider managed the shipment. The local courier waited to receive it. Customer Service responded when contacted.

Yet despite that, the experience still felt fragmented. No single interaction was particularly poor. The overall journey simply lacked coherence.

Customers don’t evaluate organizations the way organizations evaluate themselves. We don’t think in terms of retailers, logistics providers, payment partners or technology vendors. We remember one purchase. One journey. One outcome.

That’s why I believe one of the biggest challenges facing Customer Experience today isn’t simply improving individual touchpoints. It’s ensuring that the journey still feels coherent when multiple organizations contribute to delivering it.

This is where I think conversations about journey orchestration become particularly relevant. Mapping a journey helps us understand it. Orchestrating a journey requires organizations to think beyond their own responsibilities and consider how the customer experiences the transitions between partners.

Those transitions are often where uncertainty appears. They’re also where trust is either reinforced or lost.

This experience also reminded me why Customer Experience is inseparable from business performance. My disappointment wasn’t with the product itself, yet I found myself questioning whether I would order from the retailer again. That wasn’t because the retailer manufactured a poor product. It was because the journey surrounding that product influenced my confidence in the brand.

When we talk about Customer Experience influencing loyalty, advocacy and revenue, this is what that relationship looks like in practice. A customer doesn’t separate the retailer from the partners that helped deliver the experience. Whether we intend it or not, those partners become part of our brand.

If this experience had been raised through a Voice of the Customer program, my questions would have been less about the shipment itself and more about the journey surrounding it:

• At what point did we know the original expectation was at risk?
• Could proactive communication have reduced uncertainty, even if the delivery timeline couldn’t change?
• What information did the customer actually need, rather than what our operations knew?
• How are partner experiences governed to ensure they reinforce, rather than weaken, the brand promise?
• When multiple organizations contribute to one customer outcome, who is responsible for maintaining the customer’s confidence throughout the journey?

I don’t pretend to have definitive answers to those questions. What this experience changed were the questions I now ask.

As customer journeys continue to span more organizations, I believe one of the most important responsibilities of Customer Experience leaders will be ensuring that customers experience one journey, not a series of disconnected handoffs. Because while organizations may outsource parts of the operation, customers rarely believe they’ve outsourced accountability.

As customer journeys continue to evolve, I suspect many of us are asking the same question: How do we ensure customers experience one coherent journey when no single organization owns every interaction?

I’d genuinely be interested in hearing how other practitioners are approaching that.