Leader standard work (LSW) is a defined set of recurring tasks and checks a leader does on a fixed cadence to keep the management system running. It answers a simple question: what should a supervisor reliably do every single day, regardless of what is on fire? Typical LSW covers gemba checks, a look at the day's key metrics, verifying standard work is being followed, and following up on open improvement actions.
Without it, a leader's day is whatever the day throws at them, and the slow, unglamorous work that actually sustains a system, checking the standard, walking the floor, closing out yesterday's actions, is the first thing dropped when a machine goes down. LSW protects that work by making it routine. This guide covers what goes on an LSW sheet, how it differs by level, and how it keeps a lean system from decaying. For the operator-level foundation it builds on, see standard work.
What is leader standard work?
Leader standard work is the leadership equivalent of an operator's standard work: a documented, repeatable routine that defines the recurring actions expected of a leader and provides a way to confirm they were done. The concept was popularized by David Mann in Creating a Lean Culture where he frames it as one of four elements of a lean management system, alongside visual controls, daily accountability, and leadership discipline. In Mann's model, LSW is the engine: it drives the other elements by making the checks that feed them happen on schedule.
The key word is recurring. LSW is not a to-do list of one-off projects; it is the set of things that must happen again and again for the system to stay healthy, the daily verification that the standard is being followed, the review of the hour-by-hour board, the follow-up on yesterday's problems. These are precisely the tasks that feel skippable in the moment and prove costly when skipped for a month.
What goes on a leader standard work sheet?
An LSW sheet lists the leader's recurring tasks by cadence, start of shift, hourly, end of shift, weekly, with a place to mark each one done. It is deliberately simple: a task, a frequency, and a check box. The value is not in the paperwork but in the fact that the routine is written down, visible, and verifiable, so that a skipped check is obvious rather than invisible.
Here is a representative daily LSW sheet for a production supervisor. Yours will differ by plant, but the shape holds: a mix of floor presence, metric review, standard verification, and follow-up.
| Cadence | Recurring task | Why it is on the sheet |
|---|---|---|
| Shift start | Review prior shift handover and overnight issues | Start informed, not surprised |
| Shift start | Confirm staffing and the production plan for the day | Catch gaps before they stop the line |
| Hourly | Walk the floor; check the hour-by-hour board | See the real state; make problems visible fast |
| Hourly | Verify one station is following current standard work | Catch process drift early |
| Midday | Follow up on yesterday's open improvement actions | Close the loop so actions do not die |
| Shift end | Update the board; review the day's metrics vs. target | Feed daily accountability with facts |
| Shift end | Complete handover to the next shift | Pass the baton cleanly |
How does LSW differ by level?
The share of the day that is standardized decreases as you go up the organization, because higher levels must leave more room to handle exceptions. Mann's rough guidance is that a large majority of a team leader's day can be defined by standard work, a good portion of a supervisor's, and a smaller portion of a manager's, with senior leaders standardizing a modest fraction. The higher you sit, the more of your day is judgment and the less is routine, but the routine never drops to zero.
The content shifts with level, too. A team leader's LSW is dense with floor checks and real-time response. A supervisor's mixes floor checks with metric review and action follow-up. A plant manager's LSW might be a weekly gemba walk, a monthly layered process audit and a standing review of the site's key measures. What stays constant across levels is the principle: some part of every leader's time is reserved, in writing, for sustaining the system rather than fighting the day's fire.
Where do gemba walks fit in leader standard work?
The gemba walk is the heart of most leader standard work, the recurring act of going to where the work happens and seeing the real state with your own eyes. Mann is blunt that little matters more in a lean culture than getting leaders onto the floor on a schedule, and LSW is the mechanism that makes it happen. A gemba walk that depends on a leader remembering to do it will not survive a busy week; the same walk written into LSW as a fixed hourly or daily item does.
The distinction that keeps a gemba walk useful is purpose. An LSW gemba check is not a stroll and not a spot inspection to catch people out. It is a structured look at specific things, is the board current, is the standard being followed at this station, are yesterday's actions closed, driven by the same short checklist logic as an audit. The leader is verifying the system is running and surfacing problems for the team to solve, not solving every problem personally. Done on cadence, the walk feeds the daily accountability process with facts instead of opinions, which is exactly what turns a huddle from a status meeting into a problem-solving session.
How do you build leader standard work that sticks?
Building LSW that survives contact with a real plant is a matter of sequence and restraint. The most common failure is a bloated sheet nobody can actually complete, which teaches everyone that the sheet is theater. Build it lean and grow it slowly.
- Start with the sustaining tasks, not everything. List the handful of recurring actions that, if skipped for a month, would let the system decay, gemba presence, standard verification, metric review, action follow-up. Begin there.
- Assign a cadence to each. Mark whether it is per shift, hourly, daily, or weekly. Cadence is what turns a good intention into a routine.
- Put it on a simple sheet with a completion check. A task, a frequency, a check box. The completion mark is what makes a skipped check visible.
- Keep it short enough to finish. If the sheet cannot realistically be completed on a normal day, it is too long. Cut it until it fits, then hold the line.
- Tie it to visual controls. Point the checks at the boards and metrics that already exist so LSW feeds visual management instead of duplicating it.
- Audit the LSW itself. Higher levels should verify that lower levels are completing their LSW, the same layering logic that makes a layered process audit work. LSW that no one checks decays as fast as anything else.
- Adjust as the system matures. Retire checks that have become habit; add checks where new problems recur. The sheet is a living document, not a monument.
Leader standard work: by the numbers
The concept has a clear source and a documented structure:
- Leader standard work was popularized by David Mann in Creating a Lean Culture a Shingo Award-winning book that frames LSW as one of four elements of a lean management system: leader standard work, visual controls, daily accountability, and discipline.
- Mann's model holds that the standardized share of the workday falls with rank, largest for team leaders, smaller for supervisors, smaller still for managers, while the remainder is reserved for handling exceptions.
- The Lean Enterprise Institute treats standardized work as a foundation of the Toyota Production System; LSW extends that same discipline of a documented, repeatable method from the operator to the leader (LEI, standardized work).
Why does leader standard work matter for sustaining lean?
Leader standard work matters because lean tools do not sustain themselves, someone has to check them, feed them, and follow up, and LSW is what guarantees that someone does. A lean program that installs boards, standards, and huddles but leaves the sustaining routine to chance will watch all three fade the first time the plant gets busy. The tools become wallpaper; the standards drift; the huddles get skipped. LSW is the countermeasure to that decay, and it is why kaizen gains hold in some plants and evaporate in others.
The practical weak point is verification. LSW depends on a leader actually being able to check the real state of the process quickly, the current metric, whether the standard is being followed, whether yesterday's action closed. When that information lives on paper and lags a day, the checks become guesswork and the leader spends the reserved time hunting for data instead of acting on it. When production data is captured digitally and visible live, LSW becomes fast and honest: the leader walks the floor with the real numbers in hand, the check takes a minute, and the reserved time goes to fixing problems. That live loop is what Harmony builds for plants, and the shift CLS made off paper logs. Reserve the time, keep the sheet short, verify it at every level, and the system you built keeps running when your attention is elsewhere.