Skip to content

Author: ScmepOn

  • What Is Leader Standard Work? A Manufacturer’s Guide

    What Is Leader Standard Work? A Manufacturer’s Guide

    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.

    What is leader standard work?

    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.

    Leader standard work vs standard work

    These get conflated constantly, which causes real confusion when a plant rolls out both at once.

    How leader standard work differs from operator standard work
    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

    What leader standard work looks like by level

    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.

    Typical leader standard work by leadership level
    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.

    Why leader standard work fails

    This is the section most articles leave out — and the reason most LSW programs are on their second or third attempt.

    1. It gets treated as a program, not a process

    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.

    2. Pencil-whipping

    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.

    3. Piling it onto already-overloaded supervisors

    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.

    4. Going too big, too fast

    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.

    5. Nobody above them is doing it

    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.

    6. It becomes surveillance

    If the routine is used to catch people out, people optimize for looking good during the walk. You get clean audits and no information.

    How to start without it dying

    1. Start at the top. If the plant manager will not do their own LSW, do not roll it out below them.
    2. Take something away. Identify what the routine replaces. If nothing, expect it to fail.
    3. Make it short enough to be honest. A three-item routine done truthfully beats a twenty-item routine pencil-whipped.
    4. Review the routine itself monthly. Items that never surface anything should be removed. If nothing ever changes, it is not working.

    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.

    Where training fits

    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 [email protected].

    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.

    Frequently asked questions

    What is leader standard work in simple terms?

    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.

    What is the difference between standard work and leader standard work?

    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.

    What should be on a leader standard work checklist?

    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.

    Why does leader standard work fail so often?

    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.

    How long before leader standard work shows results?

    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.

  • Maintenance Planning vs Scheduling: What’s the Difference?

    Maintenance Planning vs Scheduling: What’s the Difference?

    Most plants do not have a maintenance planning problem. They have a planning-and-scheduling problem that has been quietly collapsed into one job, handed to one overloaded person, and then blamed for missed schedules.

    Planning and scheduling are two different functions. They need different skills, run on different time horizons, and answer different questions. When one person does both — which is common — the urgent work of scheduling always eats the important work of planning.

    This article explains the difference, what each role actually does, and how to decide whether you need one person or two.

    Maintenance planning vs scheduling: the short answer

    The distinction is easiest to hold onto as two questions:

    • Planning answers what and how. What is the scope of this job, what parts and tools does it need, how many labor hours, what safety steps?
    • Scheduling answers when and who. Which day does this work happen, which technician does it, and does the production line have to be down for it?

    Planning is a technical function. Scheduling is a logistics function. And the order is not negotiable — you cannot schedule work that has not been planned, because you have no idea how long it will take or whether the parts are on site.

    Maintenance planning vs maintenance scheduling at a glance
    Dimension Maintenance planning Maintenance scheduling
    Core question What needs doing, and how? When does it happen, and who does it?
    Function type Technical Logistics and coordination
    Main output A complete work pack — scope, parts, tools, hours, safety steps A committed weekly schedule matched to available labor
    Time horizon Ahead of the work — often weeks out The coming week, refined daily
    Key relationships Stores, procurement, engineering Production, supervisors, technicians
    Fails when Work packs are incomplete, so techs go hunting for parts Schedule is built on guesses, so it breaks by Tuesday
    Sequence Always first Always second

    What a maintenance planner actually does

    The planner’s job is to make sure that when a technician picks up a work order, everything needed to finish it is already sorted. That is the whole point of the role.

    In practice, that means:

    1. Scoping the job. What is the actual failure or task, and what does “done” look like?
    2. Identifying parts and materials. What is needed, is it in stores, and if not, how long will it take to arrive?
    3. Estimating labor. How many people, how many hours, what trades?
    4. Specifying tools and equipment. Including anything that has to be booked, like a crane or a contractor.
    5. Building the safety and permit requirements into the pack before the job is released.
    6. Improving the job plan after the work is done, using feedback from the people who did it.

    That last step is the one plants skip, and it is the one that compounds. A job plan that gets a little better every time it runs is the difference between a planning function and a filing function.

    What a maintenance scheduler actually does

    The scheduler takes planned, ready-to-go work and turns it into a commitment that production has agreed to.

    • Matching planned work to available labor hours for the coming week
    • Negotiating equipment access windows with production
    • Sequencing jobs so that related work happens in the same outage
    • Protecting the schedule from low-priority interruptions
    • Reporting schedule compliance — what was committed vs what got done

    Scheduling is fundamentally a negotiation with production. That is why it needs different skills from planning. A brilliant technical planner who cannot hold a firm line with a production manager will produce a schedule that evaporates every week.

    Do you need one person or two?

    This is the real question behind most searches on this topic, and most articles dodge it. Here is a straight answer.

    Combined planner-scheduler vs separated roles
    Consideration One combined role Two separate roles
    Best suited to Smaller sites; roughly under ~15 technicians Larger sites, or multi-line plants with tight uptime demands
    Main advantage One point of contact; no handoff to get wrong Each function gets protected time and the right skill set
    Main risk Scheduling is urgent and planning is important — urgent wins, and planning quietly stops happening Requires a genuine handoff discipline, or work packs get scheduled before they are ready
    Typical failure The “planner” becomes a parts-chaser and expeditor Planner and scheduler stop talking; schedule fills with unready work
    Skills needed Technical depth and negotiation — rare in one person Technical depth (planner); coordination and influence (scheduler)

    If you take one thing from this table: the most common failure mode of the combined role is that the planner becomes an expeditor. They spend the day chasing parts for work that is already in progress, which is reactive work by definition — the exact thing planning exists to prevent.

    If that describes your planner’s week, you do not have a planning function. You have a very expensive parts runner, and no amount of software will fix it.

    Why this is worth getting right

    Maintenance planning and scheduling is widely regarded as one of the highest- return improvements available in a maintenance organization, precisely because it costs little and touches everything: wrench time, downtime, parts spend, and the credibility of the maintenance department with production.

    The mechanism is simple. Every hour a technician spends looking for a part, waiting for a permit, or finding out the job is bigger than the work order said, is an hour of capacity you already paid for and did not get. Planning converts those hours back into work.

    For a deeper technical treatment of the discipline, ReliablePlant’s overview of maintenance planning and scheduling is a solid, vendor-neutral starting point.

    Where training fits

    Planning and scheduling are learnable skills, and they are rarely learned by accident. Most planners are promoted from the tools because they were good technicians — which is a completely different skill from building a work pack or defending a weekly schedule.

    SCMEP has delivered maintenance planning and scheduling training to South Carolina manufacturers as part of a broader maintenance and reliability curriculum that also covers reliability centered maintenance and predictive maintenance strategies. As a NIST Manufacturing Extension Partnership affiliate serving South Carolina manufacturers since 1989, our focus is the plant, not the software.

    If you are working out whether your site needs a planner, a scheduler, or both, or you want to build the capability in people you already have, you can browse the manufacturing maintenance and reliability training catalog or email [email protected].

    Planning is also a natural companion to leadership discipline on the floor — see our related article on how leader standard work keeps daily management from going reactive.

    Frequently asked questions

    Is maintenance planning the same as scheduling?

    No. Planning defines what a job needs — scope, parts, tools, labor hours and safety steps. Scheduling decides when the job happens and who does it. Planning always comes first, because you cannot schedule work reliably without knowing how long it takes or whether the parts are on site.

    Should the same person do both planning and scheduling?

    At smaller sites, often yes — roughly under 15 technicians, one person can carry both. The risk is that scheduling is urgent while planning is merely important, so planning gets squeezed out and the planner drifts into chasing parts. Larger or higher-uptime plants generally get better results by separating the roles.

    What does a maintenance planner do day to day?

    Scopes upcoming jobs, identifies the parts and tools each one needs, estimates labor hours, builds in safety and permit requirements, and improves job plans using feedback from the technicians who did the work. A planner should be working ahead of the work, not inside it.

    Do I need a CMMS before I can plan maintenance?

    No. A CMMS helps you scale and measure a planning process, but it does not create one. Software applied to an undefined process produces faster disorder. Define the planning and scheduling functions first, then choose a tool to support them.

    How do I measure whether planning is working?

    Two starting measures: schedule compliance (what you committed to versus what actually got done) and wrench time (the share of a technician’s day spent doing the work rather than looking for parts, waiting for permits, or travelling). Both should improve as planning matures.