Tier Huddle System

Tiered daily management connects floor execution to site leadership. When it works, problems surface fast and solutions flow back down just as fast. When it degrades, every tier becomes a status meeting where people report what happened with no action assigned and no escalation.

The Four Tiers

Tier 1 — Supervisor and Team | Every Shift | 5 Minutes

Location: At the Tier 1 board in the work area, at shift start. Led by: Supervisor. Team leads and operators attend. Format: Standing meeting — literally standing. Chairs invite 25-minute meetings. Standing enforces the 5-minute discipline.

Content:

• Yesterday’s results vs. target (safety, quality, pick rate, OTIF)
• Today’s target and known constraints (short staffing, equipment downtime, wave complexity)
• Open issues from yesterday’s Tier 1 needing follow-up
• Problems from the floor the team wants to surface

Resolves: Anything within supervisor authority — standard work clarifications, task assignments, minor equipment adjustments, immediate safety concerns. Escalates: Any problem the supervisor can’t resolve within the shift; resource needs requiring ops manager authority; recurring issues needing CI investigation.

Tier 2 — Operations Manager | 15 Minutes | Daily

Location: At the Tier 2 board in the operations area — not in a conference room. Attendees: Supervisors report up. CI engineer participates with data on open improvement items and 30-day Kaizen action register status.

Content:

• Site-level KPIs reviewed across all functions: receiving UPH, pick UPH by zone, pack throughput, dock-to-stock, OTIF
• Top 1–2 problems from each function’s Tier 1
• Escalated problems get an owner and a date — ops manager assigns accountability on the spot, not at the next meeting

Resolves: Cross-functional resource allocation; ops-manager-authority problems; equipment maintenance escalation; staffing changes. Escalates: Safety incidents; client-impacting quality events; problems requiring site leader authority or cross-departmental coordination.

Tier 3 — Site Leader | 30 Minutes | Daily (Weekly for Smaller Sites)

Attendees: Operations managers report up.

Content:

• Week-to-date performance vs. plan
• Safety metrics (TRIR, near-miss rate)
• CI project status
• Client scorecard items
• Cross-functional issues: WMS/systems problems, HR/labor relations, client service issues, maintenance capital requests

Decides: Overtime authorization for the week; escalating WMS issues as critical IT fixes; expediting CI project resources.

The site leader actively challenges the data — not accepting “we had a tough week” without a root cause and countermeasure.

Tier 4 — Regional | 60 Minutes | Weekly or Monthly

Content: Network-level trend data, multi-site benchmarking, CI program portfolio status across sites.

Critical function: Best-practice propagation. A slotting improvement at one site driving 15% pick productivity improvement should become the standard approach across the network, not stay siloed.

The Single Biggest Failure Mode

Most tier huddles degrade into status meetings. People report numbers. Others nod. Meeting ends. Nothing changes. Three weeks in, attendance slips because meetings clearly aren’t driving action.

Root cause: no accountability between meetings. When ops manager assigns three items at Tier 2 and nobody checks at the next Tier 2 whether they were resolved, the message is clear — assignments don’t need to be completed. The meeting becomes a ritual of reporting.

The Fix — Structural, Not Motivational

1. Every escalated issue gets an owner, an action, and a date — written on the board, in the room. Not “we’ll figure out who handles this.” Named person, specific action, specific date.

2. The first agenda item at every tier meeting is the status of the previous meeting’s open actions. Not new reporting — review of whether last time’s actions were completed. If not, why not? This discipline makes assignments real.

3. The CI engineer tracks open Tier 2 and Tier 3 actions in the CAPA tracker. Anything open past its due date → red flag on the board → conversation with the assigned owner. The CAPA tracker is the institutional memory of the huddle system.

4. The site leader participates in Tier 2 at least once per week — as an active participant, not an observer. When the person who controls resources is present and asking questions, problems get solved faster and assignments get completed. When leadership is absent, urgency follows.

A tier system running on autopilot without active maintenance drifts to status meetings within 90 days. That’s not a criticism of the people in it — it’s the nature of any system that lacks its own accountability structure.

CAPA Tracker Connection

The CAPA tracker (see Structured Problem Solving) is the formal mechanism connecting tier huddles to closed-loop problem solving:

• Open corrective actions from A3 reviews, Kaizen events, audit findings, and FMEA mitigations all flow into it
• Each line: problem, root cause, action, owner, due date, verification method
• CI engineer maintains and brings visibility to Tier 2 daily
• Overdue items escalate from Tier 2 → Tier 3 → Tier 4 based on age and impact