Implementation Guide
Lean Daily Management System.
A lean daily management system is the routine a plant uses to see deviations and answer them the same day. David Mann's classic model names four elements: visual controls, a daily accountability process, leader standard work and leadership discipline. On the floor that means boards updated every shift, tier meetings that give every red an owner, escalation with a response deadline, and leaders who check it daily. Below: the rhythm, a 90-day build plan and a free audit checklist.
What a lean daily management system is
A plant produces deviations all day: a machine slows, a defect slips through, an absence breaks the crewing plan, a supplier truck is late. None of these is unusual. What separates plants is how long a deviation lives before someone with the authority to fix it sees it. Without a daily system the answer is days: the miss surfaces in a weekly report, gets discussed in a monthly meeting, and by then the trail is cold. Lean daily management, also called shop floor management or a daily management system, cuts that answer to hours.
It is not one tool. The classic definition comes from David Mann's book Creating a Lean Culture, which names four elements. Visual controls show the deviation against a target. A daily accountability process, the tiered meetings and their follow-up, decides within minutes who acts and carries what a team cannot solve up to the level that can, the same day, with a promised response time. Leader standard work puts the checks into every leader's calendar. Leadership discipline keeps those routines alive when they are inconvenient.
This guide adds a fifth piece: structured problem solving, the exit for repeat deviations. Without it the same reds come back every week. Remove any one piece and the others degrade into ritual: boards without meetings become wallpaper, meetings without escalation become complaint sessions, escalation without response kills honesty.
This is the umbrella page: it explains how the parts fit and how to build the loop. Each part has its own deep guide. The table below shows, per element, what it looks like on the floor and when you actually have it rather than a poster of it.
The daily management loop
One deviation followed around the loop, from a red on the board at shift handover to a verified fix the next morning.
| Element | On the floor | You have it when |
|---|---|---|
| Visual controls Make today's deviations visible within hours, not in the monthly report Mann element SQDIP boards , SQDIP board template | An SQDIP board at every line or cell, updated by hand each shift, and an hour-by-hour chart at the constraint. Red and green against a target the team can read from three meters away. | An operator at the board can say in one sentence whether the line is winning or losing today, and every red has an action with a name and a date beside it. |
| Daily accountability process Decide who acts on each deviation, in minutes, at the right level Mann element Tier meetings | Tier 1, 2 and 3 meetings at fixed times, standing at the board. An action list with names and dates, and written escalation rules with a response promise. | Tiers 1, 2 and 3 run at fixed times every day, standing, in 15 minutes or less, and an issue raised at 06:45 can reach the plant manager by 08:00. |
| Leader standard work Put the checks into every leader's calendar Mann element Leader standard work | A short written routine for every leader: which boards to check, which questions to ask, which closed actions to verify at the machine. It covers about 70 percent of a supervisor's day and about 30 percent of the plant manager's. | Leaders' daily checks are scheduled, survive vacations, and a skipped round is visible to that leader's own manager. |
| Leadership discipline Keep the routines alive when they are inconvenient Mann element Gemba walk , Layered audits | Leaders ask for the board before the report, run their rounds in the busy weeks too, and follow up a stale board or a skipped meeting the same day. | Three supervisors asked separately name the same top priority for the plant, and a stale board gets a question from someone senior within a day. |
| Structured problem solving Kill repeat deviations at the root instead of working around them again Added in this guide 5 whys , RCCA | A red that comes back gets a 5 whys or an RCCA with the team that owns the metric, and the countermeasure is checked before the problem is closed. | A deviation that appears twice triggers a root-cause method with a verified countermeasure, not a bigger workaround. |
Where it sits in the transformation roadmap
On the TeamGuru deployment roadmap, daily management is the Daily Management practice and the heart of the Run Daily band. It starts once strategy deployment has named the few priorities the boards should reflect, runs in parallel with standard work and 5S, which give deviations a standard to deviate from, and it is the platform that leader standard work and structured problem solving are built on.
- Before Strategy Deployment
- You are here Daily Management
- In parallel Standard Work & 5S
- After Leader Standard Work
- After Structured Problem Solving
The rhythm: what runs every shift, day, week and month
A daily management system is a calendar before it is anything else. The morning tier cascade is its best-known part, but the cascade only works because of what sits before it, the shift handover that makes the board current, and after it, the weekly and monthly reviews that check whether the loop holds. The times below suit a plant whose day shift starts at 06:00; shift them to yours and keep the order.
| What runs, and when | Who | How long | What it produces |
|---|---|---|---|
| Shift handover at the board; the team posts the shift's numbers Every shift | Outgoing and incoming team leaders | 5 to 10 min | The next shift starts informed, and the board is current before anyone meets |
| Tier 1 at the line board Daily, first hour | Team leader with the crew | 10 min | An owner and a date for every red; what the team cannot solve is marked for escalation |
| Tier 2 for the area Daily, 30 min later | Area supervisors with maintenance, quality and planning | 15 min | Owners for tier 1 escalations, support committed with a time |
| Tier 3 for the plant Daily, 1 hour in | Plant manager with department heads | 15 min | Cross-area conflicts settled, yesterday's escalations checked closed |
| Leader standard work rounds Daily | Every leader, on a written route | 20 to 60 min | Boards checked, one closed action verified at the machine |
| Problem-solving review Weekly | Area manager with the CI lead | 30 min | Status of the root cause work opened from repeat reds |
| System review and audit Monthly | Plant manager's team and the CI lead | 1 to 2 hours | Share of leader routines done, audit score per area, board metrics checked against the plant's priorities |
Add it up: about an hour a day per leader in meetings and rounds, the same trade the day in the life further down shows in detail. The tier meetings guide has the minute-by-minute agenda for each tier and the escalation rules between them; the leader standard work guide has example routine cards for the daily rounds.
Why it comes before improvement
The instinct after strategy deployment is to launch improvement projects immediately: the priorities are named, so start improving. Resist it. Adding kaizen to an uncontrolled process is pushing water uphill, for three reasons.
- Without a daily baseline you cannot tell an improvement from a lucky week. A process that swings 15 percent day to day will absorb any kaizen result into its noise.
- Unattended processes drift. A gain that nobody checks daily erodes in weeks, and the plant runs improvement workshops to win back ground it already held. Daily management is the ratchet that holds each new level.
- Firefighting eats the same people who would improve. Until same-day response shrinks the firefighting load, the hours budgeted for improvement projects are fiction.
That is why the roadmap places daily management ahead of the kaizen practice and the whole Improve band. Stability is not the reward for improvement. It is the precondition. A plant that catches deviations the same day has, almost as a side effect, built the discipline that improvement work will later stand on.
How to build it in 90 days
Build the loop in one area first, then scale, and build it in the order the components depend on each other: visibility before meetings, meetings before escalation, escalation before leader routines. Choosing the handful of board metrics is its own decision; the manufacturing KPIs guide and the SQDIP guide cover it in depth. The sequence below assumes a mid-size plant and a CI lead or external coach at roughly half time.
| When | Focus | Who does what |
|---|---|---|
| Weeks 1 to 2 | Baseline and first board | Pick one pilot area with a supervisor who wants it, not the worst line in the plant. The supervisor and the CI lead choose 4 to 6 metrics the team can actually influence and record by hand at the end of each shift, usually one per SQDIP letter. Build the board on a whiteboard, not in IT. Record two baselines nobody will enjoy: how many deviations yesterday produced, and how long the oldest open issue has been open. |
| Weeks 3 to 4 | Tier 1 running daily | The team leader chairs a 10-minute tier 1 at the same time every day, standing at the board: safety first, then yesterday's misses, then today's plan, then one action per red. The area supervisor attends daily for two weeks to coach the team leader, then steps back. Expect the first week to be awkward and 20 minutes long; hold the time slot anyway. The one non-negotiable: every red gets an owner and a date before the meeting ends. |
| Weeks 5 to 8 | Tier 2 and escalation rules | Start tier 2: area supervisors plus maintenance, quality and planning, 15 minutes, right after the tier 1 round. Write the escalation rules down: safety always escalates; anything a tier cannot solve with its own people by end of shift escalates at the next meeting; and every escalation gets an answer, even an interim one, within 24 hours. That response promise is the most important sentence in the system. Roll boards out to the remaining lines in the area. |
| Weeks 9 to 12 | Leader standard work and problem solving | Start tier 3 with the plant manager, and give every leader from team leader to plant manager a short written routine: which boards to check, which questions to ask, which closed actions to verify at the machine. Connect problem solving: any metric red three times in two weeks triggers a 5 whys with the team that owns it. By week 12 the loop is closed: see, respond, escalate, verify. |
Two warnings from plants that have done this. First, do not launch plantwide on day one; ten boards installed in a week produce ten stale boards by week six, while one working loop recruits its neighbors. Second, do not let the boards be built by IT or the CI office alone. The team that must live with a board has to build it, argue about its metrics, and own the marker.
A day in the life of a working system
This is what the loop looks like when it runs, hour by hour, at the illustrative 450-person components manufacturer used across this site: 456 units a day, two shifts. Follow one issue, a bearing noise on press 2, from the night shift's handover note to a verified fix. The times are one plant's rhythm; the sequence and the same-day closure are the point.
| Time | What happens | Who acts |
|---|---|---|
| 05:50 Shift handover | The night-shift team leader writes handover notes on the board: press 2 developed a bearing noise at 03:00, output held by slowing the line; two pallets are on quality hold. The incoming team leader reads them before the first cycle, so the day shift starts informed instead of surprised. | Outgoing and incoming team leaders |
| 06:45 Tier 1 at the SQDIP board | Ten minutes, standing. Yesterday closed red on delivery: 438 of 456 units. The quality hold gets an owner and a due time. The bearing noise is beyond the team's means, so the team leader marks it for escalation. | Team leader with the line crew |
| 07:15 Tier 2 | Supervisors from four lines plus maintenance, quality and planning work through the escalations from the tier 1 boards. Press 2 is assigned to the maintenance planner with a due time of 10:00; quality commits to disposition the held pallets by noon. | Area manager chairs; support functions commit |
| 08:00 Tier 3 with the plant manager | Fifteen minutes: plant-level SQDIP, yesterday's escalations checked closed, cross-area conflicts settled. Press 2 is flagged as a delivery risk if it fails outright, so the plant manager releases a technician from a project job to cover it. | Plant manager with department heads |
| 10:00 Escalated issue answered | The bearing is replaced during the planned break. The answer is written on the tier 1 board before lunch: the team that raised the issue at 06:45 sees the response the same day, which is the moment the system earns their honesty. | Maintenance technician; supervisor closes the loop on the board |
| 14:00 Leader standard work round | The area manager walks the tier 1 boards with a five-point checklist: board current as of this shift, every red owned and dated, escalations answered on time, one operator asked what today's priority is, one closed action verified at the machine. | Area manager; the plant manager walks a different area each day |
| 06:45 next day Effectiveness check | Yesterday's fix is verified before it is closed: no noise on press 2 and a normal vibration reading, so the item comes off the board. A repeat within two weeks would trigger a 5 whys instead of a second repair. | Team leader at tier 1 |
Count the elapsed time: an issue detected at 03:00 was seen by the day shift at 05:50, escalated at 06:45, resourced by 08:00, fixed by 10:00, audited at 14:00 and verified the next morning. Total leadership time invested across all tiers: under an hour per leader per day. That trade, an hour of rhythm for same-day answers, is the whole business case.
Signs it is working vs signs it is theater
Daily management is the easiest lean practice to fake, because the props are cheap: boards, markers, a meeting invite. The test is never whether the ritual happens. It is whether deviations are answered in hours and whether the answers change what the floor does next.
Theater
- Boards are colored in at 4 pm from memory, all in one handwriting
- Meetings report status upward instead of deciding who acts today
- Escalations land on a parking lot list that nobody reads back
- The same metric is red for three weeks and no problem solving starts
- Ask a supervisor for the plant's top priority and you get a shrug
Working
- Deviations raised in the morning are answered in hours, on the board that raised them
- The 24-hour response promise is kept, and everyone can quote it
- Firefighting hours are falling: fewer surprise stoppages, shorter end-of-month pushes
- Supervisors quote the plant's priorities unprompted, because the cascade repeats them every morning
- The problem-solving queue is fed by board reds, and repeat deviations are declining
The fastest diagnostic is the board photographed at 09:00: if this morning's numbers are already up and this morning's reds already have owners, the system is alive. If the board fills in at 4 pm, in one handwriting, it is a report about the past wearing the costume of a control system.
Audit the system: 20 checks
The signs above are a quick read. The audit is the monthly proof. Walk it in the morning, at the board, from before tier 1 to the end of tier 2. Each check takes a few minutes of looking or asking, and you answer only from what you saw or heard. Every No gets an owner and a date, the same rule the boards follow for reds.
| # | Check | How to verify |
|---|---|---|
| Visual controls | ||
| 1 | This shift's numbers are on the board before the first tier meeting. | Look at the board before 09:00. Numbers filled in at the end of the day, in one handwriting, are a No. |
| 2 | Every red on the board has an action with one owner and a due date. | Count the reds, then count the actions with a name and a date beside them. |
| 3 | Each metric shows its target and the rule that makes the day red. | Ask an operator what makes today red for one metric. |
| 4 | An operator can say in one sentence whether the line is winning or losing today. | Ask one operator at random, not the team leader. |
| Daily accountability process | ||
| 5 | Tier 1, 2 and 3 started on time on each of the last five working days. | Check the meeting log or attendance record for the last week. |
| 6 | Meetings are held standing at the board and stay inside their timebox. | Observe one tier 1 and time it. Ten to fifteen minutes is the usual box. |
| 7 | The escalation rules are written down, and last week's escalations were answered within the promised time. | Trace three escalations from the board that raised them to the answer. |
| 8 | No open action is past its due date without a new date and a reason. | Find the oldest open action on the board or in the action list and ask why it is still open. |
| Leader standard work | ||
| 9 | Every leader from team leader to plant manager has a written routine. | Ask two leaders for their routine card: which boards, which questions, which actions to verify. |
| 10 | Last month's routines were recorded as done or missed, and the leader's own manager reviewed them. | Look at last month's record and ask the manager what they did about the misses. |
| 11 | Leaders verify closed actions at the machine, not on paper. | Ask a leader which closed action they checked today, and where. |
| 12 | Routines are covered during vacations by a named deputy. | Check the record for the last week a leader was away. |
| Leadership discipline | ||
| 13 | The plant manager chairs tier 3 and walks part of the plant on a fixed route every day. | Ask two area managers when the plant manager was last at their board. |
| 14 | Three supervisors name the same top priority for the plant. | Ask three supervisors separately and compare the answers. |
| 15 | A skipped meeting or a stale board is noticed by someone senior within a day. | Ask what happened the last time a board was not updated. |
| 16 | The team leader chairs tier 1; the supervisor coaches instead of taking over. | Observe one tier 1 and note who speaks most. |
| Structured problem solving | ||
| 17 | A metric red three times in two weeks has a root cause investigation open with the team that owns it. | Pick the most frequent red on one board and look for its 5 whys or RCCA. |
| 18 | Countermeasures are checked for effect before the problem is closed. | Look at the last three closed problems for the check and its date. |
| 19 | Repeat deviations are falling over the last quarter. | Count repeats per month from the board history or the action list. |
| 20 | Problem-solving topics come from board reds, not from a list made in the office. | Compare the open investigations with the reds on the boards. |
Free daily management audit checklist (Excel)
All 20 checks with how to verify each. Yellow columns for the auditor: Yes, No or N/A, what you saw, and an owner and a due date for every No. A score per element shows where the system is drifting, and N/A never lowers it. A second sheet explains how to run the audit.
Download the audit checklist (.xlsx)Free, no email needed. Opens in Excel, or in Google Sheets through File, Import. For the board the audit starts at, try the free SQDIP board template.
Sustaining it through leadership changes
Daily management systems rarely die loudly. They die when the champion leaves: a new plant manager arrives, does not walk the rounds, and within a quarter the boards are stale because everyone has learned that nobody senior looks. Three defenses work.
- Write the system down as standard work for leaders, not as culture. Meeting agendas, escalation rules, board standards and each leader's daily route belong in a short controlled document, so the system is a role requirement that transfers with the chair, not a personal habit that leaves with the person.
- Audit the system itself. Run the checklist above every month, or put the daily management loop on the layered process audit schedule, so someone checks that meetings start on time, reds carry actions, and escalations get answers. The audit protects the system during exactly the months when attention drifts.
- Make the routine the onboarding. A new plant manager's first week is walking the tier structure and the board rounds with the area managers. They inherit a calendar and a checklist, not a philosophy to rediscover.
The deep guides on leader standard work and layered process audits cover the first two defenses in detail.
What happens next on the roadmap
A running loop produces a byproduct more valuable than any single save: a clean, prioritized stream of documented deviations. That stream is what structured problem solving feeds on. Instead of hunting for projects, the plant's 5 whys and root-cause work start from problems the boards have already found, sized and dated. From there the Improve band opens: kaizen finally accumulates, because the daily loop holds each gain in place.
Run the first 90 days on whiteboards. What eventually breaks is not the format but the memory: escalations crossing shifts and departments, actions that outlive the supervisor who wrote them, a plant manager handover that resets nothing. That is where software earns its place.
In TeamGuru each tier meeting runs as a standardized meeting with a fixed agenda, attendance and its own action list, so open actions are still on the table the next morning. The SQDIP widget in Reports shows the board's metrics with their open actions. An action the team cannot close is escalated by hand, to named colleagues or along timed levels, by email or SMS. Leader routines live in Leader Standard Work, with monthly attainment for each routine. The aim is the same as on the whiteboard: a same-day answer that survives turnover instead of depending on who happens to be in the room.
The meeting management, KPI management and leader standard work use cases show how the pieces fit. The tier meeting software comparison sets TeamGuru beside the other tools.
Take this with you
The diagram from this guide as a shareable image, free to reuse in internal training and workshops.
Download PNGFrequently asked questions
What is lean daily management?
What are the four elements of a lean daily management system?
What is tiered daily management?
What is the difference between lean daily management and tier meetings?
How long does it take to implement lean daily management?
Do you need software for lean daily management?
What does the plant manager do daily in this system?
How do you measure whether daily management is working?
How TeamGuru runs this