On this page
Short answer
Operational improvement plans usually fail during installation, not analysis. The design is sound, but nobody owns the new process after go-live, the ERP (enterprise resource planning) or WMS (warehouse management system) configuration it needs was never scoped, the standard work was never written, and measurement still tracks the old process. Plans hold when the layout, system configuration, standard work, measures and a named owner are designed together and installed on the floor.
Most operational improvement work does not fail at the analysis stage. The constraint gets identified, the future state gets designed, and the business case holds up. It fails somewhere between the approved recommendation and the shift that has to run it.
The recommendation is not the change
A recommendation describes a destination. Installation is the work of moving an operation there while it keeps producing. Those are different disciplines, and organizations routinely resource the first and assume the second.
The result is a design that is correct on paper and unworkable on the floor — because the system cannot be configured that way, because the standard work was never written, or because nobody owns the new process once the project team leaves.
Where installation actually breaks
Across manufacturing and distribution operations, the same failure points recur:
- Handoffs between the project team and the operating team are undefined, so the change has no owner after go-live.
- System constraints surface late — the ERP (enterprise resource planning) or WMS (warehouse management system) cannot support the designed workflow without configuration nobody scoped.
- Standard work is never written, so the new method survives only as long as the people who were trained on it.
- Measurement stays pointed at the old process, so nobody can tell whether the change is holding.
- The first failure under real demand is treated as proof the design was wrong, rather than as normal installation work.
Designing for installation from the start
Treating installation as part of the design changes what gets produced. The deliverable stops being a recommendation and becomes an operating condition: the layout, the system configuration, the standard work, the measures and the named owner, all developed together.
Work the constraint, not the symptoms
Throughput problems in particular reward this approach, because adding labor to a constrained process rarely moves output. We covered that specific pattern in why throughput problems are rarely solved by adding labor.
The work is not complete when the new process starts. It is complete when the operation can run it without us.
What to ask before approving a plan
- Who owns this process on the Monday after go-live?
- What system configuration does this design assume, and who has confirmed it is possible?
- What does the standard work look like, and who is trained on it?
- How will we know in week four whether the gain is holding?
If those questions do not have names and dates attached, the plan is a recommendation rather than a change. You can see how we structure that work in how we work.