The System
Most organisations already have something. A continuous improvement programme. A management framework from a consulting engagement three years ago. Some of it is good. Most of it is not connected to your strategic objectives, and almost none of it is designed to last.
This System is not another programme. It is the link between the daily work and the strategic direction, and builds the capability to sustain that link permanently. It exists to help the organisation deliver its objectives, not to become one.
This page explains how the System is structured, why it is built the way it is, and what it is designed to build.
Why the System exists
Every improvement effort I have seen fail has failed the same way. Not because the tools were wrong. Not because the people were unwilling. Because the system around the improvement was never designed to hold it.
The improvement delivers a result. The programme ends. The result drifts back. Two years later the same opportunity is found again.
This System exists to break that cycle. It is built on two ideas that do not change regardless of the site, the function, or the phase of the journey.
Behaviours
The System is not just a set of processes and tools. It is built and maintained by a set of deliberate behaviours, things that all leaders and teams do consistently, every day, that make improvement possible and results sustainable.
Processes and tools without behaviours produce a burst of activity. Behaviours without tools produce good intentions. The System connects them.
Three behaviours sit underneath everything else.
Structural Elements
The System is fundamentally a capability-building framework. Each structural element below exists to build, confirm, or sustain a capability, in the processes the organisation runs, or in the people who run them.
The System has six structural elements. They apply to every site and every function. The losses look different in each setting. The structure is the same.
Phases
You cannot build everything at once. Trying to deploy every process, tool, and behaviour to everyone, at the same time, would produce the same result as every other programme. A burst of activity, followed by drift.
Phases define what capabilities get built, for whom, and in what sequence. The goal is to move all pillars forward together at a pace that builds capability evenly, so that the system holds rather than collapses under its own weight.
Each phase expands capability in two ways. The groups of people who hold the capability grow wider, from a small pilot group to a broader audience. And the processes in the system grow deeper, new capabilities are introduced as the prior phase is stable enough to hold them. Each phase adds to what came before, in the processes the system runs and the people who can run them. Both expansions happen together. Widening the audience without deepening the processes produces inconsistency. Deepening the processes without widening the audience produces a system that depends on a few people.
The phases below are a starting point. Assess what the right capabilities are, in the right order, for the right audience, to support your specific strategic objectives.
The system does not go live everywhere at once. It is introduced in sequence, because each phase builds the infrastructure the next one depends on.
Pillar Links
The pillars are where the system is put to work. Each one owns a defined area of the system and builds the capability to sustain results in that area. If you are not sure where to start, start with Leadership.
Leadership: Builds the management system that holds everything else in place.
Problem Solving: Builds the capability to find the real problem and fix it permanently.
Process Improvement: Builds the capability to define, map, and improve any work process.
Autonomous Maintenance: Builds the operator capability to maintain equipment conditions, detect problems early, and progressively take ownership of the equipment they run.
Maintenance: Builds the systems that prevent equipment failure rather than responding to it.
Organisational Capability: Builds the capability to design the organisation deliberately, ensuring the structure, skills, tasks, decisions, information, and rewards are aligned to what the strategy and the system require.
Quality: Builds the capability to define what good looks like, make defects visible before they leave the process, and eliminate the conditions that keep producing them.
Safety: Builds the capability to identify hazards before they cause harm, apply the most effective controls available, and investigate every near miss before it becomes an incident.
Planning: Builds the capability to produce a schedule built around what is actually needed, hold it against the pressure to optimise for something easier to measure, and act on gaps the same day.
Not sure where to start? Run the site assessment first.