TechRadar Warns Too Much IT Change at Once Raises Outage and Cyber Risk
TechRadar says organizations risk outages and cyber incidents when they try to deliver too much IT change at once.
The article identifies two main drivers. One is pressure to innovate: rapid advances in technology and AI, shifting business priorities and vendor messaging push organizations to adopt new tools quickly, while inflation and slower economic growth increase the need for cost-effective systems. The other is forced change. Operating systems reach end of life and need upgrading, outages and cyber threats must be defended against, and software vendor price increases—such as those following ownership changes at VMware—can force companies to seek alternatives and reduce vendor dependency.
The trap, the article says, is trying to deliver all of that change at once and within a short timeframe. That makes change harder to manage and raises the risk of outages and system failures.
A central challenge is visibility. Companies must oversee complex IT estates spanning on-premises systems, cloud, servers, end-user computing and networks, where change is constant and security updates are largely automated. As older and newer systems interact, along with different operating systems and products, the risk of failure can increase.
Configuration drift occurs when unrecorded or unauthorized changes cause a system to move away from its intended baseline. Without monitoring software, the article says, that drift can remain invisible and add risk to every later change, leading to outages or cyber incidents. It cites an example from May in which Google Cloud suspended Railway's production account without warning because Railway could not see that the platform had a technical dependency on GCP that caused it to fail, resulting in an eight-hour outage.
The article also says AI tools can be adopted faster than training and processes can keep up, increasing the risk of disjointed workflows, security vulnerabilities and data breaches. Even when teams can see changes that need to be made, they still face decisions about how to modernize existing applications.
Traditionally, IT teams have had to buy new software or rebuild existing apps, both expensive and time-consuming options that can lead to vendor lock-in, according to the article. As agentic coding matures, organizations may increasingly use AI agents to build replacements for SaaS tools. The article says this can appear to remove vendor lock-in and license costs, but it transfers responsibility for maintenance, security, configuration and support in-house, making change harder to oversee without additional resources or capacity.
Another route is packaging and migrating existing applications. By packaging an app's or virtual machine's existing operating system dependencies, teams can move them into containers and modern desktop infrastructure without rewriting the app. The app keeps its existing behavior but can run on the latest operating systems and in workspaces such as AWS.
For ongoing visibility, the article says manual monitoring and reconciliation will struggle to keep up. It says teams should consider configuration monitoring software and drift detection tools that measure change against established baselines and alert IT teams when a system moves away from its baseline.