Why improvement programs stall after the pilot

A pilot succeeds with attention. The best supervisor, a cooperative shift, a consultant in the room, and daily review. None of those conditions survive the rollout, so the result does not either. The organization concludes the improvement did not work, when what actually did not work was the transfer.

What the pilot quietly borrowed

• Attention: someone senior watching the measure every day
• Slack: the pilot area was given room the rest of the operation does not have
• Selection: the most capable team and the least chaotic conditions
• Interpretation: someone present who could resolve an ambiguity in the new process on the spot

Each of those is a real input. If the rollout plan does not replace them with something durable, the rollout is not a rollout — it is the same experiment run without the equipment.

Design the second site, not the first

The discipline that changes outcomes is designing for the second site while running the first. Write the standard work so it resolves the ambiguities the pilot resolved verbally. Name the owner and the control measure before the pilot closes. Decide what the operation stops doing to make room for the new process, because capacity is not created by enthusiasm.

Sustainment is a design property

Control plans, named ownership, and an operating cadence are not closing activities bolted on at the end. Designed into the improvement, they make adoption a consequence of the process rather than a campaign fighting the process. That is the difference between an improvement and a result — and it is why the measure gets re-run after the change has been live long enough to be real, rather than on the last day of the engagement.

If a gain cannot survive the removal of the people who created it, it was never a gain. It was supervision.