Leadership
"We are what we repeatedly do. Excellence therefore is not an act, but a habit” - Aristotle
That is the argument for a management system. Not a project, or a programme. A habit.
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 initiative graveyard is not filled with bad ideas or lazy people. It is filled with improvements that landed in a management system that was never designed to hold them.
If you have not read the article on this, start there.
Pillar Intent
The Leadership pillar exists to build the capabilities that allow leaders to help their people find and fix problems themselves.
That is not a soft idea. It is a structural one. In a well-run operation, the people closest to the work are the ones who see the problems first. The leader's job is to make sure those people have the standard, the skill, and the support to act on what they see, and to remove the things that stop them.
This applies whether you run a manufacturing line or a planning function. The losses look different. The leadership system is the same.
Leadership is the first pillar in The System. Not because it outranks the others, but because nothing else works without it. It works in close partnership with the Organisational Capability pillar. Leadership builds the routines that hold the system together. Organisational Capability ensures the right people have the capability to run those routines, and that as the system grows, the capability grows with it. The two pillars are designed to work together from the start.
If you have not already read The System, start there.
Pillar Owned Losses
Leadership losses are rarely labelled. They do not appear on a loss tree when you perform a diagnostic assessment.
They appear in your organisation as:
These are management system problems. And management system problems have management system solutions.
Pillar Owned Capabilities
The Leadership pillar builds two types of capability in response to the losses it owns.
Process capabilities
Five processes. One system. Together they form the management system — the structure that holds every other pillar's work in place
- Developing Your Strategic Objectives: where direction is set.
- Deploying Your Strategic Objectives: where direction reaches every level.
- Tiered Accountability Meetings: the daily cadence that connects the floor to leadership.
- Leader Standard Work: the defined routines that make leadership consistent and visible.
- Process Confirmation: the structured check that the system is working as designed.
People capabilities
Leaders at every level who can run these routines effectively and use them to develop the people around them.
- People leaders and process owners who understand the overall System, from its intent to its application, and how it is the mechanism for delivering your Strategic Objectives.
- Frontline leaders who know how to conduct structured conversations to support Tiered Accountability Meetings effectively, to escalate problems the same day with a named owner, and go to the work to confirm the standard.
- Department leaders who know when to push decisions back to the tier below and when to step in, who remove barriers, connect daily performance to strategic direction, and coach rather than direct.
- Site and function leaders who set direction and hold it, model the behaviours they expect, and measure their success by what their team can do without them.
- Leaders at every level who have personally used the tools they ask their teams to use, Process Improvement, Problem Solving, Autonomous Maintenance, and who coach the method, not the answer.
Pillar Owned Processes
The Leadership pillar owns five processes. Each one is described briefly below. The detailed guides cover how to run each step in practice.
Developing Your Strategic Objectives — The process for defining a small number of clear, measurable objectives that reflect what the site or function most needs to achieve. This is where direction is set. Without it, every other process is pointing at a target nobody has agreed on.
Deploying Your Strategic Objectives — The process for cascading those objectives from site or function level to team level to individual level. Not a cascade of slides. A chain of conversations, boards, and measures that create a genuine line of sight from the floor to the strategy.
Tiered Accountability Meetings — The daily and weekly meeting cadence that connects the floor to site or function leadership. Problems are raised at the level closest to the work. What cannot be solved there moves up, the same day, with a named owner. The meeting system is not a reporting mechanism. It is the information and decision flow that makes everything else possible.
Leader Standard Work — The defined schedule of what a leader does, when they do it, and what they check. Without it, leadership time fills with the urgent and the reactive. The important work, confirming the standard, developing the team, removing barriers, gets displaced by whatever arrived loudest that morning.
Process Confirmation — The structured check that a specific process is being run correctly, by the right people, producing the right output for its customer. Not a compliance check. A coaching tool. The question is never "did you do it?" The question is "is the system making it easy to do it right?" What is found feeds directly into the capability plan.
Pillar Behaviours
Good leadership in this system is not about authority. It is about setting direction, building capability and providing support. The leader's job is to make it easier for their team to do the right thing, and harder to do the wrong thing. That is what servant leadership means here. Not a management style. A set of daily choices.
Here is what the same situation looks like with and without it.
A problem is raised at the line.
The weekly review happens.
A new standard is introduced.
A new tool or method is introduced across the site.
What Good Looks Like
Frontline leader
- Starts every shift with a structured conversation: did we achieve what we needed to last shift, what is the plan for this shift, what might get in the way, what do we need from the level above?
- Does not hold problems that need a different level of authority, escalates with a sense of urgency, with a named owner.
- Closes out actions as soon as possible. Not eventually. Before the next meeting if we can.
- Goes to where the work is done to confirm the standard, not to inspect, but to find what is making it hard to do it right.
- When a team member raises an idea, responds visibly. Even if the answer is no, the person knows why and knows they were heard.
- Participates in Process Improvement and Problem Solving work on their own area. Does not delegate the investigation to a specialist and wait for the answer. Is present, asks questions, and owns the outcome.
- In areas running Autonomous Maintenance, treats the team's equipment ownership as a leadership priority. Recognises the team when they find an abnormality. Ensures defects are closed, not just logged. Makes it visible that finding a problem is the right thing to do.
Department or area leader
- Removes the barriers that the frontline leader cannot. Same day where possible. Always with a named owner and a close-out date.
- Attends frontline meetings regularly, not to run them, but to see what is being raised and what is not being raised.
- Coaches frontline leaders on how they run the meeting, not just on the results it produces.
- Connects the team's daily numbers to the organisation's Strategic Objectives, regularly, at the board, in plain language.
- Has personally run at least one Process Improvement and one structured problem-solving investigation. Uses that experience to coach others through the method, not to provide the answer.
- Actively supports the operating team's ownership of their equipment. Removes the barriers, time, access, maintenance support, that prevent AM teams from completing their routines. Does not treat Autonomous Maintenance as something the maintenance function manages on behalf of the operators.
Site or function leader
- Sets the direction and holds it. Does not change the priorities every quarter and call it agility.
- Attends the site or function review. Asks the questions that only a leader at this level can ask. Acts on what is escalated, visibly, quickly, with a close-out date.
- Removes the barriers that the level below cannot. That is the job. Not the most important job. The only job that cannot be delegated.
- Models the behaviours they expect. If the leader does not run Leader Standard Work, no one else will. If the leader does not go to where the work is done, the message is that the work does not matter.
- Develops the next layer. The measure of a site or function leader is not what they fix. It is what their team can fix without them.
- Pilots the tools before asking others to use them. Runs a Process Improvement on a leadership process. Participates in a problem-solving investigation. Attends an AM step audit. The visible act of doing the work, not just sponsoring it, is what signals to the organisation that the system is real.
- Coaches the leaders below them on the method, not just the result. Asks in reviews: what did the investigation find, not just whether the number improved. What did the PI change, not just whether the changeover is faster. The question about the method is what builds the capability.
- Sets the expectation that equipment ownership belongs to the operating team. Asks AM teams what they have found this week, not what maintenance has fixed. One question builds ownership. The other confirms the old model.
Audits and Confirmations
The audit process for the Leadership pillar is not a compliance check. It is a learning check.
The question is not "did the leader run the meeting?" The question is "is the system making it easy to run the meeting well?" When something is not happening, the first assumption is that something is making it hard, not that someone chose not to do it.
Leadership audits cover four areas: direction (are Strategic Objectives clear and deployed?), cadence (are the right meetings running at the right frequency with the right information?), confirmation (are leaders going to where the work is done?), and escalation (are problems moving up and closing out visibly?).
Findings from the audit feed directly into the capability plan. The audit is not the end of the process. It is the input to the next phase.
Where to Start
Before choosing where to start, it helps to understand where you are. These questions are not a formal audit. They are a quick read of the system as it stands today. Answer honestly. The gaps are where the work begins.
If most people cannot, direction has not been deployed. Start with your Strategic Objectives.
If not, start with Tiered Accountability Meetings. The escalation system is what keeps people raising problems. Without it, disengagement follows.
If not, start with Leader Standard Work. Consistency is what makes leadership visible. Without it, the system depends on whoever happens to be present.
If not, that is the starting point. A leader who has never written a problem statement or run a PI cannot coach one. The first PI on a leadership process is not a symbolic gesture. It is the foundation.
Phases
The leadership pillar must be activated first. Without it the capability framework of the other Pillars does not hold. The capability building plan for this Pillar is linked to the depth and width of the capabilities needed across the rest of your management system.
Each phase expands the Leadership pillar's capability in two ways.
The groups of people who hold the capability grow. Phase 1, Establish, builds it with a small leadership cohort. Phase 2, Strengthen, extends it to the leaders who own processes directly. Phase 3, Sustain, reaches everyone.
The processes in the system grow, Establish sets the minimum, direction, cadence, and confirmation; Strengthen deepens them; Sustain makes them self-correcting and improving. 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.

Ready to build your pillar?
Before you start, make sure your team is in place, your charter is drafted, and your plan connects to the site's strategic objectives. The Setting Up Your Pillar guide takes you through each step in sequence.