Consultants Can Map a Transformation. They Can't Make It Stick.

Published 2026-07-23 · Updated 2026-06-26 · By Alan Wizemann

Topics: Digital Transformation, Growth Leadership, Enterprise, Board/Advisory

I have watched the same thing happen enough times now that I have stopped being surprised by it, which is its own kind of sad. A company decides it needs to transform, usually because the world moved and the business did not, and it does the thing that feels safest in the moment. It hires one of the big-three consultancies, spends an amount of money that would make most people lightheaded (we are talking many millions, sometimes many tens of millions), and a few months later it gets a beautiful map that is, to be fair, genuinely good. The slides are immaculate, the frameworks are sound, and the future state is drawn so clearly you could almost reach out and touch it. And then the consultants pack up and leave, and the whole thing quietly comes apart over the following months.

I do not say that to be unkind to the consultants, because the honest ones will tell you the same thing themselves. I have sat across from them when they admitted, more or less directly, that the moment they walk out the door it falls apart. Not because the work was bad. Because there was no internal leadership left to carry it, and no teams were ever actually formed through it. The whole effort was run as a project, with a start date and an end date and a deliverable, and transformation is not a project. I have seen this play out at companies people would recognize – the kind of business that hires the best firm in the world and still ends up exactly where it started a year later, only poorer.

Here is the part that gets missed in the conference room. The things a company is trying to build in one of these efforts – the digital products, the new capabilities, the new way of working – are evergreen. They have to run and grow for the life of the company, the way a heart has to keep beating, not finish like a renovation. A project has a clean ending built into its very definition, and a capability, by its nature, never does. So when you hand the most important, longest-lived work the business will ever do to a team whose entire model is to finish and leave, you have a structural mismatch baked in from day one, and no amount of slide quality fixes it.

The better shape is not complicated, though it is harder. Let the consultants build the framework if you find that valuable, I have no quarrel with that part of it. But bring in a leader, an actual internal owner, whose job is to take that framework and turn it into a strategy, tie that strategy to where the company is genuinely trying to go, operationalize it, and then – this is the part everyone underweights – execute it until it sticks. A framework is a description of the destination. A strategy tied to a vision and carried by a person who answers for the outcome is the thing that actually gets you there.

There is a human truth under all of this that I think explains most of the failures. The second a company brings in consultants and starts saying the word "transformation," everyone in the building hears something very specific, which is "we are all about to get fired." You can give whatever reassuring speech you like; that is what they hear, and people who believe they are being optimized out of existence do not pour themselves into the change. When you do it internally instead, using the people who are already there and moving them into new roles, new career paths, and new ways of working, the whole thing becomes survivable, even exciting. It is far more sustainable, because the people carrying it forward have a reason to want it to last.

The strangest part of this kind of role, and the part I have made peace with, is that it is built to make itself unnecessary. If I am doing it right, my entire job is to assemble the teams and the vision, and then to make sure those teams genuinely own it, so that the day I leave the reaction in the room is "we've got this" and not "well, that guy left, now what?" The person who succeeds me usually carries the same title I did, but they have a genuinely different job, because mine was to transform and theirs is to sustain, maintain, and grow what was built – which is hard in its own way, but it is not the same hard, and it asks for a different kind of leader.

I will be honest about the times it did not hold, because they taught me as much as the wins. The companies that fell backwards almost always did the same thing, which was to change the model after I left – flatten the ownership, fold the teams back into the old structure, treat the living capability like a finished project again. A few of them called me back for a month or two to help restore what had come apart (I will keep them anonymous, they know who they are), and there is no satisfaction in that, only the confirmation of the pattern, which is that the thing was never the framework and was always, every single time, whether anyone inside had been built to carry it.

Which is the whole point, and it is the one line I keep coming back to when a board asks me why they should not just hire the famous firm and be done with it. A plan is something you can rent. A capability is something you have to build, with your own people, over real time, owned by someone who will still be there long after the consultants and even after you. The map was always the easy part, and the map was never the thing that was going to be hard.