Many IT teams today share a similar feeling. No matter how much is modernized, no matter how many systems are replaced, migrated, or newly introduced, things are not getting simpler. Quite the opposite. Complexity is increasing, along with a subtle, often hard-to-define loss of control.
This perception exists across all levels of an organization, just in different forms. Administrators find themselves spending more time coordinating systems than actually operating them. The nature of their work is shifting: less design, more safeguarding, less clarity, more reaction.
At the management level, the same pattern appears in a more subtle but equally significant way. Decisions are made, yet their consequences are becoming increasingly difficult to predict. Dependencies exist, but are no longer fully visible. Strategies are defined, but operationally harder to trace. Meanwhile, business units develop their own perception: processes take longer, coordination becomes more complex, and even simple requests start to feel unexpectedly demanding. The real question, therefore, is not whether IT has become more complex, but why it becomes harder to control with every step of modernization.
The quiet shift of control
Over the past years, the IT landscape has fundamentally changed. Cloud platforms, specialized services, automation, and modular architectures have created opportunities that simply did not exist before. Systems can be deployed faster, scaled flexibly, and combined in technically clean ways. However, these possibilities have also changed how complexity is created and perceived. In the past, complexity was often visible. Systems were more monolithic, responsibilities clearer, and dependencies easier to understand. Today, complexity is less obvious. It no longer resides within individual systems, but in the way they interact. And that is precisely where it becomes difficult to grasp.
Every additional tool, interface, or external service expands the overall architecture, but not in a linear way. The relationships between components grow exponentially. What is designed as a modular and flexible system gradually evolves into a network of dependencies that is nearly impossible to fully oversee. The key point is that this complexity is not the result of poor decisions. It emerges from many decisions that are individually reasonable and often necessary. A tool is introduced to improve a process, an integration provides more transparency, and an additional service enables scalability. Each of these decisions solves a specific problem. But together, they create a structure that slowly moves away from its original clarity. The logic behind these decisions is local; their impact is systemic.
Many of these decisions are not even recognized as architectural decisions, even though that is exactly what they are. Most IT environments are not designed to be complex. They grow into complexity.
The result is an IT landscape that is technically powerful, yet structurally harder to manage. This is where the real loss of control begins. Not because systems fail, but because no one fully understands how they interact anymore.
The misconception of modern IT
A major driver behind this development is an assumption that is rarely questioned: that modern IT automatically becomes simpler. Cloud is expected to reduce complexity, automation to simplify processes, and a best-of-breed approach to deliver the optimal overall solution. In practice, however, reality looks different. Cloud does not eliminate complexity. It shifts it into areas that are harder to control. Infrastructure becomes easier to provision, but significantly more difficult to govern. Responsibilities are not removed; they are redistributed. And with every outsourced component, a new dependency is introduced that must be actively managed.
Automation behaves similarly. It reduces manual effort, but increases the complexity of the systems that replace it. Errors do not disappear; they are pushed into layers that are more difficult to understand. Issues may occur less frequently, but when they do, they are far more challenging to analyze and resolve. The more automated systems become, the less obvious their weaknesses are.
The same applies to the widely adopted best-of-breed approach. Instead of creating clarity, it often results in a collection of highly capable individual components that require significant effort to work together. What is optimized at the component level is rarely optimized at the system level. Technological excellence does not replace architectural clarity.
The core misconception lies in equating technology with simplification. Technology expands possibilities, but it does not automatically reduce complexity. Simplification is not a property of modern systems – it is the result of conscious decisions. And these decisions are often not made deliberately. Complexity does not arise because it is necessary. It arises because it is not actively limited.
When simplicity becomes a choice again
The key insight is therefore not purely technological, but organizational. If complexity is not an inevitable outcome of modern IT, but the result of many individual decisions, then it can also be influenced. Not by rejecting innovation, but by handling it more deliberately. By consciously shaping architecture, operating models, and tool landscapes. Fewer tools, but selected with intent and clearly positioned. Defined responsibilities in operations instead of fragmented ownership across multiple layers. Standardization where it increases stability and clarity, rather than being perceived as a limitation. And above all, transparency as a guiding principle, not a byproduct.
These approaches may seem unspectacular at first. They are not disruptive transformations, large-scale initiatives, or new technologies. Yet that is precisely their strength. They create the foundation for systems to become understandable again. And only systems that are understood can be effectively managed and developed over time. An IT landscape that only works as long as nothing unexpected happens quickly becomes a risk.
Perhaps the real challenge of the coming years is not to introduce ever more technologies or continuously expand existing systems. It is to make more deliberate decisions about which complexity is necessary and which is not. The best IT is not the most modern.
It is the one whose complexity has been consciously designed.
If your organization is navigating increasing infrastructure costs and growing complexity, a pragmatic approach, beyond ideology and buzzwords, can make the difference.
