How One Manufacturer Made the Strategy Stick

What did this manufacturer do differently?

In Part 1 of this series, we introduced two manufacturers that launched the same operational improvement initiative after winning major new contracts. One succeeded. One didn't. This post is about the one that succeeded — and specifically what they did that the other company didn't.

The short answer: they treated the strategy as a commitment to change how work actually happened, not just a commitment to a better outcome.

How did they connect strategy to daily work?

Before anything else changed, the leadership team did something most companies skip: they mapped current reality. Not the process-as-documented, but the process-as-lived. What actually happens when an order comes in? Who touches it? Where does it wait? Where do people work around the system because the system doesn't match what the job requires?

That mapping surfaced three specific handoff points where the old process would break under the new contract's volume and timing requirements. Those three points became the focus of the improvement effort — not the initiative broadly, but those specific friction points.

From there, they redesigned the workflows around the new volume before touching the technology. People's actual job responsibilities changed. Accountability shifted. The daily cadence of floor communication changed. Supervisors had a different set of questions to answer each morning.

The strategy didn't just get communicated. It got operationalized.

How did systems support the new way of working?

The system upgrade came last — not first.

This is the sequence most companies get backwards. They buy the new platform, go live, and then wonder why the team isn't using it the way the vendor demo suggested. The reason is usually that the platform was configured around the old workflow. It automates the wrong things. It surfaces the wrong information. It creates work instead of removing it.

This manufacturer took the redesigned workflows and used them as the specification for the system configuration. The system was built around how work was supposed to happen — not the other way around.

Adoption wasn't a training problem. The system matched what people were already doing, so it felt like a natural extension of their work instead of a new obligation layered on top of it.

What were the results?

Eighteen months after the contract win, this manufacturer was absorbing the new volume without proportional headcount increases. Lead times held. Defect rates stayed flat. Floor supervisors could tell you, at any point, where every order was and when it would ship.

The initiative delivered not because leadership was especially talented or the strategy was especially clever. It delivered because strategy, work, and systems moved together.

What does Part 3 cover?

Part 3 follows the other manufacturer — same initiative, same investment, same commitment from leadership. The strategy stayed at the top. The floor never changed. And the gap between what leadership decided and what actually happened became the source of every problem that followed.