By Michael Shonholz
Chief Executive Officer, ARG
Published: August 10, 2026
Executive Overview
The most profoundly complicated IT environments I have ever encountered were never built that way by malicious design or incompetent architecture. They arrived at their current state through a long, logical sequence of entirely reasonable decisions made by capable people operating under intense, real-world business pressure.
Consider the anatomy of a modern enterprise infrastructure: A cloud provider is brought on because the incumbent vendor cannot hit a critical latency requirement. A specialized point solution is fast-tracked because a business unit urgently needs to capture a rapidly closing market opportunity. A managed service layer is hastily introduced when corporate headcount freezes leave the internal team critically understaffed. At the precise moment each choice is made, it represents the single best course of action available.
The reckoning, however, always comes later. The true crisis of modern enterprise technology is that after two decades of logical, isolated decisions, companies are left with a sprawling, opaque ecosystem that no single individual fully comprehends.
Organizations carrying the heaviest burdens of IT complexity are rarely those that made the worst strategic choices. Paradoxically, they are almost always the companies that grew the fastest, responded most aggressively to market demands, or distributed technology purchasing power directly across their business units. In a very real sense, enterprise complexity is the accidental byproduct of commercial success. But that realization does nothing to mitigate the punishing financial and operational costs of carrying it.
The Anatomy of Accumulation: A Three-Phase Chronology
When I was leading some of the largest cloud and managed services practices in the country, I began keeping an informal tally of the recurring terminology enterprises used during our introductory discovery meetings. The same words surfaced repeatedly: legacy, inherited, technical debt, and the ubiquitous defensive refrain: "We need that for compliance" or "That particular business unit simply won’t let it go."
It became clear that complexity rarely lives in the technology stack alone. It is deeply entangled with human behavior, organizational processes, rigid regulatory mandates, and the idiosyncratic realities of how businesses operate day-to-day. Over time, I observed a consistent evolutionary pattern—a three-phase life cycle that organizations experience organically, rarely recognizing the traps as they fall into them.
Phase 1: The Accumulation Phase
This is the normal, healthy course of enterprise IT operations: organizations add raw capability as the business demands it.
- A new Software-as-a-Service (SaaS) application is onboarded because a department needs immediate functionality.
- A new cloud region is spun up overnight because a regulatory framework demands strict data sovereignty.
- A point solution patches a gap in a core platform that corporate leadership hasn’t funded for updates in three years.
- The enterprise grows aggressively through mergers and acquisitions (M&A), inheriting a tangled web of legacy contracts, disparate vendors, and overlapping toolsets.
Individually, none of these actions represent poor planning. Yet, cumulatively, each addition introduces a new integration surface, a fresh vendor contract, an independent support relationship, and another recurring line item on an already bloated budget.
Phase 2: The Drift Phase
Once accumulation reaches a critical mass, drift inevitably sets in. This is the stage where internal teams begin systematically working around official channels—bypassing IT, Finance, Legal, and Procurement—because the centralized corporate machinery has simply become too slow or too bureaucratic to serve their actual or perceived needs.
Shadow IT often carries a harsh, irresponsible reputation, but in the vast majority of enterprises I have advised, it has very little to do with rogue employees or malicious rule-breaking. Instead, it is driven by rational people attempting to solve real business problems with whatever tools are readily accessible. The problem is rarely the workforce; the problem is that the official corporate toolchain is no longer fit for purpose.
Phase 3: The Lock-In Phase
By the final phase, the enterprise environment has evolved so many interdependencies—some meticulously documented, but most living only in the institutional memory of departing employees—that initiating any significant change feels genuinely perilous.
Technical debt is extraordinarily high, and the perceived costs and risks of modernization tower over the organization. Building a credible business case for refactoring requires a level of stakeholder alignment and cross-functional analysis that most overwhelmed IT teams simply cannot muster. Every potential simplification carries a terrifying list of downstream impacts that no one is entirely confident they can predict. Consequently, the organization chooses paralysis: the environment remains aggressively complex, and the maintenance burden compounds year after year.
Supporting Context and Metrics: The True Cost of Sprawl
The financial toll of this evolutionary cycle is staggering. According to the Flexera 2024 State of the Cloud Report, organizations waste an average of 28% of their total cloud spend—a staggering metric that has held remarkably consistent across multiple consecutive years of study.
In my professional experience, a significant portion of that waste cannot be dismissed as irresponsible purchasing or accidental over-provisioning. Rather, it is the direct, unavoidable overhead of maintaining overlapping capabilities acquired at different points in corporate history, for reasons that made absolute sense at the time, but are now nearly impossible to untangle.
Furthermore, this financial drain is compounded by the hidden vectors of shadow IT. Industry research from analyst firms like Gartner indicates that shadow IT accounts for 30% to 40% of total IT spending within large enterprises. This massive shadow economy is composed of unvetted tools spun up for single projects and never decommissioned, legacy software inherited through corporate acquisitions that were never fully integrated, and unauthorized cloud instances running completely off the books. When an enterprise attempts to simplify an IT estate it can no longer fully visualize, the margin for catastrophic operational error is dangerously wide.
Official Perspectives: Why Simplification Initiatives Stall
I have watched countless enterprise simplification initiatives announced with great corporate fanfare, only to be quietly shelved six months later. The underlying causes are almost always practical rather than strictly political—though organizational politics certainly do their best to complicate matters further.
1. The Visibility Gap
The most immediate hurdle is that very few organizations possess a complete, unvarnished view of their own environment. I have witnessed major consolidation initiatives stall because every time an IT team believed they had successfully mapped their application dependencies, they uncovered yet another rogue workflow or hidden database that had been omitted from the initial discovery phase.
No one was negligent in these instances; the enterprise environment had simply evolved at a velocity far exceeding the documentation lifecycle. When you add capability under intense pressure for decades, documentation is invariably the first casualty.
2. The Human and Process Dependency
Simplification is never purely technical; it invariably impacts real people. Somewhere deep within the corporate hierarchy, an essential business process or mission-critical report is inextricably tied to a database that was ostensibly scheduled for decommissioning two years ago.
Alternatively, a specialized business unit has deeply customized a platform to fit their specific workflow, rendering them utterly incapable of migrating when modernization day arrives. True simplification requires meticulous, patient coordination to untangle these human dependencies—bandwidth that most corporate IT departments simply do not possess while simultaneously fighting fires and "keeping the lights on."
3. The Elusive Business Case
Unlike a clear software licensing fee or hardware purchase, the costs of complexity do not always manifest as a clean, easily quantifiable line item on an expense report. Instead, complexity presents itself insidiously:
- Slower incident response and resolution times.
- Inflated vendor management and contract negotiation overhead.
- Protracted onboarding cycles for new technical staff.
- Missed strategic market windows to adopt modern capabilities like AI and advanced automation.
Because these costs are diffused across the entire enterprise, they are notoriously difficult to aggregate into a single metric that cleanly justifies a multi-quarter consolidation project. As a result, funding is frequently withheld until a critical system breaks badly enough to force leadership’s hand.
Real-World Remediation: What Actually Works
It is easy to offer sweeping, superficial advice from the outside. Telling an enterprise CIO to "just rationalize your vendor portfolio" sounds elegant in a boardroom presentation, but executing that directive without accidentally shattering business operations requires extraordinary discipline and a proven methodology.
Based on decades of trenches-level experience, three specific strategies consistently yield results in complex enterprise environments:
Start with the Contract Layer, Not the Technology Layer
Most modern enterprises maintain a far clearer, more accurate inventory of what they are paying for than what they are actually running. A comprehensive, ruthlessly thorough contract and spend audit will surface redundant capabilities far faster than a traditional technical architecture review. The money trail is almost always cleaner and more honest than the configuration trail. While a financial audit will not provide the complete architectural picture, it establishes an undeniable, real-world baseline for action.
Build the Complete Map Before Touching Anything
Organizations that successfully navigate enterprise simplification dedicate significant time—often months—to conducting an exhaustive inventory of their current state before touching a single line of code or terminating a contract. This unglamorous, foundational work rarely makes headlines in board updates or executive summaries, but it is precisely the differentiator that separates successful consolidation initiatives from stalled, failed projects.
Stage the Work Around Business Cycles, Not IT Timelines
I have seen technically brilliant, flawlessly architected simplification projects fail entirely because they were scheduled without regard for the operational rhythms of the business. Executing major cloud migrations during corporate quarterly financial close processes, or pushing aggressive infrastructure changes during peak retail seasons, destroys institutional confidence in IT leadership—regardless of how sound the technical merits may be.
Future Outlook: The Goal Is Purpose, Not Minimalism
The ultimate objective of modern enterprise technology management is not to achieve a minimalist environment simply for the sake of aesthetic simplicity. A mature, thriving enterprise IT landscape should carry a degree of inherent complexity, because the global business enterprises they support are inherently complex.
The true metric of maturity is not the absence of complexity, but complete operational clarity. In a healthy IT ecosystem, every single tool, vendor, platform, and contract serves a clearly defined, defensible purpose. Leadership knows precisely who owns it, what it costs, and what operational risk it introduces.
Most enterprise organizations I work with are not light-years away from achieving this state of clarity. They simply need to recognize a fundamental truth: they must stop adding before they can ever hope to start subtracting.
About the Author
Mike Shonholz is the CEO of ARG, a premier technology advisory firm helping enterprise and public sector organizations make data-driven technology decisions. He has spent more than two decades building and leading some of the largest cloud, connectivity, and managed services practices in the country, including leadership roles at CDW prior to joining ARG. He has been recognized as one of the 50 most influential leaders in the technology sector.