Leader Standard Work Guide

A practical guide to building, running, and sustaining your Leader Standard Work plan. Covers what it is, why it matters, and how to build one that holds.

The leader who does not have a standard cannot confirm that anyone else is following one.

Leader Standard Work (LSW) is the documented schedule of what a leader does, when they do it, and what they check. It is not a to-do list. It is not a calendar. It is the standard for how a leader spends their time, the same discipline applied to leadership work that standard work applies to any other process.

Without it, leadership time fills with the urgent and the reactive. The important work, confirming the standard is being followed, developing the team, removing barriers, gets displaced by whatever arrived loudest that morning.

This guide explains what LSW is, why it matters, and how to build one that works. Work through it in sequence. The plan you produce at the end should look different from how you are spending your time today. If it does not, you have not looked hard enough.

Back to the Leadership pillar →

What Leader Standard Work is

LSW is a documented, time-structured plan that defines what a leader does each day, each week, and each month to support the management system.

It has three components:

1️⃣

The critical schedule: The time-blocked plan for the week. It shows the key activities the leader does, when, and for how long. It is built around the fixed points in the management system, shift handovers, tiered accountability meetings, floor walks, coaching conversations, and the leader's own critical tasks.

2️⃣

The process confirmation list: The specific processes the leader checks, how they check them, and how often. This is not a general walkthrough. It is a defined set of checks, what to look for, what good looks like, and what to do when it is not right.

3️⃣

The self regulating PDCA cycle: The review of the LSW itself. Did the leader do what they planned? If not, why not? What changes for next week? LSW is not written once and followed forever. It is a living standard, improved by the person who runs it.

⚠️

LSW is not the same as your calendar. Your calendar holds everything. Your LSW holds only the work that is critical to the management system, the things that, if missed, allow problems to go unseen and standards to drift. Keep them separate.

Why it matters

Most leaders in operations spend the majority of their time reacting. A problem on the line. An urgent request from above. A meeting that was not in the plan. By the end of the week, the work that was supposed to happen, the floor walk, the coaching conversation, the process check, did not happen. Again.

This is not a discipline problem. It is a system problem. Without a standard for how leadership time is spent, the urgent always wins over the important.

LSW addresses four specific losses:

⚠️

Improvements that do not hold. Every improvement eventually drifts without a leadership system to sustain it. The changeover time creeps back. The 5S area deteriorates. The standard that was followed during the programme is quietly abandoned when the programme ends. LSW is the mechanism that catches drift before it becomes a problem.

⚠️

Slow starts for new leaders. A new leader who walks into a role without a defined standard for how to spend their time takes months to find their footing. LSW shortens that curve. The critical tasks are documented. The new leader knows what to do on day one.

⚠️

Cover gaps when leaders are absent. When a leader is absent, the work that only they know about does not happen. LSW makes the critical tasks visible and transferable. A deputy or cover can pick up the plan and know what needs to happen that day.

⚠️

Time spent on the wrong things. Without a plan, leaders default to what feels productive, email, meetings, reports. LSW forces the question: is this the most important use of my time right now? It shifts focus from activity to impact.

Shadow of the leader

There is a second reason LSW matters that is harder to quantify but equally important.

If a leader expects their team to follow a standard, the leader must follow one too. LSW is the visible proof of that. When a leader runs their LSW consistently, when the team can see that the leader's time is structured, planned, and reviewed, it changes the culture of the area. Standards are not just for operators. They are for everyone.

💡

The goal of LSW is not to solve problems. It is to understand the situation, help others develop their thinking, and remove the obstacles that stop them from solving problems themselves. A leader who uses LSW to micromanage has missed the point.

How to build your LSW

Work through the following steps in order. Each step has a clear output. Do not move to the next step until you have it.

Step 1 — Identify your critical processes

Start with the key processes you own or are accountable for. Not everything you touch, the ones where, if the process is not running correctly, there is a real consequence for the line, the area, or the site.

For each process, ask:

What does good look like in this process?
How would I know if it was not running correctly?
How often do I need to check it to catch a problem before it becomes a loss?

Process	What to confirm	How to confirm	How often	Location

Rank your processes by criticality. The highest-rated processes should appear most frequently in your LSW schedule.

Rating	What it means
1 — Critical	Major disruption if this process fails. Must be confirmed regularly.
2 — High	Significant impact if this process drifts. Confirm at least weekly.
3 — Medium	Some disruption. Confirm fortnightly or monthly.
4 — Low	Local effect only. Confirm monthly or as needed.

Step 2 — Identify your critical tasks

Separate from your process confirmations, list the recurring tasks that your role requires, meetings you lead, reports you own, coaching conversations, reviews, and handovers.

Apply the same criticality rating. Not every task deserves equal time. Some tasks are critical to the management system. Others are habitual but low-value. LSW is an opportunity to be honest about the difference.

⚠️

Do not list everything you currently do. List what you should be doing. If a task is on your list and you cannot explain why it matters to the management system or the team's performance, question whether it belongs there.

Capture at this step:

Task	Frequency	Criticality	Time required

Step 3 — Align to the site calendar

Before you build your personal LSW, confirm the fixed points in the management system that your plan must align to. These are the non-negotiables, the tiered accountability meetings, shift handovers, and daily direction-setting sessions that the whole site runs around.

If your site has a fixed site calendar, use it. If it does not, this is the moment to build one.

The fixed points to protect:

Shift handovers — the structured transfer of information between shifts
Tier 1 meetings — frontline team, daily, at the line or board
Tier 2 meetings — department or area, daily or every other day
Tier 3 meetings — site or function, daily or weekly
Tier 4 meetings — site leadership, weekly
Coaching meetings — agree fixed times in the week for coaching to ensure maximum flexibility at other times

Your LSW must be built around these fixed points, not in competition with them. If your LSW conflicts with the management system, the management system loses, and so does the team.

ℹ️

The site calendar is the skeleton. Your personal LSW is the muscle. Build the skeleton first.

Step 4 — Build your personal LSW schedule

Now build your weekly or monthly plan. Time-block your schedule using the fixed points from Step 3 and the critical processes and tasks from Steps 1 and 2.

Structure your day around three types of activity:

1️⃣

Planned confirmations — the process checks and floor walks that are in your LSW because you decided they are critical. These are protected. They happen unless there is a genuine emergency.

2️⃣

Planned meetings — the tiered accountability meetings, handovers, and structured conversations that are part of the management system. Also protected.

3️⃣

Improvement and follow-up time — time set aside to close out actions, coach the team, and work on the things that are important but not urgent. This time is the first to disappear if you do not protect it explicitly.

Minimum content for a complete LSW:

Element	Included?
All tiered accountability meetings	Yes / No
Shift handovers (where applicable)	Yes / No
Process confirmation checks (from Step 1)	Yes / No
Coaching or 1:1 time	Yes / No
Improvement and follow-up time	Yes / No
Weekly LSW review (PDCA)	Yes / No

Step 5 — Add your process confirmation detail

For each process confirmation in your schedule, define exactly what you will check and how you will know whether it is right. Ideally this can be done visually, at a glance.

A process confirmation is not a walkthrough. It is a structured check with a defined standard. You should be able to complete it in a fixed time and know immediately whether the process is running correctly.

For each confirmation, define:

What process are you checking?
What does good look like? (the standard)
What are you physically looking at, reading, or asking?
What do you do if it is not right?

ℹ️

The check is not the point. The response is the point. A process confirmation that finds a problem and does nothing is worse than no confirmation at all, it tells the team that the standard does not matter.

Step 6 — Run your LSW and track adherence

Your LSW is only useful if you run it. Track whether you did what you planned, not to report upward, but to understand your own patterns.

Mark each item as complete or not complete at the end of each day. If you missed something, note why. At the end of the week, review the pattern.

Common reasons for missing LSW items:

A reactive event displaced planned time — is this a one-off or a pattern?
The item was planned at the wrong time — does it need to move?
The item is no longer critical — should it be removed?
The item is critical but consistently missed — what barrier needs to be removed?

⚠️

Do not treat LSW as written in stone. It is a standard, and standards are improved. If your LSW is consistently not achievable, the problem is the plan, not the person. Revise it.

Step 7 — Run the weekly PDCA

At the end of each week, spend fifteen minutes reviewing your LSW. This is the PDCA cycle for your own standard work.

Plan — Update your LSW for the coming week based on what you learned this week.
Do — Run the updated LSW.
Check — At the end of the week, reflect: did you do what you planned? Did you find what you expected in your process confirmations? What surprised you?
Act — Update the LSW based on what you learned. Standardise what worked. Change what did not.

Field	Your answer
Week number
Items completed as planned	Number or percentage
Items missed	Which ones, and why
Process confirmations — what did you find?	Any gaps between the standard and what you observed
Actions raised this week	What was escalated, to whom, and by when
Changes to LSW for next week	What is being added, removed, or moved

Common pitfalls

These are the patterns that cause LSW to fail. Most of them are not about effort. They are about misunderstanding what LSW is for.

⚠️

Treating LSW as a calendar. LSW is not everything you do. It is the critical subset of what you do. If your LSW looks like your full calendar, it will be impossible to follow and impossible to improve.

⚠️

Letting the latest emergency take priority, every time. One emergency displacing a planned item is a one-off. The same emergency displacing the same item every week is a pattern. The pattern is the problem to solve, not the emergency.

⚠️

Using LSW to micromanage. LSW is a tool for confirming that processes are working, not for checking up on people. If your process confirmations feel like inspections, you are using the tool incorrectly. The question is always: is the process working? Not: is this person doing what I told them?

⚠️

Not having a PDCA cycle on the LSW itself. LSW that is never reviewed is a procedure, not a standard. The weekly reflection is not optional. It is the mechanism that makes LSW improve over time.

⚠️

Skipping LSW when things get busy. The moments when LSW feels hardest to run are the moments it is most needed. A site under pressure is a site where standards are most likely to drift. That is exactly when process confirmations matter most. If you miss LSW for a good reason, you will eventually miss it for a bad reason.

What this gives you

✅

A standard for your own work. A documented, time-structured plan that makes your critical tasks visible, transferable, and improvable. A new leader, a deputy, or a cover can pick it up and know what needs to happen.

✅

A management system that holds. LSW is the mechanism that connects the tiered accountability meetings, the process confirmations, the coaching conversations, and the improvement work into a single coherent system. Without it, each of those things happens occasionally. With it, they happen consistently.

Key Links

This guide depends on:

The tiered accountability meetings are the fixed points your LSW is built around. If those meetings are not yet in place, start there before building your LSW.

Tiered Accountability Meeting guide →

This guide connects to:

Process Confirmation is the discipline your LSW schedule is designed to make happen consistently. Your confirmation list is the core of your LSW.

Process Confirmation guide →

The processes you confirm need a defined standard before you can confirm them. Process improvement is how those standards are set and maintained.

Process Improvement Process guide →

Back to the Leadership pillar →