Leader Standard Work: Keep the Gains Alive Long After Handover

Leader Standard Work sits in the Sustain phase of RDMAICS. In the product's own words, it helps you define the standard recurring tasks for leaders at each level to embed sustainment discipline. You list who does what, how often, how long it takes, what it produces, and who checks it.

The reason you need it is simple. Control charts and work instructions describe the process. They do not describe the leaders. When a project closes and the improvement team moves on, the process keeps running on whatever attention it receives. Attention is a leadership behaviour, and behaviour decays unless it is scheduled.

Reach for this tool at handover, not after the slide back. The best time to write Leader Standard Work is while the project team is still in the room and still has the credibility to ask leaders for fifteen minutes a day. If you wait until month four, you are negotiating from a position of weakness.

Use it again whenever a leader changes role. The routine should belong to the position, not the person. A new supervisor should inherit a written daily routine on day one.

The tool opens with built-in sample data. Everything that follows is based on exactly that data set. It is a fictional example, included so you can see the shape of a complete entry before you write your own.

The sample describes a single value stream after a project handover. Three leader roles carry the sustainment load. The supervisor owns the floor. The manager owns the numbers and the audit. The director owns escalations that nobody below can close.

There are five standard tasks in total. Three run daily. Two run weekly. Each one has a named output and a named verifier. No task is left as a good intention.

The input table has six columns. Leader role, standard task, frequency, time, output and verification. Three of those are marked as required. The role, the task and the frequency. The other three are where the tool earns its keep, so treat them as required anyway.

Write the role as a position, not a name. The sample uses Supervisor, Manager and Director. That keeps the routine portable when people move. Write the task so a new starter could read it and know what to do. Gemba walk plus board review is concrete. Support the team is not.

Time matters because it makes the ask honest. Fifteen minutes is a commitment a supervisor can protect. An unbounded expectation is one a supervisor will quietly drop. Putting 10 min against the Tier 1 huddle tells everyone that the huddle is short by design.

The output column is the test of whether a task is real. Issues logged, action items, decisions, audit score, escalations closed. Each one leaves a trace you can look for later. If a task has no output, you cannot tell the difference between it happening and it not happening.

The verification column names who confirms the task occurred. In the sample, the supervisor is verified by the manager, the manager by the director and by a Black Belt, and the director by the sponsor. The chain runs all the way to the top, which is the point.

The tool summarises the table into a small set of figures. In the sample it reports 5 standard tasks across 3 leader roles. It reports that 5 of 5 tasks have a verification. It reports the most daily time as Manager, 30 min.

It then splits the load by frequency. Daily: Supervisor 25 min, Manager 30 min. Weekly: Manager 45 min, Director 45 min. That single line is the most useful thing on the screen. It tells you what you are actually asking of each leader in a normal day and a normal week.

The result view also lists each task again as a card grouped by role, so you can read the routine the way a leader would read it. The tool offers an AI review that explains what the result means for your situation.

Read the summary as a feasibility check. Twenty five minutes of daily routine for a supervisor is a number you can defend in a conversation. If the daily figure had come out at two hours, you would know the routine was written by someone who does not do the job.

The first decision is coverage. With 3 leader roles named, you can see whether sustainment responsibility actually reaches every layer between the floor and the sponsor. A gap in the middle is where improvements go to die, because the floor keeps logging issues and nobody above has a scheduled moment to act on them.

The second decision is the verification chain. All five sample tasks have a verifier. That means every routine has a second person whose own routine depends on the first one happening. The manager cannot complete a spot-check if the gemba walk did not occur. The absence becomes visible immediately rather than at the next audit.

The third decision is load balancing. The sample puts the heaviest daily load on the Manager at 30 min and the heaviest weekly load on the Manager and the Director at 45 min each. If one role carries everything, you have built a single point of failure. Leave on holiday and sustainment stops.

The fourth decision is what to cut. When a leader says the routine is too heavy, you now have a table in front of you instead of an argument. You can discuss which output you are willing to lose.

Decay is rarely announced. It shows up as small substitutions that feel reasonable at the time. Knowing the signs lets you intervene in week six rather than month six.

Watch the output column first. The sample names five outputs, and each one is a physical trace. When issues logged thins out, the gemba walk has become a stroll. When action items stop appearing from the Tier 1 huddle, the huddle has become a notice board. When escalations closed goes to zero, the Tier 3 review is no longer deciding anything.

Then watch the verification column. Verification is the load-bearing part of the design, and it is the first thing to be dropped because nobody misses it in the short term.

Finally watch the time. A 15 min walk that quietly becomes a 5 min walk is a signal, not a saving.

The most common mistake is writing tasks with no output. A routine without a trace cannot be verified, and a routine that cannot be verified will not survive a busy quarter. If you cannot name what the task leaves behind, the task is not ready.

The second mistake is self-verification. If the manager verifies their own KPI review, you have written a loop with no tension in it. The sample sends the manager's daily review to the director and the weekly audit to a Black Belt. Verification should point upward or sideways, never inward.

The third mistake is overloading the routine. Teams finishing a project often want every control on the plan to become a leader task. Keep the list short enough to be done on the worst day of the month. The sample holds the whole system to five tasks.

The fourth mistake is writing names instead of roles. Names expire. The fifth is treating the document as finished. Review it when the process changes, when a leader changes, and when an output stops appearing.

This tool records intent. It does not record compliance. The summary in the sample says 5 of 5 tasks have a verification, which means a verifier has been nominated for each task. It does not mean anyone verified anything. For that you need the audit scores, the huddle boards and the escalation log.

It will not tell you whether the tasks are the right ones. The tool counts tasks, roles and minutes. It cannot judge whether a daily gemba walk is the correct control for the failure mode your project addressed. That judgement comes from your control plan and your risk analysis.

It will not detect decay on its own. Nothing in the sample output changes when a supervisor stops walking the floor. The tool gives you the written standard to compare reality against. The comparison is still human work.

It also says nothing about outcome. There are no savings, no yields and no performance figures in this tool, and you should not infer any. Leader Standard Work tells you how attention is scheduled. Whether that attention protects the gain is something your measurement system has to answer.

Used honestly, that limit is a strength. A short, specific, verified routine written down at handover is one of the few things you can hand to a new leader on day one and expect them to follow.