Two Divisions. Two Results.

Years ago, while I was working with a management consulting company, our team was engaged by a large corporation to help improve its supply chain operations. I served as the project lead.

The company had multiple divisions, and we began by implementing a new process in one of them. It wasn’t an experimental methodology. It was a disciplined process built around principles and practices our consulting team had successfully implemented elsewhere.

The first implementation was an extraordinary success. The key performance indicators didn’t just improve; some reached levels the organization had never achieved before.

The numbers were gratifying, of course. But something else had happened that was every bit as important.

The division’s leadership had gotten behind the project.

They didn’t simply approve it. They supported it.

There is a considerable difference between the two.

They made it clear that the work mattered. They participated, reinforced the changes, and helped solve problems when they arose. Their people understood that this wasn’t another corporate initiative that would disappear when management’s attention moved elsewhere.

It worked.

With results like those, the logical next step was obvious: take what we had learned and implement the same process in another division.

Same corporation. Same facility. Same consulting team. Same methodology.

We knew the process worked because we had just demonstrated it. There was every reason to expect another success.

We didn’t get one.

What Changed?

Corporate leadership expressed support for the second implementation, but there was resistance beneath the surface. Some members of the leadership team were skeptical of what we were doing. Others were openly critical.

Then came a decision that, looking back, told us almost everything we needed to know.

Several of the project’s strongest critics and detractors were assigned to the implementation team.

Think about that for a moment.

We were asking people who didn’t believe in the change to help lead the change.

The process hadn’t changed. The underlying principles hadn’t changed. The consulting team hadn’t changed.

But the environment had.

The first division’s leaders had created conditions in which the new process had an opportunity to succeed. In the second division, leadership created conditions that made success extraordinarily difficult.

The results reflected that difference.

The second implementation failed.

For consultants, that’s an uncomfortable thing to say. We prefer talking about successes. They make better case studies.

But I probably learned more about organizational change from comparing those two implementations than I would have learned from two successes.

Leadership Is Part of the Process

Organizations spend enormous amounts of time evaluating methodologies. Which system should we implement? Which consulting firm should we hire? Which technology should we purchase? Which process should we adopt?

Those are legitimate questions.

But there is another question that should come first:

Are we prepared to lead the change required to make this work?

Leadership support cannot consist merely of approving a project, allocating a budget, and telling everyone else to cooperate.

People watch what leaders actually do. They notice who gets assigned to the project. They notice whether resistance is confronted or accommodated. They notice whether senior leaders participate when things become difficult.

And they quickly determine whether the initiative really matters.

That doesn’t mean everyone must agree with every decision. Healthy skepticism can make an implementation better. Good leaders should invite difficult questions and listen to people who see problems others have missed.

But there is a fundamental difference between constructive skepticism and putting people in charge of a change they are committed to resisting.

We learned that difference the hard way.

Same Process. Different Leadership.

Our consulting team had implemented similar processes in organizations throughout the country. Naturally, no two implementations are identical. Every company has its own people, culture, constraints, and challenges.

But these two projects gave us something unusual.

They allowed us to see essentially the same methodology implemented inside the same corporation, in the same facility, by the same consulting team, with dramatically different leadership environments.

One produced outstanding—at times record-breaking—results.

The other failed.

That’s why, when someone tells me an organizational improvement effort is primarily about selecting the right system or methodology, I know there’s another part of the conversation we need to have.

Processes matter. Systems matter. Expertise matters.

But none of them operates independently of leadership.

Before beginning the next major change initiative, don’t ask only whether you’ve selected the right process. Ask whether your leadership team is genuinely prepared to lead it.

Because sometimes the difference between extraordinary results and failure isn’t the process at all.

It’s whether the people leading the organization actually believe in what they’re asking everyone else to do.