Your Operating Model Is the Real Legacy System
This is an expanded version of an article originally published on CIO.com. Reprinted with permission. © Foundry, Inc., 2026. All rights reserved. [https://www.cio.com/article/4168935/your-operating-model-is-the-real-legacy-system.html] Enterprise modernization isn’t failing because technology is outdated. It’s failing because the enterprise is still operating on a legacy decision model. For the past decade, enterprise modernization has been framed as a technology problem. Legacy systems. Technical debt. Monoliths that need to be broken apart and moved to the cloud. Those investments matter. But they rarely address the actual constraint. In many organizations, technology is capable of moving faster than the enterprise itself. The operating model has become the real legacy system. That framing may be convenient, but it is also incomplete. Technology has advanced dramatically. Cloud platforms, APIs, automation, AI, and modern engineering practices have given organizations unprecedented technical capability. Yet many enterprises continue to struggle to translate those investments into faster execution, better decisions, and measurable business outcomes. The reason is increasingly clear. In most organizations, technology isn’t the constraint. The operating model is. The Real Constraint Is Decision Latency You can see it in how decisions do or don’t move. A product team identifies an opportunity. It makes its way through architecture review, risk, finance, legal, compliance, and multiple layers of approval. Each step is rational on its own. Each exists for a legitimate reason. Collectively, however, they create latency. By the time a decision is made, the opportunity has changed. It’s worth pausing on that word legitimate. Most of this friction wasn’t installed by accident. Approval layers, architecture review boards, and risk sign-offs typically exist because an earlier version of the organization got burned: a compliance failure, a botched integration, a vendor risk nobody caught in time. Governance is, in effect, institutional memory. The problem isn’t that governance exists. It’s that most organizations never revisit which decisions actually warrant that level of scrutiny and which don’t, so a $50,000 vendor renewal and a $50 million platform migration move through the same gauntlet. This is rarely identified as the primary issue. It gets labeled as “complexity,” “organizational maturity,” or simply “the cost of operating at scale.” But the pattern is remarkably consistent. The system isn’t slow because the technology can’t move. It’s slow because the organization can’t decide, or, more precisely, hasn’t decided, which decisions deserve deliberation and which deserve delegation. Most modernization programs focus on replacing systems of record. They invest in platforms, APIs, cloud infrastructure, developer tooling, and application modernization. The expectation is that once the technology is updated, the business will naturally become faster and more adaptive. But the underlying decision structure remains unchanged. Funding is still annual and project-based. Authority is still fragmented across functions. Accountability is distributed in ways that make outcomes ambiguous. Risk is still evaluated in isolation rather than in the context of business intent. The organization integrates modern technology into its traditional operating model, resulting in predictable outcomes. While teams can move quickly in isolated pockets, overall speed does not improve, and enterprise-wide decisions continue to be delayed. As a result, the organization may seem more active, but it is not necessarily more effective. MIT’s Center for Information Systems Research (MIT CISR) has documented this fragmentation directly. Its research on componentized organizations found that as the digital economy accelerates the pace of business, companies need to redesign their people, processes, and technology to facilitate speed and identified rethinking accountability, not adding new layers of oversight, as the key lever (MIT CISR, “The Digital Operating Model: Building a Componentized Organization”). Organizations routinely measure modernization through cloud adoption, deployment frequency, application retirement, or engineering velocity. Far fewer measure how long it takes the enterprise to recognize an opportunity, make a cross-functional decision, establish clear ownership, and execute with confidence. McKinsey’s research on this exact gap found that only 37 percent of executives believe their organizations make decisions that are both fast and good and that speed and quality are not actually a trade-off, since faster decisions tend to be higher-quality ones (McKinsey, “Decision making in the age of urgency”). Increasingly, that decision cycle, not the technology stack itself, is becoming the true determinant of competitive advantage. Modern Technology Cannot Fix a Legacy Operating Model In practice, the operating model defines how work gets prioritized, how decisions are made, and how tradeoffs are resolved. It determines whether the organization can convert technology capability into business results. When that model is misaligned, even well-executed technology initiatives underdeliver. You can see this most clearly in cross-functional decisions. A customer experience initiative spans multiple systems, business units, and risk domains. Each group operates with its own objectives, constraints, funding model, and measures of success. No single decision-maker owns the tradeoffs across the entire initiative. As a result, decisions are escalated, deferred, or negotiated one function at a time. Nothing breaks. But very little moves with intent. The common response is to add another steering committee, another governance checkpoint, or another approval layer. Those changes may improve oversight, but they seldom improve throughput. The organization becomes more controlled without becoming more responsive. That’s not an argument against governance; it’s an argument for designed governance, calibrated to the actual risk and reversibility of each decision, rather than governance that grows by accretion every time something goes wrong. What it looks like when this actually gets fixed Allstate’s Claims division offers a concrete example of a company redesigning the decision layer rather than the technology layer. In 2021, Claims set out to simplify operations and deliver more frictionless digital experiences to customers. Rather than starting with a new platform, the organization redesigned decision rights: operational authority was pushed down to durable, cross-functional teams built around strategic objectives, replacing a traditional project-based way of working rooted in prescriptive annual plans with a continuous, iterative process (MIT CISR, “Allstate’s Digital Operating Model: Think Big, Act Small”). The technology stack Claims used wasn’t the differentiator. The decision architecture was. Teams that had previously waited on annual planning cycles and cross-functional sign-off could now resolve customer and business problems continuously