WHAT HAPPENS AFTER THE CONSULTANTS LEAVE

I spent the first nine years of my career as a contractor-for-hire, fixing operations. I was good at it. I worked inside gold mines in Peru, financial services companies processing millions of transactions a day, food production plants, energy utilities, and manufacturers across three continents and more industries than most consultants see in a lifetime. The work itself was never the problem. I could walk into an operation, see what was broken, design the fix, and implement it. The numbers would move. The client would be thrilled. I’d leave.

And then, six months later, the phone would ring.

The results had faded. The metrics had drifted. The improvements we’d put in place were slowly being undone, not by some catastrophic failure, but by the quiet gravitational pull of an organization reverting to what it knew. Every time. Different company, different industry, different country. Same outcome.

That pattern is the reason I created The Bismark Method in 2007. But before I explain what I built to solve it, I want to explain what I learned about whyit happens. Because the conventional wisdom about why consulting results don’t last is wrong, and that misunderstanding is costing organizations millions.

THE CONDITION YOU’RE ALREADY IN WHEN YOU PICK UP THE PHONE

No company hires consultants because everything is working. They hire consultants because they’ve already tried to fix the problem themselves and couldn’t. That’s an important starting point, because it means the organization that consultants walk into is already compromised in specific, predictable ways.

First, leadership has lost faith in their own people. They may not say it that way, but the decision to bring in outside help is, at its core, an admission that the internal team either can’t deliver what’s needed or has already failed to. Usually it’s both. The executives have watched their frontline leaders and middle managers promise improvements that didn’t materialize. Sometimes those leaders made commitments they genuinely didn’t have the skills to keep. Sometimes the executives lost patience before the efforts had time to take hold. In many cases, there’s a history of both: a cycle of ambitious plans, partial execution, fading results, and mounting frustration.

This creates an organizational dynamic that nobody talks about in the consulting pitch meeting but that shapes everything that happens next. By the time the consultants arrive, the internal team already knows that leadership doesn’t fully believe in them. They know they’re being supplemented, or replaced, for a reason. And that knowledge doesn’t make them more motivated. It makes them defensive.

Second, the people who are supposed to sustain whatever the consultants build (your frontline supervisors, your department managers, your operations leads) are often in their roles for reasons that have nothing to do with their ability to design and maintain operational systems. They’re there because they were the best individual contributors on the line before they got promoted. They’re there because they’re good with people. They’re there because they’ve been loyal to the company for twenty years. All valid reasons to be in a leadership role. None of them equip a person to design a fit-for-purpose process, build a measurement system, or engineer the workflows that actually drive performance.

This is not a criticism of those people. It’s a structural observation about how most companies fill operational leadership positions. And it’s directly relevant to what happens after the consultants leave, because those are the people who will be left holding the bag.

THE MERCENARY MODEL

Now bring the consultants into this picture.

Consultants are mercenaries. I don’t use that word pejoratively. I was one for nine years. The economics are clear: consultants are paid to deliver specific outcomes on specific timelines. Their contracts and their reputations depend on hitting those numbers. The best firms in the world, McKinsey, BCG, Bain, are brilliant at analysis, at strategy, at identifying what needs to change. But here’s the thing most people in the industry won’t say out loud: the most prestigious consulting firms in the world typically do not get involved with direct implementation. They don’t get into the operations. And there’s a reason for that.

Operations is a messy, grinding, human business. It’s shift schedules and equipment breakdowns and the supervisor who’s been doing it her way for fifteen years. Strategy is clean. Implementation is not. The business model of a firm that bills $500 an hour for senior partners does not reward having those partners spend their Tuesday mornings on a production floor resolving a bottleneck in second shift changeover. The margins don’t support it, the talent doesn’t want it, and the brand would suffer if it became known that your McKinsey team spends half its time in a hard hat arguing about conveyor belt throughput.

So the work gets segmented. The strategy firm diagnoses and recommends. The implementation, the actual doing, gets handed to the client, or to a different tier of consultant, or to an internal team that may or may not have the skills to execute what was recommended. This is the first consulting failure mode: recommend and leave. The analysis is rigorous. The recommendations are sound. The PowerPoint is beautiful. And the organization is left holding a roadmap it doesn’t have the capabilities to follow.

The second failure mode shows up when the consulting firm does stay for implementation. Now you have a team of highly paid, highly skilled outsiders doing the work for the client’s people rather than with them. The consultants design the processes, build the systems, install the metrics, and deliver the results. The numbers look great. The engagement ends. And the client’s own team, the people who were there before and will be there after, watched it happen like spectators. They didn’t design the new process. They don’t understand why the metrics are structured the way they are. They can follow the new procedures, but they can’t maintain them, adapt them, or improve them, because they were never taught how. This is implement for you, and it produces results that are impressive on paper and fragile in practice.

SURVIVE UNTIL THEY LEAVE

Here’s where it gets uncomfortable.

In the second model, consultants implementing for you, there’s a dynamic that develops inside the client organization that I’ve seen in virtually every engagement I’ve ever observed or inherited. The internal employees know the consultants are temporary. Many of them have been through this before. A previous firm came in, changed everything, and eventually left. Some of those changes stuck. Most didn’t. The institutional memory of the organization includes a deeply held pattern: this too shall pass.

When you combine that institutional memory with the pre-existing dynamic (leadership doesn’t fully trust the internal team, the internal team knows it, and many of them lack the skills to genuinely engage with the work the consultants are doing) you get a survival strategy that nobody announces but everyone practices. The frontline and middle management adopt the new processes just enough to stay out of trouble. They attend the meetings. They fill in the new forms. They hit the numbers while the consultants are in the building, watching. But they are not invested in the change. They are enduring it. They are waiting for the consultants to leave so they can go back to something more comfortable, or at minimum, something they actually understand.

And here’s the part that rarely gets discussed: many of these employees have real job security. They’ve been with the company for years. They have relationships up and down the org chart. They know that the consultants are the ones on a clock, not them. So the calculus is simple. Do enough to stay out of the crosshairs. Don’t fight the changes openly. Wait it out.

The consultants, who are smart people operating under contract pressure, often sense this but don’t have the time or the mandate to address it. Their job is to deliver the contracted outcomes by the contracted date. If the numbers are moving in the right direction, the engagement is succeeding. What happens after they’re gone is, structurally, not their problem. Their reputation is built on the results they delivered, not on the results that lasted.

I want to be clear: I’m not describing bad consultants. I’m describing rational actors inside a broken model. The consulting industry’s incentive structure rewards delivery, not durability. The firms that have built the most successful practices in the world have done so by being excellent at a specific part of the value chain (diagnosis, strategy, or short-term implementation) and none of those parts require the results to sustain after the firm leaves.

THE MAINTENANCE TRAP

So the consultants leave. The numbers were good on the final report. Leadership is cautiously optimistic. And the internal team, the same frontline supervisors and middle managers who watched the consultants do the work, is now responsible for maintaining the gains.

At first, they do. The processes are fresh. The metrics are visible. The memory of the consultants is still in the building. For a few weeks, sometimes a few months, the operation holds.

Then reality sets in.

A process exception comes up that wasn’t covered in the new procedures. A team member pushes back on a new standard. A piece of equipment changes the throughput calculation. And the supervisor or manager who’s now responsible for the process doesn’t know what to do. Not because they’re incompetent, but because they were never taught how to design. They can follow a process that someone else built. They cannot diagnose why it’s failing, redesign it for a new condition, or build a new measurement approach that captures the actual performance drivers. They were trained to operate, not to engineer.

Worse, they often lack the leadership skills to address the human side of what’s happening. When a team member isn’t following the new standard, the root issue is usually not defiance. It’s a gap in understanding, or a conflict between the new process and the way the work actually flows, or a personality dynamic that requires a difficult conversation. Consultants handle these situations reflexively because it’s a core competency of the profession. But the internal leader who’s now responsible for the process may not have the skills or the confidence to address interpersonal friction, enforce accountability, or navigate the kind of conflict that comes with sustained change. So they avoid it. Or they address it indirectly. Or they escalate it to someone who doesn’t have time.

The result is drift. Not a collapse. A drift. The metrics slip a little. Then a little more. Standards loosen. Workarounds creep back in. Within six to twelve months, the operation has reverted to something that looks recognizably like what it was before the consultants arrived, just with newer forms and a more expensive set of procedures that nobody fully follows.

THE GRAND MISPERCEPTION: IT MUST BE THE PEOPLE

Here is where most organizations make the mistake that costs them the most.

When the results fade, leadership looks at the situation and draws what seems like a reasonable conclusion: the processes were good, the consultants built them, and the numbers proved they worked. So if the processes were good and the results still faded, the problem must be the people. The supervisor in Department B isn’t the right fit. The operations manager doesn’t have the right mindset. The VP needs a fresh pair of eyes on the team.

And so the organization reaches for the one lever it knows how to pull: the org chart. They restructure. They move people around. They bring in new leaders from outside. They reorganize departments, consolidate reporting lines, create new roles. The logic feels airtight: if the ways of workingwere validated by the consultants and the results still didn’t hold, it must be the individuals who failed.

This is the grandest misperception in operational management: the belief that when a well-designed process fails to sustain, the fault lies with the personalities and individual traits of the people running it, rather than with the organization’s failure to build the capability to maintain, adapt, and improve it.

The processes weren’t sustained because nobody in the organization was ever given the skills to sustain them. The leadership didn’t hold because nobody taught the leaders how to lead through process change. The accountability faded because nobody built an accountability system that the internal team understood well enough to own. The consultants built a machine and handed the keys to people who were never taught to drive it. And when it stalled, leadership blamed the drivers instead of the training.

The org chart move feels decisive. It feels like leadership. But it’s actually the most expensive way to avoid addressing the real problem, because the new people who come in will inherit the same structural gap. They’ll have different personalities but the same missing capabilities. And in twelve months, leadership will be looking at the org chart again.

THE OBJECTIONS I KNOW YOU’RE THINKING

I’ve made this argument to executives, to consultants, and to boards for nearly twenty years. By now I know the objections before they come, and they deserve honest answers.

“You’re a consultant yourself. Isn’t this a sales pitch disguised as an insight?”

Fair question. Yes, I run a consulting firm. Yes, I’m describing a problem that my firm was specifically built to solve. I don’t pretend that makes me a neutral observer. What I’d ask you to consider is whether the pattern I’m describing matches your experience. If you’ve hired consultants before and the results faded within a year, you already know the cycle I’m talking about. The question isn’t whether I have a stake in the answer. The question is whether the answer is accurate.

“Sometimes it really is the wrong person in the role. You can’t train your way out of a bad hire.”

Absolutely true. There are cases where someone genuinely does not belong in the role they’re in, and no amount of coaching or skill-building will change that. I’ve seen it. I’ve had to have those conversations with clients. But here’s the distinction that matters: you cannot know whether it’s a people problem or a capability problem until the capability gap has been addressed. If you move someone out of a role before giving them the skills the role actually requires, you haven’t made a diagnosis. You’ve made an assumption. And most organizations skip the diagnosis entirely because restructuring is faster, more visible, and feels more like a decision. The ones who do the skills work first are often surprised by how many of those “wrong people” turn out to be the right people who were never given the right tools.

“Plenty of consulting engagements produce results that last. You’re overgeneralizing.”

Some do. And when I look at the ones that do, they almost always share a specific characteristic: the engagement included meaningful knowledge transfer to the client’s team, whether that was the firm’s intent or a byproduct of how the work happened to unfold. A consultant who works shoulder to shoulder with a client employee for six months will transfer skills by proximity even if the engagement model doesn’t require it. The issue isn’t that lasting results are impossible under traditional models. It’s that lasting results happen despite those models, not because of them. When results sustain, it’s usually because a particular consultant went beyond the contract, or because a particular client employee was exceptional enough to absorb what they observed. That’s luck, not a system.

“What about Lean and Six Sigma programs? Those are specifically designed to build internal capability.”

They are, and I have deep respect for both frameworks. I’m a certified Lean trainer and a Six Sigma Black Belt. The tools work. The question is how they’re deployed. In most organizations, Lean and Six Sigma programs train individuals in methodology and then send them back into an organization that hasn’t changed its leadership practices, its process design approach, or its measurement systems. You end up with certified people operating inside unreformed structures. They know how to run a Kaizen event, but the operation they’re running the event inside doesn’t have the process architecture or the leadership alignment to sustain what the event produces. The skills are real. The organizational infrastructure to use them is often missing.

“You’re being unfair to McKinsey and the strategy firms. Their role is strategy, not implementation. That’s not a failure.”

I agree with that completely. McKinsey, BCG, and Bain are exceptional at what they do, and what they do is not implementation. I’m not criticizing them for staying out of operations. I’m pointing out that the industry has a structural gap between the firms that design the strategy and the organizations that have to execute it. The strategy firms occupy one end. The implementation firms occupy the other. And the space in the middle, where the client’s own people need to be built into the solution rather than served by it, is largely unoccupied. That’s not a criticism of any firm. It’s an observation about the industry. The gap exists whether you find it uncomfortable or not.

WHAT HAS TO BE STRUCTURALLY DIFFERENT

I spent nine years watching this cycle from the inside before I understood it well enough to build something that breaks it. The insight wasn’t complicated. It was just uncomfortable for the consulting industry to accept.

If the results fade because the internal team doesn’t have the skills to sustain them, the answer isn’t to build better processes for them to follow. The answer is to build better people. To transfer the actual design skills, the diagnostic capabilities, and the leadership competencies so that the client’s own team can do what the consultants did. Not follow what the consultants built. Do what the consultants did. Design processes. Engineer measurement systems. Diagnose failures. Have the hard conversations. Lead through change rather than administer through compliance.

That’s the principle The Bismark Method was built on in 2007, and it’s the reason the model works the way it does. Monday classroom sessions where the actual skills are taught. Tuesday through Thursday, hands-on coaching where dedicated apprentices from the client’s own team apply what they learned. A sequential structure that ensures the foundational work is done before the more complex work begins. It’s not a faster or more efficient version of traditional consulting. It’s a fundamentally different model, what I call coach to build, the third mode that neither the strategy firms nor the implementation firms occupy.

The strategy firms don’t occupy it because it requires being in the operations, and that’s not their business. The implementation firms don’t occupy it because teaching the client to do the work eliminates the dependency that drives repeat engagements. And most internal improvement teams don’t occupy it because they tend to start with organizational restructuring, moving people around on the org chart before the process design work has been done, which guarantees they’ll have to redo the work once they realize the structure doesn’t match the process.

I’ve coached over eighty clients through this model across ten industries and three continents. The ones where the results sustained, and I mean truly sustained, years after we left, are the ones where the client’s own people could stand in front of their leadership team and explain not just what had changed, but why it was designed that way, and what they would do differentlyif the conditions changed. That’s not maintenance. That’s ownership. And it’s the only thing that lasts.

The consulting industry doesn’t have a quality problem. It has a structural one. The model rewards firms for delivering results, not for building the client’s capacity to sustain them. And until that changes, the phone will keep ringing six months later.

The question isn’t whether your last consulting engagement produced results. It almost certainly did. The question is whether your team can explain why those results happened, adapt the approach when conditions change, and improve on what was built without picking up the phone.

If they can’t, the problem isn’t your people. The problem is the model that was used to get you here.