Stop mapping the journey. Start blueprinting the transformation.

When I joined BRP to lead Customer Experience, my office came with an unusual piece of inherited decor: a roughly 40-foot customer journey map rolled up in the corner collecting dust.

It was almost too perfect a metaphor.

I’ve seen versions of this throughout my career, through conversations with peers, working with clients and, in some instances, my own experience. Organizations invest significant time and money mapping the customer journey, uncover real problems, design a compelling future state and generate excitement around the work. Then everyone goes back to their day jobs and the journey slowly becomes something people remember as a “cool exercise.”

The problem isn’t journey mapping. I still believe it’s one of the most valuable ways to understand the current experience and design something better. The problem is stopping there.

A journey map helps identify what needs to change. But it doesn’t necessarily tell you how to change the organization behind the experience.

That gap became the genesis for what we now call Transformation Blueprinting at Dialed.

From understanding the experience to changing the business

The customer journey remains our anchor, but the work quickly moves beyond the journey itself.

We look at three fundamental dimensions:

People: Who owns the opportunities? Who needs to be involved, and does the organization have the capabilities and accountability to deliver the change?

Process: How does shit actually get done? Not what the process map says, but how decisions happen, where handoffs break down and what needs to work differently.

Technology: What capabilities are required to deliver the future-state experience, and where should technology investment be directed to create the greatest value?

The important part is understanding how these pieces connect. A customer problem might appear to be a technology issue but actually be rooted in a broken process or unclear accountability.

Technology should follow the opportunity, not the other way around.

And because no organization can transform everything at once, the work needs to be prioritized and sequenced around impact, complexity and the organization’s ability to absorb change.

Quick wins build momentum, but the larger structural changes are often where the real value lives. You need both.

A blueprint only matters if the business uses it

This is the part I think gets missed most often.

You can have a compelling future-state experience and a thoughtful transformation roadmap, but if neither becomes part of how the business actually operates, you’ve created a more sophisticated version of that rolled-up journey map.

The business needs to own the change. Priorities need to show up in planning, decisions need to get made, roadblocks need somewhere to go and progress needs to be measured against customer and commercial outcomes, not simply project completion.

A transformation office can help coordinate the work, but it can’t substitute for accountability within the business itself.

The goal isn’t to create a transformation program that runs beside the business. It’s to change how the business runs.

I learned a lot of this through lived experience

At BRP, we undertook a massive end-to-end digital transformation, anchored in the customer and employee experience.

We had some material wins, and we made some blunders.

Looking back, I wish I’d understood then as clearly as I do now how important the connections between all these pieces were. A great future-state experience means little without ownership. Technology investment means little if it isn’t solving the right problem. And even the best roadmap struggles if the organization can’t see meaningful progress along the way.

A lot of what became Transformation Blueprinting at Dialed came from those experiences, both what worked and what I wish we’d done differently.

And I think it’s about to become even more important.

Which brings me to AI

I’m seeing organizations approach (or be sold) AI transformation in much the same way we did with digital transformation: start with the technology, develop a list of use cases and look for places to deploy it.

I think that’s backwards.

AI transformation forces some fundamental business questions. What should humans do? What should machines do? How should they work together? Which processes should we improve before we automate them? And what experience are we ultimately trying to create?

Those are business transformation questions that technology alone can’t answer.

The risk is that we repeat the mistakes of digital transformation, only this time with much more powerful tools that can scale both good and bad outcomes considerably faster.

That’s why I believe Transformation Blueprinting is becoming increasingly relevant. It provides a way to connect the experience we’re trying to create with the organizational changes required to deliver it.

What most companies need isn’t an AI roadmap. They need a business transformation roadmap for an AI-enabled world.