The Pillars

The System page explains how the management system works. This page explains what each part of it owns and how it is put to work.

A pillar is a defined area of responsibility within the management system. It owns a specific category of losses and builds the capability needed to drive those losses toward zero.

The pages that follow are not departments, teams, or specialist functions. They are practical guides to the processes, tools, behaviours, and confirmations that make each area of the system work.

WHAT IS A PILLAR

A pillar is not a team or a department. It is a defined area of responsibility that can apply across a manufacturing site, a function, or both.

The losses will look different in each setting. The management-system logic is the same:

• Define the losses the pillar is responsible for addressing.
• Select the processes, tools, and behaviours that will address them.
• Build capability with the right audiences.
• Confirm that the processes are being run correctly and producing the right outputs.
• Use what is learned to improve the system and move toward zero losses.

A pillar does not deploy everything at once. It builds the capability the organisation needs, in the sequence it can sustain.

HOW TO READ THE PILLAR GUIDES

Every pillar page follows the same structure. Start with the intent, then move through the losses, behaviours, processes, tools, and confirmations.

Intent

Why does this pillar exist? The Intent section describes the result the pillar is responsible for creating and the principle that guides the work.

Losses

What does this pillar own? The Losses section describes the observable losses the pillar is accountable for addressing. These are not abstract categories. They are the wasted effort, rework, delays, bottlenecks, recurring problems, and other failures that people can see in the work.

Behaviours

What does good look like? The Behaviours section describes the daily choices and actions that make the pillar effective. It shows how leaders and teams behave when the system is working, and what happens when those behaviours are missing.

Processes

How is the work done? The Processes section describes the defined ways of working that identifies or address the pillar's losses. Each process has a clear purpose, owner, customer, sequence, and output.

Tools

What supports the processes? The Tools section identifies the practical instruments used by the right people to run the processes and build capability. A tool is not included because it is available. It is included because a process requires it.

Audits and Confirmations

How do we know the system is working? This section explains how the pillar confirms that its processes are being run correctly, producing the right outputs, and developing the required capability.

Process confirmations are ongoing and used to coach and develop people. Phase assessments are broader programme-level gates that check whether all pillars are ready to move to the next phase.

HOW PILLARS MOVE TOGETHER

The pillars are connected. They do not operate as separate improvement programmes, each moving at its own speed.

Phases define which processes, tools, and behaviours are introduced to which audiences, and in what sequence. A later phase may add new capabilities or extend existing capabilities to a wider audience.

The goal is not for one pillar to race ahead. The goal is for all pillars to build capability together at a pace the organisation can hold. Before moving to the next phase, a phase assessment checks that the system as a whole is ready to build on what has been established.

That is what turns a collection of pillar activities into one management system.