Before You Transform Anything, Map the Gap

Mapping the Approach (image courtesy of Unsplash)

I love a good strategy session, but sometimes I get the feeling all that brainstorming and discussion is just a waste of time.

A bunch of leaders get together in the conference room at the start of a new cycle. The people in the room are smart. The energy is good. Someone has put together a deck. The slides say something like: "We need to be more agile. We need to build a culture of accountability. We need better systems."

Everyone nods. SWOT analysis. Notes are taken. Action items are assigned. Everyone goes back to their day jobs.

And over the next six months, very little changes. Or things change — but not in the ways anyone intended.

I'm not being cynical. I've watched genuinely committed leaders run into this wall. The problem isn't their commitment or their vision. The problem is that they moved before they mapped.

The gap between strategy and operational reality

Often we live in-between the vision we have for an organization and the reality. Two versions. There's the organization on paper — described in the strategic plan, the org chart, the values document. And then there's the organization that exists in the hallways and behind closed doors: the patterns of decision-making, the informal hierarchies, the work that absorbs the most time, the way information actually moves.

These two organizations have common DNA but are almost never the same. And the distance between them — what I've come to think of as an Alignment Delta — is not a failure. It's a finding. It's information about where the real work is before moving forward.

The disconnect happens when we try to change the organization on paper without understanding the one that actually exists.

What the diagnostic lens reveals

When I work with an organization before they make a transformation decision, I conduct an assessment to look at six interconnected domains: Strategic Clarity, Leadership Readiness, Culture and Change Capacity, Process Maturity, Systems and Technology, and Team Capability.

None of these domains exist in isolation. A strategy might be genuinely clear at the leadership level and almost unrecognizable three layers down. A technology investment might be technically sound yet operationally undeliverable because the team doesn't yet have the capability to absorb it. A restructure might solve a reporting problem and create a cultural one.

This approach isn't an attempt at judgement on how well the organization is running. It's a way of reading the terrain before anyone decides where to go.

A good architectural assessment is like reading a river before you paddle it — you're looking for the features that tell you where the current actually wants to go, not just where the map says the water should be.

What this looks like in practice

Imagine a growing organization — one that wants to scale quickly but is feeling the friction of how that growth might play out. The leadership team thinks they are aligned on the direction, they just want to build more consistent processes and invest in the systems that will carry them to the next stage.

Before any of that happens, a diagnostic assessment surfaces something interesting: the team's understanding of the organization's current priorities — gathered independently, without bringing the team together in a room to talk strategy — diverges significantly. Not on values. On sequencing. On what needs to happen first.

That divergence is not a problem to fix. It is the transformation itself. Or at least, the first conversation in it.

Without the diagnostic, the organization might have invested months and significant resources in a process redesign that the team would have experienced as a top-down imposition disconnected from the real constraints of the work. With it, the leadership team has something more useful than a plan. They have an approach.

Where this gets complicated

There are limits to this approach.

Mapping the terrain and reading the landscape takes time that organizations under pressure feel they don't have. There's a version of the diagnostic conversation where the response is: "We know what the problem is. We just need to move." And sometimes that's true — some situations do require action ahead of full clarity.

What I've noticed, though, is that the organizations most certain they know what the problem is are often the ones who would benefit most from checking. Not because they're wrong, but because what looks like an execution problem from the top frequently looks different from the middle. And sustainable change requires both views.

A diagnostic assessment doesn't slow the work down. It redirects the energy to where it will actually land.

A question worth sitting with

When approaching a significant decision about your organization — a restructure, a new hire, a system investment, a culture initiative — it could be worth asking one question before you move:

Do we have a shared, honest picture of the organization as it actually is right now — not as we'd like it to be?

If the answer is yes, move. If someone's not sure, building the map is the first investment.

That gap — between the organization on paper and the one that shows up every day — is where most of the interesting work lives. And in my experience, it's also where the brainstorming and discussion gets legs and becomes fun again.