Why organizations risk changing too much, too quickly

Organizations face pressure to change their IT systems as technology and AI advance, business priorities shift and economic growth slows. They may also need to replace systems nearing the end of their supported life, respond to outages or cyber threats, or find alternatives after software prices rise. TechRadar’s Kashif Nazir describes the risk of trying to handle these demands all at once: rapid, overlapping changes can be harder to manage and increase the chance of outages and system failures.

A central challenge is visibility across complex IT environments that span on-premises systems, cloud services, servers, networks and end-user devices. As older and newer systems interact, unrecorded or unauthorized changes can cause configuration drift: a system moves away from its intended baseline. Without monitoring, that drift may go unnoticed and complicate later changes.

Nazir cites an incident in May in which Google Cloud suspended Railway’s production account without warning. Railway had not seen a technical dependency on GCP, and the failure led to an eight-hour outage. He also warns that adopting AI tools faster than training and processes can keep up may contribute to disjointed workflows, security vulnerabilities and data breaches.

For legacy applications, Nazir outlines options including buying software, rebuilding apps or using AI agents to create replacements for SaaS tools. The latter may shift maintenance, security, configuration and support responsibilities in-house. Another approach is to package existing operating-system dependencies and move applications into containers or modern desktop infrastructure without rewriting them. He argues that continuous configuration monitoring can help teams detect drift, understand system interactions and plan changes; automating app packaging and delivery can also reduce manual work.