Most factories have management. The best factories have a management system.
The difference sounds semantic. It is not. Management — in the informal sense — happens everywhere. Leaders walk the floor. Problems get discussed. Actions get taken. But without a structured system connecting daily operational reality to strategic intent, management is reactive. It responds to what happened. A management system anticipates what is about to happen and creates the conditions for the right response.
The Daily Management System (DMS) is the operational architecture that makes this possible. It is the most consistently underinvested element of lean transformation — and the one that determines whether any other improvement sticks.
What a Daily Management System Actually Is
A DMS is a structured set of routines, visual controls, and escalation mechanisms that connect the work happening on the floor to the decisions that need to be made by leadership — daily, and in the right sequence.
At its core, a DMS answers four questions every day: Are we on plan? If not, why not? What are we doing about it? And is that response sufficient, or does it need escalating?
Simple questions. But answering them reliably, at every level of the organisation, every day, is surprisingly hard — and most factories cannot do it.
The Tiered Meeting Structure
The mechanism that makes a DMS work is a tiered meeting structure. Rather than a single daily operations meeting where everything gets discussed by everyone, a tiered structure creates short, focused conversations at each level of the organisation — each one feeding the next.
Tier 1 — the team level. This is the frontline. A 10–15 minute standing meeting at the start of each shift, at the work cell or production line. The team leader reviews yesterday’s performance against target, identifies today’s priorities, surfaces any safety concerns, and confirms that the team has what it needs to execute the plan. The output is clarity — every operator knows what they are doing today and why it matters.
The Tier 1 meeting does not solve problems. It surfaces them. Anything that cannot be resolved within the team’s authority is escalated — immediately, not at the end of the shift.
Tier 2 — the departmental level. This meeting happens slightly later, once the Tier 1s have run. The production manager or department head reviews performance across all teams, identifies cross-functional issues — maintenance, quality, materials, scheduling — and resolves anything that was escalated from Tier 1. Duration: 20–30 minutes, standing, at a visual management board that shows actual versus plan across the department.
The critical discipline at Tier 2 is that problems unresolved within the department’s authority get escalated to Tier 3 before the Tier 2 meeting ends. Not later. Before it ends.
Tier 3 — the plant or site level. This is the senior operations leadership meeting. It reviews plant-wide performance, addresses cross-departmental escalations from Tier 2, and makes the decisions that only leadership can make — resource reallocation, priority calls, customer commitments, capital approvals. Duration: 30–45 minutes. The agenda is driven by exceptions, not presentations.
In larger or more complex organisations, there may be a Tier 4 at divisional or regional level. The principle remains the same: each tier handles what it can, escalates what it cannot, and does so quickly enough that problems are resolved before they become crises.
Visual Management: The Foundation
The tiered meeting structure only works if there is reliable, visible information to discuss. This is what visual management provides.
A visual management board at each tier should show, at a glance, whether performance is on plan or not. It should be updated in real time — or as close to real time as the environment allows. It should require no interpretation: green is good, red is not, and the reason for red should be visible alongside the data.
The key metrics differ by tier. At Tier 1, the board typically shows hourly output versus target, quality issues, safety observations, and attendance. At Tier 2, it shows daily performance by team, key downtime events, material shortages, and open escalations. At Tier 3, it shows plant-wide KPIs, trending metrics, and the status of strategic improvement activities.
The discipline that matters most is this: the board is updated before the meeting, not during it. If the team is updating the board while standing around it, you do not have a management system. You have a slower version of email.
Escalation: The Nervous System of the DMS
The most important — and most commonly broken — element of a DMS is escalation.
Escalation is not failure. It is the mechanism by which the organisation learns that something needs senior attention and applies it before damage is done. In a healthy DMS culture, escalation is expected and fast. In a dysfunctional one, it is avoided — because people have learned that escalating problems attracts blame rather than support.
Building a culture where escalation is normalised requires consistent leadership behaviour. When a team leader escalates an issue and receives a rapid, supportive response, they escalate more readily next time. When they receive a lecture about why they should have solved it themselves, they stop escalating — and the problem that needed senior attention gets managed quietly at the wrong level until it becomes a crisis.
The escalation protocol should be explicit: what types of problems must be escalated to what tier, within what timeframe? A safety near-miss goes to Tier 3 immediately. A machine breakdown unresolved after two hours goes to Tier 2 within the hour. A customer delivery risk goes to Tier 3 before end of day. Written, visible, followed.
The Connection to SIOP
A DMS does not exist in isolation. Its purpose is to execute the plan that the SIOP process created.
Without a DMS, SIOP outputs are wishful thinking. The monthly plan is agreed, then immediately buffeted by daily operational reality with no structured mechanism to maintain alignment. By week three, the plan and reality have diverged so completely that the next SIOP cycle starts with a gap analysis rather than a refinement.
With a DMS, deviations from the SIOP plan are visible within hours. Escalation mechanisms ensure they receive appropriate attention. Mid-cycle corrections happen in days rather than weeks. The monthly SIOP meeting reviews actual performance against an agreed plan, rather than trying to reconstruct what happened and why.
SIOP sets the direction. The DMS executes it. Neither works without the other.
Why Most DMS Implementations Fail
The DMS is one of the most frequently attempted and least successfully sustained lean interventions. The reasons are predictable.
The meetings become presentations. The standing meeting turns into a sit-down review. The visual board becomes a slide deck. The conversation shifts from problem-solving to reporting. Senior leaders start attending Tier 1 meetings and turning them into Tier 3 conversations. The cadence collapses.
The boards stop being maintained. When data quality degrades, the meetings become discussions about the data rather than the performance. Trust in the system erodes. Within months, the boards are out of date and the meetings are cancelled.
Escalation is punished. Once or twice. Then it stops happening. Then the DMS is disconnected from real operational decisions and becomes ceremonial.
The antidote to all three is leadership consistency. The DMS reflects the management culture that surrounds it. If leadership treats it seriously, it works. If leadership treats it as a lean initiative that runs in the background, it does not.
The Test
Here is a simple test for whether your DMS is functioning.
Pick any day in the last month when something went significantly wrong — a customer miss, a quality escape, an unplanned downtime event. Now trace it back: at what point did the right level of leadership know about it? Hours? Days? Was it escalated through the tiered structure, or did someone call the plant manager directly at 4pm? Was it on the visual board before the morning meeting, or did it appear in the weekly report?
The answer tells you whether you have a management system or just management.
Adam
Leave a comment