One of the most common misconceptions about transformation is that it begins with a clean break. In reality, it becomes integrated into overall delivery.
Systems are still running, operations continue, and commitments remain. At the same time, the organization is being asked to change how those systems are built, supported, and delivered.
There is no opportunity to stop ongoing work and reset the environment. Transformation happens while the plane is still in the air.
The Illusion of Separation
It is often assumed that operations and transformation can be treated as separate efforts. One maintaining the present, the other building the future. In practice, they are deeply interconnected.
All changes impact current operations, while operational constraints influence what can realistically be changed. Capacity, risk, and outcomes are shared, even when transformation work is treated as something separate.
When that relationship is not acknowledged, transformation planning becomes disconnected from how it actually operates.
Competing Demands on the Same System
The same teams responsible for maintaining legacy systems are often the ones expected to modernize them.
At the same time:
- Operational issues require immediate attention
- New projects, enhancements, and technology requests continue to emerge
- Legislative and enterprise priorities drive additional demand
- Transformation efforts require focus and sequencing
- Workforce capacity remains constrained
These demands arrive simultaneously. This creates constant tension between what must be maintained, what must be delivered, and what must be transformed.
External Pressure and Internal Constraint
Transformation does not occur in isolation. It is shaped by external timelines, enterprise dependencies, and the pace at which partners can move.
At the same time, legacy environments continue to require support, often consuming a disproportionate share of capacity. This creates a dual constraint:
- The organization must move forward
- The system limits how quickly it can move
Without alignment between these constraints, transformation planning becomes disconnected from operational reality.
Why Transformation Slows
Everybody wants progress, but the same people/systems are carrying operations, new work, and modernization simultaneously.
When operational stability is at risk, it will always take precedence. That is priority number one, particularly in environments where reliability directly impacts public safety.
Without disciplined prioritization, operational work expands to consume available capacity while new demand continues to enter the environment. Transformation work becomes reactive rather than intentionally sequenced.
Over time, this creates a cycle:
- Legacy systems require ongoing attention
- Capacity for modernization decreases
- Complexity continues to grow
Breaking that cycle requires intentional intervention.
Creating Space for Change
Transformation requires funding, time, focus, and capability. Creating that capacity is a leadership responsibility.
Through governance and intake processes such as the IT Investment Board (ITIB), work is prioritized, sequenced, and aligned to available capacity. Tradeoffs become visible and decisions are made with a clearer understanding of impact.
At the same time, identifying areas where progress can be made without legacy constraints becomes important. Investments in data, automation, and AI provide visible forward movement while larger transformation efforts continue to take shape.
These efforts are not replacements for core transformation work. They are parallel paths that create momentum while larger modernization efforts continue.
Balancing Stability, Transformation, & Innovation
The objective is not to choose between operations, transformation, and innovation. It is to manage all three deliberately.
This requires:
- Maintaining stability where it matters most
- Sequencing transformation work based on capacity and readiness
- Advancing innovation in areas that are less constrained
- Ensuring that new work does not outpace the system’s ability to support it
This is an ongoing discipline that must be maintained as demand continues to grow.
What This Reinforced
One of the biggest shifts in perspective is realizing that transformation is not a separate initiative. It has to be integrated into how the organization operates every day.
Running the system and changing the system are not independent activities. They are the same work, viewed from different perspectives.
Leaders who recognize this tend to approach transformation differently and execute it more effectively.
The Wrap
Transformation is often described as a journey. In practice, it is an operating condition.
The organization does not stop so that change can occur. Change must occur while the organization continues to operate.
The challenge is not simply to move forward; it is to do so without losing control of what is already in motion.
Trusted insights for technology leaders
Our readers are CIOs, CTOs, and senior IT executives who rely on The National CIO Review for smart, curated takes on the trends shaping the enterprise, from GenAI to cybersecurity and beyond.
Subscribe to our 4x a week newsletter to keep up with the insights that matter.
