There was a time when huge customer journey maps hung on company walls. Colourful sticky notes, touchpoints, emotions, pain points… People stood in front of them in meetings, took photos of them, and they were the obligatory backdrop for award entries. Yet a meaningful, lasting drop in the number of customers calling the contact centre did not always follow.
I do not think the problem was the maps themselves; it was that the map never turned into a decision-making mechanism. There was also a truth that was often skipped: the customer journey has never moved in a straight line. A user starts a transaction in the mobile app, continues on the website, drops into the store, complains on social media and comes back to the app the next day. And we still try to describe this behaviour with a diagram that flows from left to right.
A map shows what happened. Orchestration manages what is about to happen. Imagine a customer struggling at the payment step. The map tells us there is friction at that step. Orchestration does not leave the customer alone with that friction; it offers another payment method, brings the support channel forward and, if needed, redesigns the process. We mostly focus on seeing where customers have or will have a problem. What we should focus on is how the organisation responds before the problem happens.
I think this is where the quiet transformation in customer experience is taking place. For years, companies did journey mapping; now they talk about journey management, or more precisely, real-time journey orchestration. This change is not only about technology; it is also about how the organisation is structured. If marketing, operations, product, stores, digital channels and the contact centre tell the same customer different stories, there is no journey, only noise. What we call orchestration is the ability to turn that noise into a single experience.
In the coming years, the success of customer experience teams will not be decided by how many maps they draw, but by how well they stop a problem a customer had in one channel from happening again in another. Most good experiences go unnoticed; the customer simply feels that things got done.
So I do not think journey maps are dead. They just need to come off the wall and move into operations. Is your map still on the wall, or is it inside your decisions?