Leader standard work is the routine that sustains a lean process — and the one most plants can't sustain. What it is, what it looks like by level, and why it fails.
Leader standard work is the part of a lean program everyone
agrees with and almost nobody sustains. The checklist gets built, runs for six
weeks, then quietly becomes a clipboard nobody picks up.
This article covers what leader standard work is, what it looks like at
different levels of a plant, and — more usefully — the specific ways it dies.
Leader standard work (LSW) is the set of recurring activities a leader
performs on a fixed cadence — daily, weekly, monthly — to make sure the process
runs as designed and keeps improving.
If standard work defines how the operator does the job, LSW defines how the
leader does theirs — same principle, one level up.
It is sometimes called “kaizen for management,” and the description fits.
The intent is not to give managers a to-do list — it is to shift the manager
from being the plant’s primary problem-solver to building problem-solving
capability in the people who do the work.
That distinction matters more than any template. A leader who uses LSW to
check up on people has built a surveillance routine. A leader who uses it to
find out where the process is failing them has built an improvement engine.
The checklist looks identical either way.
These get conflated constantly, which causes real confusion when a plant
rolls out both at once.
| Dimension | Standard work | Leader standard work |
|---|---|---|
| Who it is for | The person performing the process | The person accountable for the process |
| Defines | The best known way to do a task | The recurring routine that sustains and improves it |
| Cadence | Every cycle | Daily, weekly, monthly — by leader level |
| Measured by | Adherence and takt | Whether the routine happened, and what changed as a result |
| Fails as | A document nobody follows | A checklist nobody completes honestly |
| Owned by | The team doing the work | The leader — it cannot be delegated |
The most common mistake is giving every leader the same LSW. A team leader
and a plant manager should not run the same routine — cadence and altitude both
change as you go up.
| Level | Typical cadence | Focus of the routine |
|---|---|---|
| Team leader | Mostly hourly and daily; a large share of the shift | Confirming the process is running to standard; responding to abnormalities as they surface; first-line problem containment |
| Supervisor | Daily, with weekly elements | Tiered meetings, process confirmation, coaching team leaders, escalating what cannot be solved at the line |
| Value stream / area manager | Weekly, with some daily | Gemba walks, reviewing improvement work, removing the barriers supervisors escalate |
| Plant manager | Weekly and monthly | Reviewing the system rather than the numbers; confirming the tiers below are actually functioning; strategy deployment |
The pattern: the further up you go, the less time goes on the process itself
and the more on whether the layer below has what it needs.
This is the section most articles leave out — and the reason most LSW
programs are on their second or third attempt.
LSW is launched with a kickoff, a template, and a deadline. But the value is
not in the checklist — it is in the loop of building it, running it, finding it
wrong, and changing it. A program has an end date. A process does not.
The single most common failure. The manager gets pulled into a breakdown,
misses the checks, and completes the whole sheet at 4pm from memory. Now you
have a document that says the process is healthy and a process nobody looked
at. This is worse than having no LSW, because it manufactures false confidence.
If a supervisor is firefighting for nine hours a day, adding a routine does
not create discipline — it creates a new thing to fail at. LSW usually has to
replace reactive work, not sit on top of it. Something has to be taken
away first, and that is a leadership decision, not a lean one.
Four tiers, every level, plant-wide, from week one. It collapses under its
own weight. One leader, one level, one real problem is slower on paper and far
faster in practice.
This is the one that quietly kills more LSW than all the others combined. If
a supervisor’s LSW is audited by a manager who has no LSW of their own, the
message is unmistakable: this is something done to the front line, not
something the organization believes in. LSW has to start at the top or it reads
as compliance theatre.
If the routine is used to catch people out, people optimize for looking good
during the walk. You get clean audits and no information.
The Lean Enterprise Institute’s
lexicon entry on leader standard work
is a good vendor-neutral reference on where the practice sits in the wider lean
management system.
Leader standard work is a behavior, not a document, which makes it hard to
learn from a template download. Most supervisors were promoted for being
excellent at the technical job — not for coaching, process confirmation, or
holding a routine when the plant is on fire.
SCMEP delivers Leader Standard Work as part of a leadership and workforce
curriculum built for manufacturers. As a
NIST Manufacturing Extension Partnership affiliate working with South Carolina manufacturers since 1989,
we teach it in the context of the shop floor rather than the classroom. You can
browse the manufacturing leadership and workforce training catalog,
see
structured learning paths that build lean capability end to end,
or email the training team.
To watch LSW working in other plants, join
OpExChange, our peer network for operational excellence in South Carolina
— plant tours and benchmarking discussions with manufacturers across the state.
Related reading:
the difference between maintenance planning and scheduling,
and how A3 problem solving turns a root cause into a verified fix.
Leader Standard Work formalizes what a supervisor checks and when; a related program from the 1940s formalized how to teach a job correctly in the first place. See our related guide on TWI (Training Within Industry) for the four-step Job Instruction method many standard work training programs are built around.
Leader Standard Work is frequently confused with a related but distinct lean tool. See our related guide on Standard Work for the operator-facing document defining takt time, work sequence, and standard WIP.
It is the set of recurring activities a leader does on a fixed cadence — daily, weekly or monthly — to confirm the process is running as designed and to keep improving it. Where standard work defines how an operator does the job, leader standard work defines how the leader does theirs.
Standard work is for the person performing a task and defines the best known way to do it. Leader standard work is for the person accountable for the process and defines the routine that sustains and improves it. Standard work repeats every cycle; leader standard work runs daily, weekly or monthly depending on the leader’s level.
It depends entirely on level. A team leader’s routine is mostly hourly and daily process confirmation. A plant manager’s is weekly and monthly, and focuses on whether the tiers below are functioning. Copying another plant’s template is the most common way to end up with a routine that surfaces nothing.
The most common causes are pencil-whipping (completing the checklist from memory), adding it on top of already-overloaded supervisors instead of replacing reactive work, rolling out every tier at once, and — the big one — leaders above not doing their own. If the manager auditing the routine has no routine, it reads as compliance theatre.
Expect it to feel bureaucratic before it feels useful. The turn comes when the routine starts surfacing real problems that get fixed — which is also the point most plants abandon it. Pruning the routine monthly shortens that gap.
