In a meeting last month, a senior executive mentioned without a hint of irony: “We need to transform our transformation.” The room didn’t flinch. That’s how far gone we are. It’s been roughly a decade since “digital transformation” entered the corporate lexicon, and the phrase has been stretched to mean everything and nothing. It’s on every strategy deck, every annual report, every keynote. And yet, the results are… underwhelming. Depending on which analyst you read, somewhere between 70% and 85% of digital transformation initiatives fail to deliver their intended outcomes.
Let that sit for a moment. An entire industry built around a concept with a failure rate that would shut down a restaurant.
Why Transformations Stall
These patterns seem to emerge:
- The label replaced the work. Somewhere along the way, digital transformation became a brand rather than a discipline. Organizations created programs, hired chiefs, stood up teams, built decks, confusing the scaffolding with the building. Having a digital transformation office doesn’t mean you’re transforming any more than having a gym membership means you’re fit.
- The scope became everything. When transformation means everything, it means nothing. I worked with a media company last year that had dozens of initiatives under their transformation umbrella. From replacing their CRM to redesigning the lobby. In fairness, the lobby was to have a digital kiosk.
- The technology got ahead of the problem. Too many organizations start with a technology choice and work backward to the business case. “We’re moving to the cloud” or “We’re becoming API-centric” sounds decisive. But decisive about what? For whom?
Then there’s an anti pattern: middle gets stuck. Executive sponsors get the vision. Delivery teams get agile. But the layer in between who built their careers on the old model is caught. One analyst research paper I came across called this layer the “permafrost”, the frozen middle that blocks everything from taking root, no matter how much heat comes from the top. Its provocative conclusion was that you’d have to fire two-thirds of them to truly transform. I don’t think that’s the answer, but the diagnosis rings true. These are people who rose through the ranks by mastering how things work today. They know the governance, the vendor relationships, the budget cycles, the reporting lines. That expertise is real and hard-won. Now they’re being asked to champion an operating model that flattens hierarchies, distributes decision-making, and values speed over certainty. In other words, the transformation they’re asked to lead dismantles the very structures that give them meaning. So they add governance to the agile process. They create steering committees for the autonomous teams. They translate the new language into the old operating model, and the transformation quietly calcifies into something that looks different but behaves the same. It’s one of the biggest silent killers of transformation.
The Chief Digital Officer Problem
Here’s a controversial take. The CDO role, in many organizations, has become part of the problem. Not because the people in these roles aren’t talented or skilled. They usually are. But the role itself creates a convenient fiction: that transformation is someone’s job. It gives everyone else permission to keep doing what they were doing, because hey, the CDO is handling the digital stuff.
The best organizations I’ve worked with don’t have a CDO by title. They have leaders across the business who own digital outcomes as part of their actual job. The transformation isn’t a separate program that runs alongside the business. It is the business.
The Transformation Fatigue is Real
Talk to people in the trenches and you’ll hear it. They’re tired. They’ve been through three reorgs, two methodology changes, and a platform migration. They’ve been told to be agile, then told to scale agile, then told that agile isn’t enough and they need to be product-oriented. They’ve sat through design thinking workshops and innovation labs and hackathons, and then gone back to their desks to fight with the same legacy systems and structures they had before. It’s a rational response to watching a revolving door of initiatives that promise change and deliver disruption without progress.
Wow, That was Depressing, So Now What?
The organizations that are making real progress share a few characteristics, and none of them are glamorous:
- They’re ruthlessly specific about outcomes. Not “become digital” but “reduce customer onboarding time from three weeks to two days.” Concrete, measurable, tied to value that someone in the business actually cares about.
- They fund small and fast. Instead of an eighteen-month program with a 200-page business case, they fund ninety-day experiments with clear hypotheses. If it works, scale it. If it doesn’t, kill it, learn and move on. The sunk cost fallacy of large programs is one of the biggest enemies of real transformation.
- They invest in the boring stuff. Data quality. Process simplification. Technical debt. Nobody puts “we cleaned up our master data” on a conference slide, but it’s often the thing that unblocks everything else.
- They change how they measure success. Not project milestones and budget variance, but business outcomes and speed of learning. The dashboard that matters isn’t the one the PMO produces, shocker. It’s the one the customer sees.
The Phrase Doesn’t Matter
My prediction for the 2020s is that the phrase “digital transformation” will quietly fade from strategy decks. The work will still be done, but organizations that figure it out will stop calling it that. It’ll just be how they operate. The ones that don’t figure it out will rebrand it as something else and start the cycle again. Wheee!
