{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicvwhi4o5k4kunk6nvzcvlkyeewe52jgge32tjqjizqtkj3sopx4m",
    "uri": "at://did:plc:qz6ohvpdsdvv5kniizyfz25y/app.bsky.feed.post/3mllkrqjsl7e2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreigptqludvyda2xxlxcm3ffjkvrttzfxyk4elhziqc57xe5mejmusu"
    },
    "mimeType": "image/jpeg",
    "size": 1801479
  },
  "path": "/article/4168935/your-operating-model-is-the-real-legacy-system.html",
  "publishedAt": "2026-05-11T11:00:00.000Z",
  "site": "https://www.cio.com",
  "tags": [
    "Digital Transformation, IT Leadership, IT Management",
    "operating model transformations",
    "AI doesn’t create value",
    "digital and AI transformation",
    "Want to join?"
  ],
  "textContent": "For the past decade, enterprise modernization has been framed as a technology problem.\n\nLegacy systems. Technical debt. Monoliths that need to be broken apart and moved to the cloud.\n\nThat framing is convenient and also incomplete.\n\nIn most organizations, the technology isn’t the constraint. The operating model is.\n\nYou can see it in how decisions move — or don’t. A product team identifies an opportunity. It makes its way through architecture review, risk, finance and multiple layers of approval. Each step is rational on its own. Collectively, they create latency.\n\nBy the time a decision is made, the opportunity has changed.\n\nThis is rarely called out as the primary issue. It gets labeled as “complexity” or “scale.” But the pattern is consistent. The system isn’t slow because the technology can’t move. It’s slow because the organization can’t decide.\n\nThat distinction matters.\n\nMost modernization programs focus on replacing systems of record. They invest in platforms, APIs and cloud infrastructure. The expectation is that once the technology is up to date, the business will move faster.\n\nBut the underlying decision structure remains unchanged.\n\nFunding is still annual and project-based. Authority is still fragmented across functions. Accountability is distributed in a way that makes outcomes ambiguous. Risk is still evaluated in isolation, rather than in the context of business intent.\n\nSo, the organization implements modern technology on top of a legacy operating model.\n\nThe result is predictable.\n\nSpeed doesn’t increase. It fragments. Teams move quickly in isolated pockets while enterprise decisions continue to stall. The organization appears more active, but not more effective.\n\nThis is where many transformation efforts quietly lose momentum.\n\nMost organizations don’t recognize it at the time. It just feels like things are taking longer than they should.\n\nFrom the outside, progress is visible. Systems are upgraded. Agile is adopted. Cloud adoption metrics improve. But inside the organization, the experience is different. Decision cycles are still long. Dependencies are still opaque. Tradeoffs are still negotiated too late.\n\nThe operating model absorbs the change and neutralizes it. McKinsey has observed the same pattern in operating model transformations: The organization starts to change, but under pressure, decision-making fragments, accountability weakens and the system defaults back to how it has always operated.\n\nThis is why some of the most heavily invested technology environments still struggle to produce consistent business outcomes.\n\nThe issue isn’t capability. It’s coordination.\n\nEven at the CIO level, the pattern is getting harder to ignore: AI doesn’t create value. Organizations do, and most aren’t structured to do it consistently.\n\nIn practice, the operating model defines how work gets prioritized, how decisions get made and how tradeoffs are resolved. It determines whether the organization can convert technology capability into business results.\n\nWhen that model is misaligned, even well-executed technology initiatives underdeliver.\n\nYou can see this most clearly in how organizations handle cross-functional decisions.\n\nA customer experience initiative spans multiple systems, teams and risk domains. Each group operates with its own priorities and constraints. There is no single point at which trade-offs are made with full context.\n\nSo, decisions are escalated, deferred or negotiated incrementally.\n\nNothing breaks. But nothing moves with intent.\n\nOver time, this creates a form of structural drag. Not visible enough to trigger intervention, but persistent enough to erode performance.\n\nOrganizations respond by adding more process. More governance. More coordination layers.\n\nThe system becomes more controlled, but not more effective.\n\nThat same pattern shows up in execution. It doesn’t collapse; it fragments. Alignment fades, coordination weakens and progress slows despite the capability being there. This is a failure mode McKinsey has also highlighted in its work on digital and AI transformation.\n\nThis is the paradox many CIOs are now navigating. Technology has advanced to the point where it can support far more adaptive, responsive businesses. But the way the enterprise is structured for decision-making hasn’t kept pace.\n\nSo, the constraint has shifted.\n\nIt’s no longer primarily in the systems.\n\nIt’s in the way the organization operates those systems.\n\nThis is also why comparisons between companies in the same industry can be misleading. Two firms may run similar technology stacks, use the same cloud providers and invest at comparable levels.\n\nYet their outcomes diverge.\n\nOne moves with clarity, the other stalls under its own weight.\n\nThe difference is not the technology.\n\nIt’s how decisions are made, who owns them and how quickly they can be executed.\n\nThat is the operating model.\n\nAnd in many enterprises, it is now the oldest system in the environment.\n\nIt carries forward assumptions about control, risk and coordination that were designed for a different era. An era where change was slower, systems were more centralized and decisions could be sequenced over time.\n\nThat environment no longer exists.\n\nBut the model remains.\n\nSo, organizations continue to invest in modern technology while relying on a legacy structure to use it.\n\nThe gap between what the technology can do and what the organization can execute continues to widen.\n\nAt a certain point, that gap becomes the defining constraint on performance.\n\nNot because the systems are outdated.\n\nBut because of the way the enterprise operates them.****\n\n**This article is published as part of the Foundry Expert Contributor Network.**\n**Want to join?**",
  "title": "Your operating model is the real legacy system"
}