Every organisation has a transformation roadmap. Whether it’s adopting AI, modernising infrastructure, improving cyber resilience, migrating workloads to the cloud, or enhancing digital employee experiences, the destination is usually well defined.
The challenge is rarely deciding where to go. It’s understanding where you’re starting from. This is one of the most overlooked reasons transformation programmes fail to deliver the outcomes organisations expect. Leaders spend significant time defining the future state, but comparatively little establishing a complete picture of the current one.
Without an accurate understanding of today’s environment, every transformation decision carries greater uncertainty. Because every roadmap is only as reliable as its starting point.
Why “AS-IS” matters more than ever
Imagine being asked to renovate a large office building. You have ambitious plans to create more collaborative workspaces, improve energy efficiency and future-proof the building for decades to come. There’s just one problem. Nobody has the original architectural drawings. Some floors have been remodelled over the years. Extensions have been added. Electrical systems have been upgraded by different contractors. Several walls aren’t where the plans suggest they should be.
Would you begin construction? Probably not. You would first invest time in understanding what already exists. And enterprise IT deserves the same approach.
Most technology estates have evolved over many years through business growth, acquisitions, changing suppliers, cloud adoption, urgent projects and strategic initiatives. Individually, each decision solved a business challenge or enabled the organisation to move forward. Collectively, they have shaped environments that often look very different from those originally designed. Transformation doesn’t erase that history. It builds upon it.
Technology isn’t the problem
When transformation initiatives underperform, organisations often question the technology they selected. Was the platform wrong? Did we choose the wrong vendor? Should we have invested somewhere else? Sometimes.
More often, the technology itself was never the issue. The real challenge was an incomplete understanding of the environment into which it was being introduced. Undocumented dependencies between applications, ageing infrastructure supporting critical services, fragmented ownership and inconsistent configuration standards can all shape how successfully new technology is adopted. At the same time, service management data may present one picture, while the day-to-day experience of operational teams reveals another.
None of these issues prevent transformation individually. Together, however, they create friction that slows delivery, increases cost and introduces unnecessary risk.
Every transformation creates new dependencies
Modern technology isn’t replacing complexity. In many cases, it’s adding to it.
- Cloud services still rely on on-premises infrastructure
- AI platforms depend on clean, trusted data
- Automation requires consistent processes
- Zero Trust architectures rely on accurate visibility of users, devices and applications
- Observability platforms need meaningful telemetry
- Digital employee experience depends on reliable networks, applications and service management working together
Every strategic initiative introduces another layer of dependency. If those dependencies aren’t understood beforehand, organisations often find themselves solving yesterday’s problems while trying to build tomorrow’s capabilities.
Visibility isn’t about assets; it’s about relationships
Many organisations can produce an asset register. They know how many switches they own. They know which firewalls are deployed. They know where their cloud workloads reside. All of which is useful information. But transformation requires something different. It requires understanding relationships.
- Which applications rely on which services?
- Which business processes depend on ageing infrastructure?
- Which teams own critical platforms?
- Where are operational bottlenecks created?
- Which services would be affected if a single component failed?
Visibility isn’t simply knowing what exists. It’s understanding how everything works together. Only then can leaders understand the true impact of change before it happens.
The cost of starting in the wrong place
When organisations begin transformation without a complete baseline, the consequences rarely appear immediately. Projects continue. Milestones are achieved. New technology is deployed. Only later do the hidden costs begin to emerge as:
- Unexpected delays
- Budget overruns
- Repeated design changes
- Growing operational complexity
- Unplanned outages
- Reduced confidence from stakeholders
These are often treated as delivery issues. But usually, they are symptoms of insufficient visibility at the very beginning of the programme. Transformation doesn’t create uncertainty. It exposes the uncertainty that already existed.
Building confidence before building change
Successful organisations don’t eliminate uncertainty entirely. They reduce it. They create confidence by understanding:
- Their current operational maturity
- Where critical dependencies exist
- Which risks carry the greatest business impact
- Where technical debt is limiting progress
- Which improvements should be prioritised first
Only then do they define what the future should look like. The strongest transformation strategies don’t begin with ambitious technology goals. They begin with evidence. Because evidence creates confidence. And confidence creates better decisions.
Rounding up
Transformation is often presented as a race to adopt the latest technologies. In practice, it’s a process of making better decisions. Those decisions become significantly easier when leaders understand not only what they want their organisation to become, but also the environment they’re asking it to evolve from.
Seeing the complete picture doesn’t slow transformation. It accelerates it.
This is because organisations spend less time reacting to unexpected complexity and more time delivering meaningful change. But even when leaders have a clear understanding of their environment, another challenge often remains.
What if the greatest threat to resilience isn’t a lack of technology…
…but the assumption that buying more security tools automatically makes an organisation more secure?
Check out the next article in this series: Cyber resilience starts long before security tooling, where we discuss why cyber resilience begins long before the first security product is deployed, and why the strongest defence is often built on operational discipline rather than technology alone.