Daily Management System
Most problems get solved at the wrong level because there's no system for surfacing them to the right one. Daily management fixes that. Tier-board structure, KPI selection, escalation logic, and response-to-abnormality protocol, built for your operation.
Problems This Solves
Four signs a daily management system is missing
Tier Structure
Three tiers. Escalation flows up. Resolution flows down.
Each tier covers a specific scope, frequency, and duration. A problem a tier can't resolve with its own authority moves up to the next tier, not because someone has to decide to escalate, but because the system requires it.
A problem that escalates from T1 to T2 is the system working. The failure mode is a problem that should escalate but doesn't, because no one owns the trigger, or because the team is afraid to surface it. The skill builds the escalation protocol into the board design from the start.
KPI Selection
Lead indicators vs. lag indicators
Most tier boards only show lag indicators: results from last week. By the time a lag indicator goes red, the underlying problem happened days ago. Lead indicators tell you what's happening today, while you can still act on it.
- % of preventive maintenance completed on schedule
- Hours of cross-training completed this week
- Number of near-misses reported
- First-pass yield at the pacemaker step
- Monthly customer defect rate
- Total recordable incident rate (TRIR)
- On-time delivery %
- Cost per unit
Every KPI on a tier board should answer the question: can the team act on this today? If the answer is no, it's a lag indicator. It's useful for T3 trend review but not for T1 daily response. The skill helps select 3–5 lead indicators per tier before adding any lags.
Response-to-Abnormality Protocol
Detect → Contain → Escalate → Analyze
Every abnormality needs a defined protocol, not a conversation about what to do. The protocol specifies who does what at each step. Define the escalation thresholds in advance, so nobody has to judge each case from scratch.
Board Content Guide
What belongs on each tier board
Each tier board covers different content: more detail and shorter time horizon at T1; more aggregation and longer trends at T3. Putting T3 content on a T1 board is one of the most common ways a daily management system stops working.
| Content Area | Tier 1 (Cell) | Tier 2 (Dept) | Tier 3 (Plant) |
|---|---|---|---|
| Safety | Near-miss count, Days since last incident (cell) | TRIR trend, open corrective actions | Facility TRIR, regulatory compliance status |
| Quality | First-pass yield, defects by type (today) | Customer defect rate, internal scrap cost | Warranty / return rate, audit scores |
| Delivery | Units vs. target by hour, on-time to next step | On-time shipment %, schedule attainment | Customer on-time delivery, backlog trend |
| Cost | Overtime hours, material waste (shift) | Labor cost vs. budget, scrap $ this week | Cost per unit, budget variance |
| People | Attendance, cross-training status, open escalations | Turnover, training completion % | Engagement, headcount vs. plan |
Examples
Manufacturing and healthcare tier systems
Assembly plant: 3-tier DMS for a plant with 4 value streams and 18 cells. T1 huddles at 6:05 AM (5 min), T2 at 6:20 AM (15 min), T3 on Monday mornings (30 min). Lead KPIs selected: first-pass yield at pacemaker, PM completion rate, near-miss count.
Plant: Final Assembly — 18 cells, 4 value streams
Tier 1: 6:05 AM · 5 min · Cell lead + operators
Tier 2: 6:20 AM · 15 min · Dept manager + cell leads
Tier 3: Monday 7:00 AM · 30 min · Plant manager + dept heads
T1 lead KPIs: First-pass yield · PM completion % · Near-miss count
Escalation trigger: Any abnormality beyond the cell's authority → dept manager right away, then on the T2 board at the next 6:20 AM huddle
[NEEDS GEMBA: confirm current T1 board owners for cells 9–12]Hospital unit daily management: T1 at each nursing station (daily huddle, 5 min), T2 at charge nurse level (daily, 15 min), T3 at department director level (weekly, 30 min). Lead KPIs adapted for clinical context: patient safety events, hand hygiene compliance, throughput vs. target census.
In clinical settings, "abnormality" includes patient safety events, near-misses, and falls, not just throughput metrics. The skill builds the safety response-to-abnormality protocol around immediate containment, event reporting, root cause review at T2 and systemic action at T3. It supports your event-reporting process. It does not replace your organization's Joint Commission or sentinel-event procedures.
What you get
A real run on the sample data
Unedited output. The sample message at the top went to Claude Sonnet 4.6 (an earlier-generation model, so a newer one may word things differently) with this skill pasted in, the same way the steps below show, on September 29, 2026. Scroll inside the frame to read the whole reply.
Installation
Describe your operation. Get the system design.
resources/examples folder.Related Skills
Daily management connects the whole improvement system
A daily management system surfaces abnormalities. Kaizen events and root cause analysis are how you resolve the recurring ones that can't be fixed in a shift huddle.