Leadership
How technology leaders keep things running while also trying to modernize them
Technology leaders are expected to keep systems stable and drive major changes at the same time. These are genuinely conflicting goals. This piece looks at how the best ones manage both without consistently sacrificing one for the other.
Two mandates in genuine tension
The modern CIO has two mandates that are in genuine tension with each other. The first mandate is operational: keep the lights on, protect the enterprise from security threats, maintain system availability, and manage technology costs. This mandate is measured by incidents avoided, uptime maintained, and budgets not exceeded. The second mandate is strategic: modernize the technology estate, enable new business capabilities, and position the enterprise to compete in an increasingly digital market. This mandate is measured by new capabilities delivered, transformation programs advanced, and business outcomes enabled. These mandates are in tension because the resources, risk appetite, and organizational focus required for transformation are exactly the resources that operational stability requires you to conserve.
How the tension typically resolves — and why it shouldn't
In most enterprises, the tension resolves in favour of operational stability — because the consequences of operational failure are immediate, visible, and attributable. An outage produces a war room, board attention, and a review process. A transformation program that delivers six months late produces a revised timeline. The asymmetry in consequences means that CIOs who face resource constraints will consistently deprioritize transformation in favour of operations — which is often the individually rational decision and the collectively wrong one. The enterprises that fall furthest behind in technology capability are usually not the ones where CIOs made bad decisions. They're the ones where rational CIOs made consistent operational decisions in an environment where transformation was always the thing that could wait.
The organizational design that reduces the tension
The most effective approach we've observed is organizational separation between the 'run' function and the 'change' function — not as a permanent structure, but as a resourcing and governance model. The run function has explicit ownership of operational metrics and operational budgets. The change function has explicit ownership of transformation programs and transformation budgets. The CIO governs both, but the two functions don't compete for the same resources or the same leadership attention in the same forums. This separation doesn't eliminate the tension — they will always compete for the same engineering talent — but it makes the competition visible and manageable rather than implicit and unresolvable.
The technology choices that reduce the underlying tension
The technology choices that reduce the tension between stability and transformation are the ones that make the run function less resource-intensive. Managed services, automated operations, and platform infrastructure that requires less human intervention to maintain free up engineering capacity for transformation work. The CIOs who navigate the stability-transformation tension most effectively are the ones who invest in reducing the operational burden of the existing estate — not to cut headcount, but to redirect engineering capacity toward the transformation program. This is a multi-year investment with a non-linear return: the first year produces marginal capacity gains, the second and third years produce enough freed capacity to meaningfully accelerate transformation.
Want early access to our thinking?
Subscribe to receive Aethon Core insights as they publish — practical, plain-language content on enterprise technology from people who build it.