Daily management: the routines that turn a bad hour into same-day action

What daily management covers, and why it decides how fast a plant reacts

Losses happen in minutes. Most management systems review them in weeks. Daily management is the layer in between: the set of fixed routines that makes sure a problem seen at 07:40 reaches someone with the authority to solve it before the end of the day, and that the team that raised it hears back.

It carries weight because every other pillar depends on it to run. Loss data is only useful if a meeting looks at it. A root-cause method is only used if an escalation rule triggers it. Improvement actions only close if a routine reviews them. When daily management is missing, those practices exist on paper and happen when someone has time.

It also decides what a supervisor's day is for. Without defined routines, supervisors default to firefighting, and the plant becomes dependent on a few people who know whom to call. With them, the plant behaves the same way on the night shift as on the day shift, and the same way when the plant manager is on holiday.

None of this needs software. Every practice in this pillar can run with a whiteboard and a printed form. What the assessment scores is whether the routine is actually followed, and whether it ends in a decision.

The five levels as you would see them on the floor

Use the table to place your plant before you take the assessment, then compare with your pillar index. Remember the weakest-pillar rule on the levels page: a plant cannot sit more than one level above its weakest pillar, however strong the others are.

The five questions and how plants misjudge themselves

Self-assessment drifts easily on this pillar, because the routine is usually written down somewhere and the person answering attends the best-run meeting of the day. Each check below takes less than a week and uses nothing but a notebook and a watch.

1. Is there a structured daily performance meeting? We are asking whether issues flow from the line to someone who can decide, on the same day. Plants over-rate by describing the design of their cascade rather than its practice: the line meeting that gets skipped when the line is busy, or a plant meeting that runs to 45 minutes because it does the work the lower tiers did not.

2. How does the shift handover work? We are asking whether the incoming shift starts with everything it needs, and whether every open issue leaves the handover with a name. The usual over-rating: a standard form exists, but it is filled in after the outgoing leader has left, or copied from the day before.

3. What does visual management at the line look like? We are asking whether someone walking past can see if the line is on plan and what is wrong. Over-rating comes from boards that are updated by the supervisor rather than the team, or hourly columns filled in at the end of the shift. Under-rating also happens: plants with a well-used paper board sometimes assume Level 4 requires screens. It does not.

4. How are abnormalities escalated? We are asking whether escalation follows written rules with time triggers, and whether those rules are used. A matrix on the wall that nobody follows is Level 2 in practice, whatever the laminate says.

5. Do supervisors and managers follow a defined daily routine? This is leader standard work. We are asking whether leaders' days have protected structure, including floor time and checks, and whether anyone looks at adherence. Plants over-rate by answering from the written routine rather than the diary.

What Level-4 plants do differently

Plants at Level 4 on daily management do not hold more meetings than others. They hold shorter ones, in a fixed order, with a strict rule about what each tier is for. These are the practices that separate them.

• A timed sequence. Line meetings finish before the department meeting starts, and the department meeting finishes before the plant meeting. For example: lines at 08:00, department at 08:20, plant at 08:40. Each tier works from what the tier below sent up.
• Standing, at the board, with a timer. Fifteen minutes is the ceiling, not the target. A topic that needs longer leaves the meeting with an owner and a slot, and is not discussed further there.
• The same agenda at every tier. Safety, quality, output, issues, in that order, so anyone from any tier can join any meeting and follow it.
• A written rule for escalating. An issue goes up the same day when it needs authority, budget or another department that the tier does not control. Everything else is solved where it was raised.
• An issue list with an answer-back date. Each escalated issue is recorded with the date raised, who raised it, the owner, the due date and the date the answer went back to the team. The last column is the one most plants are missing.
• Handover as a five-minute meeting. Face-to-face, at the board, both leaders present. Every open issue is handed to a named person, and the incoming leader signs the form.
• Escalation with time triggers and a third step. For example: a stop over 10 minutes calls the technician, over 30 minutes the supervisor, over a longer limit set by the plant the production manager. Quality holds and material shortages have their own lines on the same page.
• Layered process audits built into the routine. Each level checks a few standard points at the line on a set frequency: team leaders daily, supervisors and managers less often. The findings feed the issue list rather than a separate report.

A 90-day plan to move up one level

Your report gives a specific next move for each of the five questions. The plan below combines them for a plant with a daily meeting that exists but varies, free-format handovers and escalation by phone call. Start with the bottleneck line and one supervisor; add lines once the first one holds for a month.

1. Weeks 1–2Map every meeting that touches production today: who, when, how long, what is decided. Fix one time and place for the daily meeting and write the four-heading agenda. Start timing it. Write one page per line listing whom to call for a breakdown, a quality problem and a material shortage on every shift, with a time rule for each, and post it at the line.
2. Weeks 3–6Add a line-level meeting on the bottleneck, held before the plant meeting and at its board. Move the handover to a five-minute face-to-face at the board using a one-page form. Switch the bottleneck board to hour-by-hour with a reason next to every missed hour. Log every escalation with the time it was raised and the time it was answered.
3. Weeks 7–12Start the issue list with an answer-back date and review response times weekly. Adjust the escalation triggers using the log. Write each supervisor's daily routine on one page and add a short layered audit of a few standard points. At week 12, repeat the five self-checks above and retake the assessment.

Who owns what during the 90 days:

• Plant manager: protects the meeting times, attends the plant tier every day, and starts following a written routine of their own.
• Production manager: the agenda, the tier sequence, the issue list and the weekly review of response times.
• Team leaders: the line meeting, the hour-by-hour board and the handover.
• Maintenance and quality leads: attend the tier where their issues surface and respond within the escalation triggers.
• Continuous improvement lead: observes a sample of meetings and handovers each week and coaches the leaders who run them.

Evidence a jury looks for in verification

Daily management is easy to describe and hard to fake over several weeks, which is why jurors in verification ask for records that span several weeks. A routine that exists leaves traces every day.

• The meeting schedule showing the tier sequence and times, with attendance records for at least a few weeks.
• Photos of a tier board with its issue list, showing dates raised and dates answered.
• Handover forms from consecutive shifts over a week, with names against open issues.
• The escalation matrix as posted at the line, plus the log of real escalations with times raised and answered.
• Hour-by-hour boards from several consecutive days.
• Written leader standard work for supervisors and managers, and completed layered audit checklists.
• If you are willing, a short recording of a line meeting as it normally runs.

What does not count: an agenda template with no sign of use, minutes typed up after the fact as the only record, an escalation matrix without a log, or leader standard work for supervisors only when you claim Level 5. In the interview, expect to be asked to follow one escalated issue from the line to its answer.

Pitfalls that keep plants stuck on this pillar

• Meetings that report instead of decide. People read figures everyone could have read on the board. Ask each tier to end with a list of decisions and escalations; if the list is empty for a week, the meeting needs redesigning.
• The meeting only happens when the boss is there. If the daily meeting is skipped when the plant manager travels, the routine belongs to a person, not the plant.
• Escalation without an answer back. Teams raise issues for a few weeks, hear nothing, and stop raising them. The silence then looks like improvement.
• Too many tiers for the plant. A small plant with one supervisor does not need three meeting levels. Two tiers held reliably beat three held occasionally.
• Boards as wallpaper. Several boards per line, each started by a different initiative and none current. One board per line, maintained, is worth more.
• Handover forms filled alone. The form becomes a ritual and the real handover happens in the car park, or not at all.
• Leader standard work used for control. When adherence reviews are used to catch people out, supervisors fill in the checklist and stop doing the walk.

Where to go next

Score your plant in the FEI assessment: it takes 12 to 15 minutes and gives you a pillar index here plus a 90-day move for your biggest gaps. If your report shows strong routines but weak data, read performance visibility first. Otherwise, the next pillar is loss and downtime problem-solving, which covers what happens to an issue once your routines have escalated it.

Questions