A digital transformation announced in January and stalling by summer is not unusual. It is the normal case. I have led transformations at large companies and small ones: a $3B automotive platform with a thousand-plus engineers, a hundred-person venture-backed startup, and a public software company between them. I have sat on the board while portfolio companies attempted them and watched what venture and private equity pressure does to them. I have been called in after they stalled by major retailers, insurance companies, and technology companies. The versions differ: organizational design, who is accountable for the transformation and who is merely empowered to attempt it, the investor's clock. The pattern does not. That lived experience is the playbook. It is what lets me name the pattern in the first conversation and fix the right thing instead of the visible thing.
The one that failed three times
A large healthcare company spent more than twenty million dollars on three failed attempts to move to the cloud. The technology was never the problem. The first attempts were run by infrastructure. The software teams whose systems were being moved fought with infrastructure the whole way, because their designs were never part of the plan. Infrastructure was executing a migration; software was living with the result. And the team leading the transformation was also the team it would disrupt the most. The focus was on checking a box, not on achieving a business outcome.
It worked on the fourth attempt, and the difference was not a new platform or a new vendor. It was organizational. The company put software and infrastructure under one leader, accountable for the outcome rather than the activity, and the conflict that had stalled three programs disappeared because it no longer had two sides. The migration completed. What followed was a dramatic increase in engineering production, and in the speed and performance customers experienced.
That is the shape of most stalls I see. Nobody is lazy. Nobody is wrong. The work is organized so that the people who have to make it succeed are the people it hurts, or the people who need each other report to different bosses with different scoreboards.
Why digital transformations stall
I wrote most of this list in 2022, and every stall since has fit it.
Ownership sits in the wrong place. The team running the change is the team the change disrupts, or the two teams that need each other report to different leaders with different numbers. You get what you organize for. A transformation run by one side of a conflict will produce the conflict.
Accountability is for activity, not outcomes. The group that owns the result has to be accountable for it even when it depends on another group, or the review becomes a blame exchange between two teams that were each on plan.
There is no business problem, so there is no measure. "Move to the cloud" is a tactic, not a destination. If the leadership team cannot say what the transformation will make true, in a number, by a date, the program will be measured on activity, and activity is where stalls hide. The healthcare company was measuring completed migrations. The business outcome it needed was never written down.
The people being changed were not told how it affects them. Every employee's first question is "what does this mean for me," and nobody does their best work in survival mode. If the answer is "your job gets automated" and nobody says it, the people closest to the work will slow it down without ever refusing anything.
Decision rights were never settled. Who decides sequencing, who decides what the old business gives up, who decides when a workstream is done. When two people each believe it is theirs, everything is busy and nothing moves.
Leadership stops deciding. This is the one that surprises boards. Transformations rarely die in the teams. They die in the executive suite, when the leaders stop making the calls about outcomes, funding, and what gets stopped, and start reviewing dashboards instead. Without leadership, some transformations simply will not succeed, and no amount of vendor or methodology changes that.
A transformation I owned when the numbers were under pressure
When I arrived at New Relic as EVP and General Manager, our largest customers said we had not shipped meaningful innovation in nearly three years. Sales had no confidence that product and engineering could deliver, and customers were looking at competitors. Revenue was $300 million and the plan said $500 million.
What I stopped: product and engineering reporting to different leaders with different measures. I appointed a general manager to align both on business metrics, which ended the finger-pointing because there was no longer a second finger.
Who resisted: the leaders who were on plan by their own number. Each function was hitting its scoreboard while the company missed the customer.
What unlocked it: a quarterly planning session that set a specific allocation of engineering capacity across the roadmap, bugs, and new sales commitments, and a cross-company escalation meeting where any change to the roadmap had to be argued and agreed by the leaders of the company, in the open. Trade-offs stopped happening under the hood.
Six months later, at our Customer Advisory Board, the CTO of Disney and an SVP at Capital One told us we had delivered more of what they wanted in six months than in the previous three years. That translated into roughly fifty million dollars in new sales within five months, and the company went on to $500 million.
What I look for in the first thirty days
I do not start with a maturity assessment or a new roadmap. I start with the pattern, and the pattern shows up in five questions asked of every executive, one on one.
What problem is this transformation solving, and how will we measure it? If the answers differ across the room, the program has no destination, only tactics.
Who owns it, and is that the person it disrupts? I ask who runs it, who reports to them, and who has to live with the result. If the answer is a team on one side of a conflict, or two teams that report to different leaders, I have usually found the stall.
Who has the decision? Sequencing, what the old business gives up, what "done" means. Unsettled decision rights look like disagreement about the plan. They are not.
Do the scoreboards fight? Each leader's number, side by side. If sales, engineering, and operations can each hit their number while the transformation fails, the incentives are the problem, not the people.
Does the leadership team believe it is a must? I ask each of them, alone, what happens if it does not get done. If nobody can answer, the stall is the honest answer to a question the kickoff never asked.
By the end of the thirty days I know which of the six causes is doing the damage, and I write it down for the CEO in plain language, with the one or two decisions that restart it. It is rarely all six. It is never the one the kickoff deck named.
What you should expect from an advisor
The right advisor should be willing to say uncomfortable things, work with the CEO privately, and then help the leadership team turn those conclusions into operating commitments with owners and dates. Be wary of anyone whose main deliverable is a maturity assessment, a new roadmap, or another offsite.
Ask any advisor, including me: tell me about a transformation you personally owned when the numbers were under pressure; what did you stop doing, who resisted, and what decision unlocked progress; how would you diagnose our situation in the first thirty days; what access would you need; and what would make you tell me the current transformation leader, or I, should be replaced. My answers are above. The last one is simple: when the person leading the change is the person the change disrupts most, and cannot be moved out of that position, the program will fail again, and I will say so.
Operating partner, turnaround consultant, or advisor: which does a stall need?
An operating partner takes a seat and owns an outcome; that is the right answer when the stall is a leadership gap. A turnaround consultant runs a process against a deadline, usually a cash deadline; the right answer when the stall is a survival problem. An advisor stands beside the CEO over time while the CEO makes the calls; the right answer when the leadership is sound and the transformation is not. I work all three ways, and most stalled transformations need the third, with the first held in reserve.
What an engagement involves, and how it is priced
The first thirty days are the diagnostic above: interviews with every seat, the plan tested against the causes, a written verdict the CEO can act on. After that, the work takes one of three shapes: standing advisory, a scoped project with owners and dates, or transformation leadership, which is priced like the operating commitment it is. What moves the number is scope, cadence, and how much of the work is on-site. We agree on it at the discovery call, once we both know the shape of the work. I do not publish fees.
Common questions
Why do transformations stall at six months? Because the launch runs on enthusiasm and month six runs on the operating model, and most transformations never changed the operating model. The old business still wins every resource fight, and the people being changed were never told what it means for them.
What are the signs an executive team is avoiding a decision? Every workstream is on track and the total is late. The resource conversation is always next quarter's. Two executives each describe the same decision as the other's.
What does a diagnostic for a stalled transformation involve? Thirty days: every executive interviewed one on one, the plan tested against the six causes, a written verdict with the one or two decisions that restart it. Priced as a scoped project.
How is an operating partner different from a turnaround consultant? One takes a seat and owns an outcome; the other runs a process against a deadline. A stall usually needs neither first. It needs the decision nobody has made.
Can a transformation be restarted without replacing the team? Usually. Most stalls are ownership and decision problems, not talent problems. The exception is when the leader of the change is the person it disrupts most and cannot be moved; then the structure has to change before anything else can.
Why do most digital transformations fail? The consultancies' own surveys put it at about seven in ten, and some higher. In my experience the number matters less than the pattern. They fail for the six reasons above, and the first two are organizational: the work is owned by the team it disrupts, or measured on activity instead of an outcome. Technology is almost never the cause. A transformation announced with conviction and stalling by month six is usually one unmade decision away from restarting.