DMS
The Operating System
3
Components
Daily
Non-Negotiable Cadence
Act
Every Red Needs Action

What Is a Daily Management System?

A Daily Management System is the set of routines, visuals, and behaviors that connect daily shop floor activity to organizational goals. It is the operating system of a lean operation — the mechanism that ensures problems are surfaced, escalated, and solved every single day.

Without a DMS, information flows randomly: some problems get fixed, most do not, and leadership learns about issues days or weeks late. With a DMS, the entire operation runs on a predictable rhythm where the right people see the right data and take the right action at the right time.

The Three Components

1. Visual Boards

Physical or digital boards located where work happens, displaying real-time performance against plan. The board is the centerpiece of the DMS — it makes the invisible visible.

Board SectionWhat It ShowsUpdate Frequency
S — SafetyIncidents, near misses, safety observations, days since last incidentReal-time (incidents) / Daily (observations)
Q — QualityFPY, scrap/rework, customer complaints, open quality holdsShift / Daily
D — DeliveryHour-by-hour production vs. plan, schedule adherence, OEEHourly / Shift
C — CostOvertime, scrap cost, downtime cost, labor productivityDaily / Weekly
M — MoraleAttendance, recognition, improvement suggestions, training statusDaily / Weekly
ActionsOpen action items with owner, due date, status (red/yellow/green)Daily

The Board Is Not Decoration

If your board is beautifully formatted but no one looks at it, it is waste. The board earns its place by driving daily conversation and action. Test: Does the team gather at this board daily? Do actions get assigned here? Do metrics change daily? If any answer is no, simplify the board until the answer is yes.

2. Tier Meetings

Structured, time-boxed meetings at escalating levels of the organization. Each tier reviews its metrics, solves what it can, and escalates what it cannot to the next tier.

TierWhoWhenDurationPurpose
T1Team leader + operatorsStart of shift5 minSafety moment, quality alerts, today's plan, yesterday's issues
T2Supervisors + support functionsWithin 1 hr of shift start10-15 minReview all T1 escalations, assign cross-functional actions
T3Department managers + plant staffMid-morning15-20 minReview T2 escalations, plant-level issues, resource allocation
T4Plant manager + directorsWeekly30-45 minStrategic alignment, systemic issues, resource decisions
T1 (5 min)
escalate →
T2 (15 min)
escalate →
T3 (20 min)
escalate →
T4 (Weekly)
Problems flow UP through tiers. Actions and support flow DOWN. The system works when both directions are active.

3. Leader Standard Work

The scheduled routines that ensure leaders are on the floor, reviewing boards, following up on actions, and coaching their teams. Without leader standard work, the DMS depends on individual motivation instead of system discipline.

Running an Effective Tier Meeting

Start on time, every timeIf the meeting starts at 6:05 instead of 6:00, it sends a signal that the DMS is optional. Non-negotiable start time. If someone is late, start without them.
Stand, do not sitStand-up meetings are shorter, more focused, and more energetic. Meet at the board, not in a conference room. The data is on the wall, not in a laptop.
Follow the SQDCM sequenceSafety first, always. Then quality, delivery, cost, morale. Same order every day. Predictable structure prevents meandering discussions.
Red metrics get airtime, green metrics get a nodDo not spend 5 minutes celebrating green metrics. Acknowledge them ("safety is green, good") and spend the time on the reds. "Quality is red — FPY at 91% due to gasket defects on Line 2. Who owns the countermeasure?"
Every action gets an owner and a date"We will look into it" is not an action. "Maria will root cause the gasket defect by Thursday" is an action. Write it on the board. Follow up tomorrow.
Escalate, do not solve at the wrong levelT1 meetings solve T1 problems (operator-level, within the shift). If it needs a different department, budget, or authority — escalate to T2. Do not let T1 meetings turn into 30-minute problem-solving sessions.

The Escalation Path

If the Problem Is...Solve AtExample
Within the team's controlT1Operator needs tool sharpened, minor workstation adjustment
Needs another departmentT2Maintenance needed, material shortage, quality hold decision
Needs budget or policy changeT3Capital request, scheduling change, staffing decision
Systemic / strategicT4Capacity investment, supplier change, organizational redesign

Common DMS Failures

✅ DMS That Works
  • Meetings happen on time, every day, no exceptions
  • Boards are updated before the meeting, not during
  • Every red metric has an owner and countermeasure
  • Actions are followed up the next day
  • Leaders are at the board, not in the office
  • Escalation is expected, not punished
❌ DMS That Dies
  • Meetings skipped when "too busy" (which is when you need them most)
  • Boards are updated weekly or not at all
  • Red metrics with no assigned actions
  • Actions roll over for weeks without closure
  • Meeting happens in a conference room away from the floor
  • Problems escalated are ignored by the next tier

What a Good T1 Sounds Like

Supervisor (at board, 6:00 AM sharp): "Morning everyone. Safety: green, no incidents yesterday, watch for wet floors near wash station — facilities is fixing the drain today. Quality: yellow — FPY dropped to 93% on Line 2, we had 4 gasket defects. I need Tom and Sarah to do a quick 5 Why at first break. Delivery: green — we hit 98% schedule adherence yesterday, nice work. Today's plan: 480 units of Product A, changeover to B at 2 PM. Any questions? Good. Safe shift everyone."

Total time: 3 minutes.

🎯 Key Takeaway

A Daily Management System is the single most impactful operational improvement you can make. It does not require technology, consultants, or budget — it requires discipline. A board, a daily stand-up, a defined escalation path, and leader standard work to sustain it. When the DMS runs consistently, problems shrink, communication improves, and the entire operation becomes predictable.

Interactive Demo

Configure your tier meeting cascade. Set up Tier 1, 2, and 3 meetings and simulate issue escalation.

⚑
Try It Yourself
Tier Meeting Cascade
β–Ό
Configure your Tier 1/2/3 meetings, then simulate an issue escalating through the tiers. See how meeting frequency affects response time.
πŸ‘· Tier 1 β€” Team
Front-line team at the board
1x
0x3x
15 min
5 min45 min
8
212
πŸ“‹ Tier 2 β€” Supervisor
Supervisors review escalations
1x
0x3x
20 min
5 min45 min
5
212
🏭 Tier 3 β€” Plant
Leadership addresses systemic issues
1x
0x3x
30 min
5 min45 min
4
212
Escalation Flow
πŸ‘·
Team
1x/day, 15min
β†’
πŸ“‹
Supervisor
1x/day, 20min
β†’
🏭
Plant
1x/day, 30min
65 min
Daily Meeting Time
240 min
T1 Response
720 min
Full Escalation
Ready for the full knowledge check? Test your understanding with guided scenarios and data export.
PROTake the Pro Knowledge Check β†’
🏭
Free Process Modeler
Map your production flow, find bottlenecks & optimize staffing. No login required.
Try It Free →
Free forever · No credit card

Stop reading, start doing

Model your process flow, optimize staffing with Theory of Constraints, and track every shift — all in one platform. Set up in under 5 minutes.

Start Free → Try Process Modeler