Operations and Continuous Improvement
Making gains permanent
Once a change is live, the question shifts from "did we improve?" to "will it stay improved and keep improving?". Sustaining requires standard work (the current best documented method), daily management (short team huddles reviewing the few measures that matter), a visual control that makes abnormal conditions obvious, and a named owner with authority to act. Improvement without a standard has nothing to hold it in place; a standard without review becomes a ritual.
Concepts to name
- BAU versus project - operations is steady-state with recurring demand; projects are temporary and unique. Improvements must land in BAU budgets and roles.
- Control charts - distinguish common-cause variation (the system, adjust the system) from special-cause variation (an event, investigate the point). Reacting to common-cause noise is tampering and increases variation.
- SLAs and KPIs - service commitments versus internal performance measures; dashboards should show a few leading and lagging indicators, not everything measurable.
- Lessons learned and maturity review - capture what worked, update the standard, reassess maturity, and re-enter the improvement cycle.
Traps
Setting a numeric target on a stable process and expecting the number to change the process; rewarding a single metric until it is gamed (Goodhart's law); and answering "sustainability" with "more training" when the real gap is an owner, a standard or a measure.
Rule of thumb
Before closing any improvement, answer "who checks this, how often, and what do they do if it is off-standard?" If any part is blank, the gain is not yet sustained - write it into the standard and the daily management routine.