Leader standard work is the routine that keeps daily management alive: which huddles a leader attends, which boards they check, when they walk the gemba. In most organizations it contains nothing about the strategy. A few additions change that.
In this guide
Key Takeaways
- →Leader standard work is the documented routine that sustains the lean system at each level.
- →Most versions of it contain nothing about the strategy, so the strategy has no daily presence.
- →Add, don’t replace: a team leader notes blockers, an executive coaches one A3.
- →Every added item has to be checkable by a peer, or it quietly lapses.
- →About an hour a week for a site manager, all inside moments that already existed.
- →The items only stay light if the records they need sit in one place.
What leader standard work is
Leader standard work, described in depth in David Mann’s Creating a Lean Culture, defines what leaders at each level do routinely to sustain the lean system: attend huddles, check visual controls, follow up on actions, walk the gemba. The share of a leader’s time it covers falls as you move up the organization, leaving senior leaders more room for discretionary work.
That taper is the whole design. A team leader’s day is mostly standard work because the system needs someone present at the point where problems appear. An executive’s day is mostly not, because the system needs someone able to act on what the lower tiers surface. Both ends break the same way: when the routine stops being written down, it stops being done, and nobody notices for a quarter.
Strategy items by level
The addition is small and specific at every level. Nothing in the table below replaces an existing item; each one attaches to a moment the leader was already going to be in.
Read the right-hand column as a chain. The team leader supplies raw observations, the area manager turns repeated observations into a pattern, the site manager answers the pattern with effort, and the executive checks whether the effort moved anything. Break any link and the two above it are running on guesswork.
| Level | Usual items | Strategy items to add |
|---|---|---|
| Team leader | Run tier 1 huddle; check standard work | Note problems affecting the strategic KPI on the board |
| Area or department manager | Attend tier 1 and 2; follow up actions | Flag patterns that affect a strategic bet |
| Site or unit manager | Tier 3 huddle; gemba walk; KPI review | Weekly review of improvement effort on strategic KPIs; respond to escalations within a week |
| Executive | Tier 4 review; site visits | Monthly review of flagged patterns; coach one strategic A3 |
If leaders’ routines never touch the strategy, the strategy has no daily presence.
Keeping it light
- Add, don’t replace. A few minutes a week at each level.
- Make it checkable. Each item is something a peer can see was done.
- Tie it to existing moments: the huddle, the walk, the weekly review.
- Revisit quarterly as the focus KPIs change.
The second rule is the one that decides whether this survives. “Reviews improvement effort weekly” is checkable if there is a record showing which improvements were logged against which strategic KPI and when the manager last opened it. It is not checkable if the answer lives in the manager’s own notes. Items that cannot be seen from outside are the first to go in a busy month, and their disappearance is silent.
A worked example: a site manager’s week
Here is one hypothetical site manager’s week, with each routine tied to the strategy item it serves:
| Day | Routine | Strategy item |
|---|---|---|
| Daily | Tier 3 huddle, 15 minutes | Check on-time delivery trend; note flagged problems |
| Tuesday | Gemba walk, two lines | Ask each line what blocks parts availability |
| Wednesday | — | Respond to the week’s strategic escalations |
| Thursday | Weekly KPI review | Review improvement effort on delivery and scrap |
| Friday | A3 coaching, 30 minutes | Coach the supplier reliability A3 |
About an hour a week of the manager’s routine now touches the strategy, all of it inside moments that already existed.
Wednesday is the item most often cut, and it is the one that matters most to the tiers below. A front-line team that flags a strategic problem and hears nothing back for three weeks learns that flagging is unpaid work. Rebuilding that habit afterwards takes far longer than answering would have.
What a disconnected routine costs
The cost of leaving leader standard work disconnected from the strategy is not a missed meeting. It is a year in which the daily management system runs at full strength on local problems while the strategic KPIs are improved by whoever happens to be interested. The improvement capacity is spent either way; only the direction differs. For an organization with a few hundred people in daily management, a year of undirected improvement capacity is the single largest discretionary cost on the table, and it never appears as a line item.
Among published alternatives for connecting the two, OnStrategy lists $200 per month for unlimited users. i-nexus publishes a free Starter tier for up to five users and $28 per user per month at its Standard tier. Either way, test the same thing in a trial: open a site manager’s week and count how many clicks it takes to see this week’s strategic escalations, the improvement effort logged against each strategic KPI, and the open A3s. If that is three screens and a spreadsheet export, the routine will not hold.
Profit.co publishes two plans, Essentials and Enterprise, quoting against modules and scale rather than a public seat rate, which fits an organization adding leaders tier by tier rather than buying every seat up front. Hoshin Kanri, OKRs and Goals and Balanced Scorecard sit in Essentials, and the 30-day free trial covers four full weeks of a leader’s routine, which is long enough to see whether the added items actually take minutes.
Minutes, not a hunt through systems
In Profit.co, the strategic KPIs, escalations, improvement effort by KPI and A3s are in one place, so the strategy items in leader standard work take minutes rather than a hunt through systems. See the lean strategy software page.
Three things follow from having them on one set of records rather than four:
- The weekly review is a filter, not a reconciliation. Improvement effort is already tagged to the strategic KPI it was meant to move, so the manager reads a list instead of building one.
- Escalations have a clock. A flag raised at a tier 1 huddle carries the date it was raised and the owner it reached, so a one-week response time is reportable rather than aspirational.
- A peer check takes a minute. Because each item leaves a record, checking another manager’s leader standard work is reading a screen, not shadowing them for a day.
The patterns those routines surface are worth more when someone is deliberately looking for them on the floor: Gemba Walks That Feed the Strategy. And when the items start quietly dropping out, the cause is usually the one described in Why Lean Strategy Deployment Stalls in Year Two.
Free Product Demo
Add strategy to your leaders’ routines
A 30-minute walkthrough, tailored to your team.
Book a free demoWhat happens in the call
How your teams set goals, track progress and review results.
Strategy, performance, projects and engagement on one platform, with AI.
A practical path to align teams, execute faster and drive results.
Questions this article answers
The documented routine of leaders at each level, such as attending huddles, checking boards and walking the gemba, that sustains a lean management system.
By adding a few items at each level: checking strategic KPIs, flagging patterns, responding to escalations, reviewing improvement effort on strategic KPIs and coaching strategic A3s.
Typically minutes a day for front-line leaders and about an hour a week for site managers, inside routines that already exist.
Make every item checkable by a peer and check them monthly. An item that leaves no record behind is the first one to disappear in a busy month, and it disappears silently.
Yes. Revisit the strategy items quarterly as the focus KPIs rotate, so leaders are checking the measures the plan currently depends on rather than last year’s.