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.

🎯
Zero losses is the direction: The target is always zero. Not better than last year. Not industry average. Zero. That does not mean zero is always achievable, it means zero is always the direction. Every loss we accept as normal is a loss we have stopped trying to eliminate.
🤝
100% engagement is the method: Improvement is not the job of a specialist team. It is the job of everyone. The system's role is to build the conditions where every person, from the line to the leadership team, can see a problem, name it, and act on it.
🎓
Capability building is how both are achieved. Zero losses and 100% engagement are not delivered by a programme. They are delivered by an organisation that has built the capability to sustain them. That means two things. First, the processes are defined, confirmed, and improved over time. Second, that the people who run those processes have the knowledge, skills, and habits to run them well. Neither is sufficient alone. The system is designed to build both, in sequence, across every pillar and every phase.

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.

👁️
Go to where the work is done. Decisions made away from the work are decisions made with incomplete information. The system requires leaders at every level to be present where the work happens, not to supervise, but to see, to learn, and to remove what is in the way.
📋
Confirm the standard, not the person. The question is never "did you do it?" The question is "is the system making it easy to do it right?" When the standard is not being followed, the first assumption is that something is making it hard, not that someone chose not to follow it.
⬆️
Escalate early, close out visibly. Problems that cannot be solved at the level where they are found must move up, the same day, with a named owner and a close-out date. The person who raised the problem should be able to see it move. That is what keeps people raising problems.

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.

🏛️
Pillars: Each pillar owns a defined category of losses and is accountable for driving them toward zero. It does this by building the capabilities, in processes and in people, needed to address that loss category and sustain results over time.
🎓
Capabilities: What each pillar is building. Every pillar is responsible for two types of capability. Process capabilities are the defined, confirmed ways of working that make the pillar's results repeatable, independent of any one person, any one shift, or any one programme. People capabilities are the knowledge, skills, and habits that allow the right people to run those processes effectively and improve them over time. Neither is sufficient alone. Each pillar page names the specific capabilities that pillar is responsible for building.
📆
Phases: Defines which capabilities are introduced to which audiences, and in what sequence. Each additional phase either adds new capabilities or expands the same ones to a wider audience. All pillars move forward together at a pace the organisation can hold.
📋
Phase Assessments: Before moving from one phase to the next, a phase assessment checks that all pillars are ready, not just one. It is a programme-level gate that ensures the system is spreading as intended and the next phase will land on solid ground.
⚙️
Processes: A defined set of tasks with a named owner, a named customer, and an output that customer cares about. A process that is not defined cannot be confirmed, and a process that cannot be confirmed cannot be maintained or improved.
🔍
Process Confirmations: Checks that a specific process is being run correctly, by the right people, producing the right output for its customer. It is not an inspection. It is a coaching tool, and what it finds feeds directly into the capability plan.

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.

1️⃣
Establish: Narrow scope, narrow audience. The minimum system. Direction is set, the cadence is running, and standards exist and are confirmed. A small group of leaders know what they are responsible for and have the capability to run the processes the system requires. Nothing is built on top of this until it is stable. This phase proves the system works and produces the concrete examples that make the case for expanding it.
2️⃣
Strengthen: The system deepens and widens. Capability extends to more people and more roles. Leaders begin coaching rather than just doing. New capabilities are introduced where the Establish phase is stable enough to hold them. The Pillars begin to connect, problem solving feeds process improvement, process improvement feeds reliability.
3️⃣
Sustain: The system runs, all core processes execute and deviations are found and fixed quickly. Behaviours are routine. Capability is assessed and refreshed. All pillars are active and each audits itself and feeds findings back into the plan. The organisation is no longer running a programme, it is just how we run.

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.