Tier boards are the visual management infrastructure for the lean tiered daily management system: a structured hierarchy of brief, daily meetings at each organizational level that resolves operational problems at the lowest level possible and escalates only what cannot be resolved to the next level up. The Lean Enterprise Institute describes daily management as the mechanism that connects strategy with execution. Tier boards are the physical and visual component of that mechanism: at each tier, a board displays the SQCDM performance data relevant to that tier's scope, making the current state of safety, quality, cost, delivery, and morale visible to the people responsible for managing it without requiring them to extract data from reports or wait for a formal review.
The tier system solves two interconnected information problems. Problems discovered at the front line are invisible to plant leadership until they have already become production failures. Leadership priorities are invisible to frontline teams until they have already been missed. iObeya describes the tier system with a practical example. A defect surge on an assembly line discovered at the Tier 1 meeting at 7:30 AM triggers escalation to the Tier 2 meeting at 8:00 AM where maintenance and quality are involved, reaching plant leadership context by 9:00 AM if not resolved. Without the tier system, the same problem might be discovered by plant leadership in a weekly report three days later.
The Four-Tier Structure
The tiered daily management system operates through four defined meeting levels, each with a distinct scope, audience, and meeting duration. The structure is designed so that each tier meets and resolves what it can before the next tier meets, allowing each successive tier to start with escalated issues rather than raw data.
Tier 1: Frontline Team Level
Tier 1 is the foundational meeting, led by the team leader or cell leader with the frontline production team at the start of each shift. A Lean Journey confirms the standard structure: Tier 1 occurs at shift start, covers the production board data from the previous period, identifies any open issues, and sets the team's priorities for the shift ahead.
Duration: 10 to 15 minutes maximum, standing at the production board or team tier board in the work area.
Tier 1 focuses on:
- Safety observations or near-misses from the previous shift
- Quality performance (first pass yield, defect counts, customer flags)
- Production performance (planned vs. actual output, gaps, recovery plan)
- Open issues from the previous shift and their current status
- Priorities and targets for the current shift
Issues that cannot be resolved at Tier 1 are logged on the board and escalated to Tier 2 with a clear problem description and the information gathered so far.
Tier 2: Supervisory Level
Tier 2 is led by the supervisor with team leaders from multiple cells or lines and dedicated support representatives from quality, maintenance, and materials. The meeting aggregates the escalated issues from all Tier 1 meetings in the area and resolves what can be resolved with supervisory authority and cross-functional support.
Duration: 15 to 20 minutes, standing at the Tier 2 board which shows aggregated SQCDM performance across all cells or lines in the supervisor's scope.
Tier 2 reviews escalated issues from Tier 1, identifies patterns across multiple cells (a quality issue appearing on three lines simultaneously may indicate a supplier or incoming material problem), and assigns cross-functional resources to problems that cannot be resolved by the team leader alone.
Tier 3: Value Stream or Area Manager Level
Tier 3 is led by the value stream manager or area manager with supervisors and support staff representatives. This is the first tier where overall production performance across the entire value stream or manufacturing area is reviewed in aggregate. A Lean Journey notes that Tier 3 is the first meeting where all production for a site or value stream comes together and is summarized as a whole.
Duration: 20 to 30 minutes, typically standing at the Tier 3 board in a central location visible to all participants.
Tier 3 addresses escalated issues that require area-level resources or authority, reviews SQCDM trend data across the full value stream, and identifies systemic conditions that require improvement project launches rather than immediate corrective action.
Tier 4: Plant Leadership Level
Tier 4 is led by the plant manager with production and support staff members. Richard Clark's tier process framework identifies Tier 4 as focused on both run-the-business and improve-the-business activities. The meeting reviews plant-level SQCDM performance, addresses escalated issues from Tier 3, and ensures that daily operational performance connects to the plant's strategic improvement priorities.
Duration: 30 minutes or less, with the plant-level SQCDM board showing consolidated performance across all areas.
Key Insight: Each tier resolves what it can and escalates only what it cannot. A problem resolved at Tier 1 never consumes plant leadership time. A problem requiring plant authority reaches leadership the same morning it surfaces.
The SQCDM Board: What Each Tier Displays
Each tier in the system has a board displaying SQCDM performance at the scope relevant to that tier. SQCDM stands for Safety, Quality, Cost, Delivery, and Morale: the five dimensions of manufacturing performance that together provide a complete operational picture. Some organizations use SQCDP (replacing Morale with People) or SQDCP, but the structure is equivalent.
The SQCDM board at each tier typically displays:
Dimension: Safety
- What is tracked: Near-miss count, days since last incident, safety observations completed.
Dimension: Quality
- What is tracked: First pass yield, defect count, customer complaints, CAPA status.
Dimension: Cost
- What is tracked: Productivity vs. plan, OEE, scrap cost, rework hours.
Dimension: Delivery
- What is tracked: On-time delivery rate, output vs. schedule, changeover performance.
Dimension: Morale/People
- What is tracked: Attendance, open positions, training completion, recognition.
Each metric is displayed with a target and a color code: green for meeting target, red for below target. The board at a glance shows which dimensions are performing and which require attention, without requiring the reader to analyze raw data.
The tier board is updated before each meeting from the data captured at the level below. Tier 1 board data feeds the Tier 2 board. Tier 2 data feeds Tier 3. This cascade means that by the time the Tier 4 meeting begins, plant leadership is reviewing a consolidated picture assembled from real operational data captured at the frontline level, not a management summary compiled by a staff analyst.
Key Insight: The SQCDM board shows five dimensions simultaneously. A plant that is green on four and red on one has a visible priority. A plant that is red on all five has a visible crisis.
The Escalation Logic: Resolving Problems at the Lowest Level
The defining principle of the tier system is that problems should be resolved at the lowest level possible. This principle has two operational implications that determine whether the tier system functions as designed or degrades into a reporting hierarchy.
Issues are resolved before escalation where possible. A Tier 1 issue that the team leader and operator resolve during the shift is closed at Tier 1. It does not appear at Tier 2, does not consume supervisor time, and does not add to the escalation list that reaches plant leadership. The tier system's value is measured partly by what does not reach Tier 4 — a well-functioning system resolves the majority of daily operational issues at Tier 1 and Tier 2.
Issues are escalated with context, not just with the problem. When an issue escalates from Tier 1 to Tier 2, it carries the information gathered at Tier 1: what the problem is, when it started, what has already been tried, and what resources or authority are needed to resolve it. An escalation without this context forces the receiving tier to restart the investigation rather than advance it, defeating the speed advantage the tier system is designed to provide.
The practical example from iObeya illustrates how this works in operation. A scrap rate surge on one line is identified at Tier 1 at 7:30 AM. The team leader logs the issue and escalates because the cause is not immediately identifiable. At Tier 2 at 8:00 AM, the supervisor and maintenance technician investigate and identify a tooling issue. If tooling cannot be replaced within the supervisor's authority, the issue escalates to Tier 3 with a specific request: a replacement tooling set from central stores and authorization for a production schedule adjustment.
Key Insight: The tier system's measure of success is what does not reach Tier 4. Issues resolved at Tier 1 and Tier 2 are the system working correctly.
Common Tier System Failures
The tier system is one of the most widely attempted and most frequently degraded lean management tools. Four failure patterns appear consistently across manufacturing organizations that implement tier meetings without the supporting discipline.
Meetings become reporting sessions. When tier meetings focus on reviewing what happened rather than on resolving what is happening, they lose their operational value. A ten-minute meeting that reviews yesterday's production numbers generates information without action. A ten-minute meeting that reviews open issues and assigns resources to close them generates accountability. The distinction is the meeting agenda: performance review versus issue resolution.
Escalation is not disciplined. When every issue from Tier 1 is escalated to Tier 2 regardless of whether the team leader could resolve it, the tier system adds meeting overhead without the problem-resolution benefit. Supervisors spend their time on issues the team leader should have closed. Plant leadership receives an undifferentiated list of operational details rather than the strategic issues requiring their attention. Escalation discipline requires team leaders who understand what is within their authority to resolve and what requires the next level.
Boards are not updated before meetings. A tier meeting conducted without current data on the board is a meeting without a shared factual basis. Participants discuss what they believe happened rather than what the board shows happened. Boards must be updated before each tier meeting, and the data quality of the boards determines the quality of the decisions made in the meetings.
The system does not connect to improvement projects. A tier system that identifies recurring issues without connecting them to kaizen projects or A3 investigations produces daily accountability without organizational learning. Issues that appear repeatedly on tier boards are by definition systemic conditions that improvement activities should target. The connection between tier board findings and the improvement project pipeline covered in [Prioritization Matrix in Lean Manufacturing: Impact vs Effort] is what converts daily management from operational maintenance into continuous improvement.
Key Insight: Tier meetings that review what happened generate information. Tier meetings that resolve what is happening generate accountability. The agenda determines which one occurs.
Within the Lean System
Connection to Lean Principles
The tier board system operationalizes the lean principle of pursuing perfection by creating a daily mechanism that makes the gap between current performance and the target visible at every organizational level simultaneously. The [5 Core Principles of Lean Manufacturing] positions perfection as the ongoing pursuit of the ideal condition through continuous waste elimination. The tier system makes this pursuit daily rather than periodic. Every morning, every level of the organization reviews its SQCDM performance against target, identifies deviations, and assigns resources to close them. The hoshin kanri strategic deployment system covered in [Hoshin Kanri: 7-Step Strategy Deployment Process] connects to tier boards through Tier 3 and Tier 4 meetings: the breakthrough objectives deployed through hoshin kanri appear as targets on the upper-tier SQCDM boards, making the connection between daily operational performance and annual strategic goals visible.
Connection to Lean Tools
The tier board system connects directly to [Production Boards: Real-Time Team Communication on the Shop Floor] as the first level of the escalation hierarchy. The production board at the workstation level feeds the Tier 1 meeting. Issues escalated from Tier 1 appear on the Tier 2 board. This information cascade is the mechanism through which frontline operational data reaches plant leadership in the same morning it is generated rather than in a weekly summary. The tier system also connects to [Kamishibai Board: A Guide for Manufacturing Teams]: kamishibai boards track audit compliance at a level of detail that tier meetings review in aggregate. The kamishibai finding that a specific audit has been missed for three consecutive shifts is an escalation trigger that surfaces at the tier meeting for the relevant level.
Connection to Continuous Improvement
The tier board system connects to the [PDCA Cycle: The Foundation of Continuous Improvement] as the daily management infrastructure through which every level of the organization runs its own PDCA cycle. The Tier 1 meeting is the daily Plan and Check for the frontline team. The Tier 2 meeting is the daily Check and Act for the supervisory level. The tier system as a whole is the organizational mechanism through which PDCA becomes a daily discipline rather than a periodic improvement project. [Kaizen: The Complete Beginner's Guide to Continuous Improvement] describes the connection between daily problem identification and systemic improvement: issues that appear on tier boards day after day are the kaizen inputs that improvement programs should be addressing. The tier system makes those inputs visible and traceable.
Frequently Asked Questions
What is a tier board in lean manufacturing? A tier board is the visual management tool for a specific level of the tiered daily management system, displaying SQCDM (Safety, Quality, Cost, Delivery, Morale) performance data relevant to that level's organizational scope. Tier boards support brief, structured daily meetings at each level, from frontline teams at Tier 1 to plant leadership at Tier 4, where performance is reviewed, issues are resolved at the lowest possible level, and unresolved issues are escalated with context to the next tier.
How many tiers are in a tiered daily management system? Most manufacturing implementations use three or four tiers. Tier 1 is the frontline team meeting at shift start, led by the team leader with the production team. Tier 2 is the supervisory meeting with team leaders and cross-functional support. Tier 3 is the area or value stream manager meeting with supervisors. Tier 4 is the plant leadership meeting with managers and support staff. Some organizations use three tiers, combining the supervisory and area manager levels based on facility size and organizational structure.
What does SQCDM stand for in tier meetings? SQCDM stands for Safety, Quality, Cost, Delivery, and Morale: the five dimensions of manufacturing performance tracked on tier boards. Each dimension is displayed with a target and color coded green for meeting target or red for below target. Some organizations use SQCDP (replacing Morale with People) or SQDCP, but the five-dimension structure is consistent. The board makes it immediately visible which dimensions are performing and which require focused attention.
What is the difference between a tier board and a production board? A production board tracks output performance at the workstation or cell level throughout a shift: planned vs. actual output by hour, open issues, and shift context. A tier board displays SQCDM performance at the organizational level relevant to each tier's meeting scope. Production boards are updated hourly throughout the shift. Tier boards are updated before each daily meeting from the data captured at the level below. Production boards feed Tier 1. Tier 1 data feeds the Tier 2 board.
Why do tier systems fail in manufacturing? Tier systems most commonly fail when meetings become reporting sessions reviewing what happened rather than resolving what is happening, when escalation discipline is weak and every Tier 1 issue reaches plant leadership, when boards are not updated with current data before meetings, and when recurring tier board issues are not connected to improvement projects. The tier system requires disciplined adherence to defined meeting durations, escalation protocols, and board update responsibilities to deliver its intended value.
LeanSuite: A complete lean manufacturing software
Schedule Demo
