The Discovery Before the Exit

There’s a reason so many human stories begin with a journey. Sometimes it’s a pilgrimage. Sometimes it’s an inward search. Sometimes it’s the decision to walk away from what’s known and set out toward something new.

Discovery — whether personal or organisational — starts with an uncomfortable truth: something is missing. The map isn’t complete. The understanding isn’t whole. And before you can move forward, you have to acknowledge that gap.

In the world of data centre exits, this stage is unavoidable.

The acceptance point

Every organisation embarking on a data centre exit comes to the same moment. On paper, it seems obvious: “we’ve been running these systems for years, we must know them inside out.” But when the process of preparing for migration begins, the realisation dawns that the knowledge is incomplete.

Documentation is patchy. Dependencies are blurred. Commercial terms are unclear. Even the simplest questions — “what runs where, who owns what, how much does it cost?” — can produce long silences in the room.

For many leaders, this triggers frustration, or worse, embarrassment. “How can we not know?” But this reaction misses the point. What matters is not how the organisation arrived here, but what it does next.

The acceptance point is the recognition that imperfection is the starting line, not the end state.

The journey itself

From that moment, discovery becomes a journey in its own right. And like all journeys, it has stages.

• Technology: understanding the current estate, from mainstream platforms to the forgotten corners running on obscure operating systems.
• People: mapping not just the teams but the tacit knowledge they hold, often carried by a handful of individuals whose names have been passed down over decades.
• Documentation: sifting through what exists, accepting where it falls short, and deciding how much new work is required.
• Commercials: tracing supplier contracts, renewals, and hidden obligations that will shape migration choices.

Each of these stages uncovers something unexpected. An application that nobody realised was still in use. A contract clause that limits options. A dependency that ties one system to another in ways the design never anticipated.

The instinct is to see these as setbacks. In reality, they’re signs that the journey is working. The point of discovery is not to validate what you think you know; it’s to illuminate what you don’t.

New issues along the way

Just as personal journeys of self-discovery bring moments of doubt, frustration, or revelation, so too does a data centre discovery. New issues will appear. Sometimes they’re small — missing diagrams or outdated records. Sometimes they’re large — business-critical systems without clear ownership.

It’s tempting to see these moments as proof of failure: “we should have known this already.” But in truth, every organisation that undertakes this process finds itself here. These are not signs of weakness; they are simply the reality of decades of evolving technology estates, shifting ownership, and fragmented record-keeping.

The real measure is not whether issues appear, but how quickly and constructively they are surfaced, shared, and resolved.

The myth of perfection

One of the hardest lessons is that discovery is never complete. There will always be gaps. There will always be uncertainties. The idea that a programme can delay until every fact is known is a myth — and usually an expensive one.

Instead, the discipline lies in reaching a level of “good enough” to make decisions. Risk management becomes the companion to discovery. It provides the framework to move forward in the knowledge that unknowns remain, but that they are being actively managed.

Far from being a flaw, this is how large-scale transformations succeed. Progress is made by balancing the ambition for detail with the practical need to move.

Why the journey matters

What discovery achieves, above all, is clarity. Not perfect clarity, but better clarity. Enough to move from assumptions to evidence. Enough to challenge long-held myths. Enough to prepare leadership for the realities of the exit ahead.

And just as personal journeys of discovery often leave the individual changed, so too do organisational journeys. Teams emerge with a sharper understanding of their own estate. Leadership gains a clearer view of risks and opportunities. Even when the process uncovers uncomfortable truths, it equips the organisation to act with eyes open.

The worth of discovery does not lie in achieving perfection. It lies in the progress from uncertainty to understanding.

MyTwoCents

I’ve seen discovery framed as a box-ticking exercise, as if the aim is to produce a perfect inventory before migration can start. In practice, it is nothing of the sort. It’s a journey that brings its own value, often reshaping how leaders view their own organisation.

Yes, it can be frustrating. Yes, it will uncover gaps you wish weren’t there. But that is the work. The act of discovery is not just preparation for the data centre exit — it is part of the transformation itself.

And just like other journeys of discovery, the point is not to emerge with a flawless map. The point is to emerge with enough insight, resilience, and shared understanding to take the next step.