The Pillars

A pillar is a defined area of responsibility within the management system. It owns specific categories of losses. And it builds the capability, in the processes and the people, to drive those losses toward zero and keep them there.

That is the distinction between a pillar and a programme. A programme delivers a result. A pillar builds the capability to deliver that result permanently.


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 pillar. The management-system logic will look the same.

  • Define the losses the pillar is responsible for addressing.
  • Build the process capabilities, the defined, confirmed ways of working, that address those losses.
  • Build the people capabilities, the knowledge, skills, and habits, that allow the right people to run those processes effectively.
  • 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.

The pillars are not separate programmes. They are the parts of the same system, introduced in a sequence that reflects what each one depends on. Leadership comes first because nothing else holds without it.


How to read the Pillar guides

Every pillar page follows the same structure. Start with the intent, then move through the losses, capabilities, behaviours, audits and confirmations, phases, and where to start.

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.

Capabilities

What does this pillar build? The Capabilities section names the two types of capability the pillar is responsible for developing, in response to the losses it owns.

  • Process capabilities are the defined, confirmed ways of working the pillar establishes, the processes, standards, and routines that make the pillar's results repeatable.
  • People capabilities are the knowledge, skills, and habits the right people need to run those processes effectively.

Behaviours

What does the system look like in practice? The Behaviours section shows the same situation with and without the pillar in place. Not a list of principles. A before-and-after picture of what changes when the system is working.

What Good Looks Like

What does this pillar require of leaders at each level? This section describes the specific actions and habits expected of frontline leaders, department leaders, and site or function leaders when the pillar is embedded and working. It is the practical expression of the behaviours section — what you would actually see if you walked the floor.

Pillar Owned Processes

What are the specific processes this pillar runs? This section describes each process the pillar is responsible for, what it does, and why it matters. It links to the detailed guides where the step-by-step method is covered.

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.

Phases

How does capability grow over time? The Phases section describes how the pillar's capabilities are built in sequence. 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 processes are added as the foundation from the previous phase is stable enough to build on. Phases do not just sequence activity. They sequence capability growth.

Where to Start

Where does this pillar fit in the current situation? The Where to Start section provides diagnostic questions that help identify the right entry point, whether the organisation is new to the pillar or already has some capability in place.


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 capabilities are introduced to which audiences, and in what sequence. A later phase may add new capabilities or extend existing capabilities to a wider audience.

Phases should be designed to build the right capabilities to meet the organisation's strategic objectives as quickly as possible, while ensuring those capabilities can be sustained.

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.

⚠️
All Pillars must pass a phase 1, Establish, assessment before moving into phase 2, Strengthen. Similarly all Pillars must pass the Phase 2 assessment before moving together into Phase 3, Sustain.

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


Active Pillars

Leadership: Builds the management system that holds everything else in place.

Process Improvement: Builds the capability to define, map, and improve any work process.

Problem Solving: Builds the capability to understand the real problem and fix it permanently.

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 capability to move from reactive to planned to predictive maintenance, and to sustain equipment reliability as a system.

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 that holds, review it every day, and act on what it finds before the next shift starts.


Not sure where to start?

Every pillar needs a team, a plan, and a clear connection to the site's strategic objectives before it can build capability in sequence. This guide takes you through the steps, from forming your team and drafting a charter, to building your three-year master plan and breaking it down into a annual master plan and a 90 day action plan.