Lean Daily Management: Tier Meetings and Escalation

What lean daily management is

Lean daily management is a routine of short, layered meetings, called tier meetings, in which each level of the plant reviews the previous day's results, follows up on open actions and escalates whatever it cannot solve. Problems move up in hours, not weeks, and decisions come back down with an owner and a due date.

Each tier uses a board, preferably an SQDCM board, and a fixed time. The whole works like a nervous system: the floor feels the problem, and leadership is told the same day.

Visual map of lean daily management

The map shows the meeting tiers, the escalation rule and the example with the time load of the routine.

The tiers and who attends

Times follow a cascade: tier 1 before tier 2, tier 2 before tier 3. A problem raised at 7:05 then reaches the plant level the same morning.

The escalation rule

The question that drives the routine is simple: who can solve this, and by when? A starting rule:

• Tier 1: solves what the team can fix within the same shift.
• Tier 2: receives what was not solved in one shift, or depends on another cell, and has up to 24 hours.
• Tier 3: receives what depends on another department (purchasing, engineering, a supplier) and handles it within 48 hours.
• Tier 4: receives what needs investment, a policy change, or has been recurring for weeks.

Nothing goes up as a complaint. It goes up with data: which metric left target, what was already tried and what is requested from the tier above. If the higher tier does not respond, the problem falls back to the floor and nobody learns that the board works.

Example: the time load of the routine in a plant

Fictional example: a plant whose shift starts at 7:00, with 12 people in the cell meeting. Daily schedule:

Daily load = 12 × 10 + 6 × 15 + 8 × 20 = 370 person-minutes ≈ 6.2 h

For the production team, the tier 1 meeting uses 10 ÷ 480 = 2.1% of an 8-hour shift. That is the price of a problem being visible at 7:05 and another function responding before 8:30. Compare it with the cost of finding the same problem in next week's report.

Case: a problem climbs the tiers

We continue the SQDCM board example: a missing component at station 4 that caused 48 minutes of downtime on Wednesday.

1. 7:05, tier 1: the leader logs the stop as red in Delivery (432 of 480). The team does not control replenishment.
2. 7:25, tier 2: the area supervisor confirms recurring stops from replenishment and calls internal logistics.
3. 8:05, tier 3: logistics and planning set a fixed replenishment route and schedule. 5W2H action: owner, due Friday.
4. Thursday, 7:05: tier 1 checks that replenishment happened on time. The loop closes where it began.

The deviation started and ended on the same board in under two working days. An andon signal can call support during the shift, and tier 1 handles what remains.

Standard agenda for each meeting

1. Attendance and safety (always the first topic).
2. Red metrics from the previous day, only those off target.
3. Open actions: what is overdue, what is done, what needs help.
4. Escalation: what goes up, with data and a clear request.
5. Plan for the day: delivery and quality risks.

Ground rules: standing, at the gemba, at a fixed time, no laptops and no solving on the spot. If a problem needs analysis, schedule a 5 Whys session outside the meeting with the people involved.

The leader's role: standard work and verification

The routine only holds if the leader also has a routine. This is leader standard work: running the meeting, doing the gemba walk to check the board, and following up on actions. We go deeper in lean leadership and management at the gemba. The higher tier asks about the process ("what happened, what did you do?"), not about who to blame.

How to implement in four steps

1. Start with tier 1 in one or two cells, with an SQDCM board and a 10-minute meeting. Stabilize for 4 to 6 weeks.
2. Add tier 2 as soon as there are problems to escalate, setting cascaded times.
3. Define escalation criteria in writing: what goes up, when and to whom.
4. Link to strategy: board targets should come from the annual deployment, as in hoshin kanri. Where a management room exists, the Obeya brings the upper tiers together.

Common mistakes

• The meeting turns into a report: numbers read aloud, no action, no escalation.
• Tiers with no time cascade: the problem goes up, but the answer arrives days later.
• Leaders who do not go to the gemba and do not respond to escalations.
• Long, seated meetings. Past 15 minutes, you are solving problems at the wrong time.
• Too many metrics, or different ones across tiers: the data does not roll up between boards.
• Hunting for someone to blame instead of causes; the team starts hiding problems.

Frequently asked questions

What are tier meetings?

Short, cascading meetings in layers (tiers), where each level reviews its metrics and escalates what it cannot solve.

How many tiers does a plant need?

Usually three to four: team, area, plant and, weekly, leadership. Small plants can start with two.

How long should each meeting last?

Ten minutes at team level, about 15 at area level and 20 at plant level. If it runs longer, the agenda is loose or people are solving problems in the meeting.

What is the difference between daily management and SQDCM?

SQDCM is the metrics board; daily management is the routine of meetings and escalation that uses the board.

How do you stop the meeting from turning into a reading of numbers?

Focus on the reds, require an action with an owner and a date, and review overdue actions at the start of the agenda.

Who runs the meeting?

The leader of that tier: the team leader at tier 1, the supervisor at tier 2 and the manager at tier 3. The tier above joins as a listener during visits.

About the author

Vagner Soares

Lean Manufacturing & Behavioral Management Specialist

Over 20 years in the automotive and metalworking industries (GM and Dana), Lean Manufacturing practitioner since 2006. SENAI instructor and mentor in Brazil’s Brasil Mais Produtivo program, delivering consulting, training and audits for 50+ companies, combining quality, productivity and people development.

LinkedInInstagramFull profile →