Leadership

"We are what we repeatedly do. Excellence therefor is not an act, but a habit” - Aristotle

Every organisation I have worked in has a version of this.

Lean arrives. It is about flow, waste, and the people closest to the work. Within eighteen months it is a cost reduction programme with a Lean label on it. Six Sigma arrives. Operational excellence. Continuous improvement. Same journey. Different name on the slide.

The methodology is not the problem. The methodology is usually sound. The problem is that it lands in a system that was never designed to hold it. The improvement delivers a number. The consultants leave. The posters fade. Two years later someone does an assessment and finds the same opportunity. The consultants are called. The room nods. The programme is approved. It was always going to be approved.

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.

The Leadership pillar is built to be that system. Not a project. Not a training programme. A management system, a connected set of processes, tools, and behaviours that builds capability over time and drives losses toward zero. The difference between an improvement that sticks and one that fades is almost never the quality of the idea. It is whether the management system was designed to hold it.

What this pillar is responsible for

The Leadership pillar exists for one reason, to build leaders who help their people 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 losses are rarely labelled as such. They do not appear on a loss tree as "leadership failures." They appear as:

⚠️
Wasted effort. Work done twice because the standard was unclear the first time. Meetings that produce no decision. Reports that nobody reads because they do not connect to anything that matters.
⚠️
Rework. Output that did not meet the customer's expectation because the process was not confirmed, the deviation was not caught, or the standard was not followed consistently enough to prevent it.
⚠️
Bottlenecks. Decisions held at the wrong tier. Actions waiting for a leader who is not available, not informed, or not empowered to act. Problems that could have been solved at the line, escalated to a level that cannot act on them quickly.
⚠️
Disengagement. People who stopped raising ideas because nothing happened when they did. Teams that wait to be told rather than act on what they see.
⚠️
Improvement that does not hold. The changeover time that crept back. The 5S area that drifted. The standard that was followed while the programme was running and abandoned when it ended.

These are not people problems. They are management system problems. And management system problems have management system solutions.

What leaders need to be able to do

A leader in this system needs to be able to do five things:

1️⃣
Set direction clearly. Translate the organisation's Strategic Objectives into goals that a team can act on. Not a slide. A conversation, a board, and a shared understanding of what matters and why, so that every person in the team can answer the question "are we winning or losing?" without looking anything up.
2️⃣
Run a reliable cadence. Show up consistently. Run the right meeting at the right level with the right information. Know what to look for and what to do when it is not there.
3️⃣
Confirm the standard. Go to where the work is done. Verify that the process is running as designed, not to catch people out, but to find the barriers that stop people from doing it right.
4️⃣
Remove barriers. When a team member cannot fix something themselves, the leader acts. Quickly. Visibly. That is the job.
5️⃣
Develop the next layer. The measure of a leader is not what they fix. It is what their team can fix without them.

What good looks like

Good leadership in this management system is not about authority. 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.

It is worth being honest about what poor leadership looks like first, because it is more recognisable than most people admit:

  • A problem is raised at the line on Monday. By Friday it might be on a list, but without an owner or a date.
  • The weekly review tells the room what happened last week. Nobody asks whether it was good enough.
  • A decision that could have been made at the team level waits three days for a leader who is unavailable.
  • The standard exists. Nobody has checked whether it is being followed. The deviation has been running for weeks.
  • An operator stopped raising ideas six months ago. Nobody noticed.

These are not character flaws. They are management system failures.

At the frontline leader level:

  • Starts every shift with a structured conversation: what is the plan, what might get in the way, what do we need from the level above?
  • When a problem occurs, asks first: can the team solve this, or does it need to go up? Does not hold problems that need a different level of authority.
  • Closes out actions before the next meeting. Not eventually. Before the next meeting.
  • Goes to where the work is done and confirms the standard is being followed, 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.

At the department or area leader level:

  • 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. Not once a year at the strategy offsite. Regularly, at the board, in plain language.

At the site or function leader level:

  • Sets the direction and holds it. Does not change the priorities every quarter and call it agility.
  • Attends the site or function meeting. 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.

Leadership Business Processes

Each process below is a defined way of working. Together, they form the management system for leadership across every site and function.

Developing Your Strategic Objectives

The process for defining measurable objectives that reflect what the site or function most needs to achieve. This is where direction is set. Done well, every person in the team can explain what they are trying to achieve and why their work connects to it.

Go to the guide →

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 cascade of conversations, boards, and measures that create a genuine line of sight from the floor to the strategy.

Go to the guide →

Leader Standard Work

The daily and weekly routines that make leadership consistent. Not a checklist. A discipline. Leader Standard Work defines what a leader does, when, and why, so that the management system runs whether or not the leader is having a good day.

Go to the workshop → · Download the template →

Tiered Accountability Meetings

The structured meeting cadence that connects the floor to the site or function leadership. Each tier has a defined purpose, a defined frequency, and a defined escalation path. Information moves up when it needs to. Decisions move down when they should.

Go to the guide →

Audit Process

The process for verifying that the management system is working as designed. Not a compliance audit. A learning audit. The question is not "did you do it?" The question is "is the system making it easy to do it right?" Findings feed back into the capability plan.

Go to the guide →