Leadership Standard Work

Leadership standard work is a structured set of tasks — daily, weekly, and monthly — that define how a leader spends their time. Not what they should do if they have time. What they must do regardless of what fires are burning.

Without LSW, leaders are reactive. They spend their days responding to the loudest problem, the most urgent email, the most insistent request. The result: strategic initiatives die of neglect, MDI boards go unverified, hoshin projects stall because nobody is following up, and the gemba operates on autopilot.

What LSW is not

• Not a to-do list. A to-do list is things I need to get done. LSW is a management operating rhythm. The tasks repeat. The discipline is in the repetition.
• Not delegation. LSW tasks are things the leader does personally. “Verify 5S condition in Area 3” means walk to Area 3 and look. Not ask someone to report on it.
• Not optional during busy weeks. The weeks when you are most tempted to skip LSW are the weeks it matters most. If the plant is in crisis, that is precisely when you need to verify that the management system is functioning.
• Not surveillance. LSW is verification, not policing. The purpose is to confirm that systems are working, not to catch people doing things wrong. The questions are “is the system functioning?” and “what barriers exist?” — not “who screwed up?”

The core principle

A leader’s most important job is not solving problems. It is ensuring that the system solves problems. LSW is the mechanism for verifying that the system — MDI, visual management, hoshin, standard work — is functioning. If the system is functioning, problems get surfaced and resolved through normal channels. If the system is broken, the leader needs to fix the system, not the symptoms.

The content and time allocation of LSW varies by role. Higher in the organization, less time is spent on daily standard work and more on strategic verification. But every level has standard work. No one is “too senior” for structured tasks.

Why percentages matter

If a team lead spends only 30% of their time on standard work, they are firefighting 70% of the day. That means the management system is broken — problems are not being surfaced and resolved systematically, so the team lead is personally compensating. The fix is not to work harder. The fix is to repair the MDI system so problems flow through normal channels.

Conversely, if a plant manager spends 80% of their time on standard work, they are not spending enough time on strategic thinking and organizational development. The percentages are diagnostic — they tell you where the system is healthy and where it is failing.

LSW is structured as a calendar, not a list. Each task has a cadence (daily, weekly, monthly), a specific time slot, and a specific location or scope. The calendar makes it visible whether the tasks are getting done.

Reading the calendar

Thursday’s pre-shift board review shows a miss (red ×). Why? Was the leader pulled into a crisis? Was the meeting cancelled? The calendar does not judge — it records. Over time, a pattern emerges. If gemba walks are missed every Wednesday, something systemic is happening on Wednesdays (perhaps a standing meeting conflicts). The calendar makes these patterns visible.

The goal is not 100% completion every week. The goal is high-enough completion that the management system functions, and honest recording so that gaps are visible and addressable.

A gemba walk is not a tour. It is structured observation at the point of work, with a specific route, specific things to observe, and a specific follow-up process. Without structure, gemba walks become “walking around.” Walking around does not improve anything.

A structured gemba route

What to look for

• Visual management boards: Are they current (updated in the last 24 hours)? Are red conditions addressed with action items? Does the team reference the board or ignore it?
• Standard work adherence: Is the operator following the standard work procedure? Is the procedure posted and current? If there is a deviation, is it a training gap, a tooling issue, or a better method the standard has not captured?
• 5S condition: Is the work area organized? Are tools where they belong? Is there unnecessary material or WIP accumulating? The 5S condition tells you whether shaping is being maintained.
• Safety: Any new hazards? Guard rails in place? PPE being used? Safety concerns raised by operators?
• Conversations: Talk to operators. “What is your biggest frustration right now?” “Is there anything you need that you are not getting?” “Do you know what the hoshin objectives are this year?” The answers tell you more than any board.

After the walk

A gemba walk that does not produce action is a walking meeting. Every walk should result in one of three outcomes:

1. Confirmation: The system is working as intended. No action needed. This is a valid outcome — not every walk finds problems.
2. Action item: Something needs attention. Put it on the newspaper with an owner and date. Follow up at the next day’s tier meeting.
3. System issue: The problem is not a one-off — it is a gap in the management system itself. This goes to the relevant tier for structural resolution.

LSW is the third pillar of MDI. Visual management makes performance visible. Daily accountability drives action. LSW ensures that leaders are present in the system, verifying and supporting rather than operating above it.

LSW as MDI verification

The most important function of LSW is verifying that the MDI system is working:

• Are Tier 1 meetings happening? Not just scheduled — happening. With data. With actions assigned. On time, every day. If the team lead is skipping meetings, LSW catches it.
• Are newspapers being honored? Are items completed by their due dates? Are barriers being escalated? Are resources being provided? The newspaper only works if both sides deliver.
• Are visual boards current? Stale data on a board means nobody is maintaining the system. This is the earliest signal of MDI decay.
• Are escalations being resolved? Items escalated from Tier 1 to Tier 2 should have a response within 24 hours. LSW tracks whether this is happening.

The leader as system operator

In a functioning MDI system, the leader’s job is not to manage people — it is to manage the system that manages performance. LSW is how the leader operates that system: daily checks, weekly audits, monthly reviews. If the system is working, the leader verifies. If the system is broken, the leader fixes the system — not the individual problem.

Without LSW, hoshin kanri floats above the operation. Strategic objectives exist on the X-matrix. Annual targets are set. Projects are assigned. But nobody verifies whether strategic intent is reaching the gemba. LSW is that verification mechanism.

Hoshin verification tasks in LSW

• Weekly: Review hoshin project status. Are active projects on schedule? Are action items progressing? Any blocked items that need escalation? This is a 15-minute review, not a meeting.
• Weekly: Walk to Tier 1 boards for areas with active hoshin projects. Do the operators know about the project? Are the project’s KPIs visible on the board? Is the project producing visible improvement?
• Monthly: Review hoshin savings actuals. Are projects delivering the dollars they committed to? What is the variance? For projects behind target, what is the recovery plan?
• Monthly: Check X-matrix correlations. Are there orphan projects (no connection to objectives)? Are there unsupported objectives (no projects driving them)? Have any correlations changed?
• Quarterly: Review annual objective status. On-track, at-risk, or behind? Does the trajectory suggest year-end targets will be met? Any course corrections needed?

The gap LSW closes

Most hoshin implementations fail not because the strategy is wrong but because the verification is absent. The plant manager sets ambitious objectives in January, reviews them in July, and discovers that half the projects stalled in March. Seven months of drift. LSW prevents this by building weekly and monthly hoshin checks into the management routine. The drift gets caught in weeks, not months.

LSW provides an objective measure of management execution. Not opinions about whether leaders are “engaged.” Data: did the task happen or not?

LSW completion rate

The simplest metric: what percentage of scheduled LSW tasks were completed this week? This number tells you more about the health of the management system than any engagement survey.

What the numbers mean

• Above 85%: Healthy. The leader is executing the management routine with consistency. Misses are occasional and explainable.
• 70-85%: Slipping. Some tasks are being systematically skipped. Investigate which tasks and why. Is the leader overloaded? Is the task unrealistic? Is the leader deprioritizing verification for firefighting?
• Below 70%: Broken. The management routine is not functioning. The leader is either overwhelmed, disengaged, or unsupported. This requires a structural conversation, not a lecture.

Trending, not judging

A single week at 64% means nothing. A trend from 87% to 78% to 64% over three weeks means the system is decaying. Trend the data. Look for patterns: which tasks get dropped first? Are gemba walks the first casualty? Are hoshin checks being skipped? The pattern tells you where the management system is weakest.

Leader’s leader verification

The plant manager’s LSW includes verifying that area managers are executing their LSW. The area manager’s LSW includes verifying that team leads are executing theirs. Each level verifies the level below. This is not micromanagement — it is system verification. If the team lead’s LSW completion drops to 50%, the area manager needs to understand why and either adjust the workload, provide support, or address the root cause.

LSW as paperwork

When LSW completion is tracked but the tasks are done superficially — checking the box without actually verifying anything. The leader walks to the board, checks it off, and walks away without looking at the data. 100% completion, zero value. The fix: pair completion tracking with outcome questions. Did the gemba walk produce any actions? What did you learn? If the answer is always “nothing,” either the system is perfect (unlikely) or the walk is not genuine.

Firefighting displaces LSW

The most common failure. A machine goes down, a customer complaint arrives, a supplier misses a delivery. The leader drops LSW to fight the fire. This is sometimes necessary. But if it happens more than once per week, the firefighting is systemic and the management system needs repair. Frequent firefighting means problems are not being surfaced and resolved through normal MDI channels.

LSW designed by someone who does not do the job

If a consultant designs the LSW calendar without consulting the people who will execute it, the tasks will not match reality. LSW must be designed by the person who will do it, reviewed by their leader, and adjusted based on experience. A team lead who has never been asked “what should your standard work look like?” will not own the result.

No verification of the verifier

If no one verifies the plant manager’s LSW, the plant manager’s discipline depends entirely on personal commitment. In mature organizations, the operations VP or regional manager reviews plant manager LSW completion and hoshin results. This is not optional — accountability at every level is what makes the system work.