Sergio D'Amico, CSSBB recently shared something that caught my attention because it is so easy to get wrong in manufacturing: "Your plant doesn’t need more meetings. It needs a cascade that turns 7:00 AM problems into same-day fixes." He followed that with a simple operating idea: problems rise, help returns, every morning.

That framing matters. Many plants are not short on meetings, they are short on decisions, ownership, and a reliable path for help to get back to the line quickly. Sergio D'Amico, CSSBB calls the mechanism a Daily Tier Meeting Cascade, and it is one of the most practical ways I know to convert daily noise into daily action without creating leadership micromanagement or frontline frustration.

The real problem is not communication, it is latency

When a defect, downtime, or staffing issue shows up at 7:00 AM, the outcome is usually determined by how fast the organization can do three things:

See the issue clearly (facts, not opinions)
Decide who owns the next step
Remove barriers that the frontline cannot remove alone

Without a structured cascade, issues drift into side conversations, rumors, or disconnected spreadsheets. People try to be helpful, but the system turns into a game of telephone. Sergio D'Amico, CSSBB summed up the better alternative with a core philosophy worth repeating:

"Information flows up. Support flows down."

That is the whole point of a tiered daily management system. It is not a meeting strategy. It is an execution strategy.

What is a Daily Tier Meeting Cascade?

Sergio D'Amico, CSSBB described a three-tier rhythm that happens every day with clear time boundaries:

Tier 1 at 07:00: Operators + Team Leader
Tier 2 at 08:30: Team Leaders + Production Manager
Tier 3 at 10:00: Managers + Plant Director

Each tier has a different job. Tier 1 detects and stabilizes. Tier 2 coordinates across teams and removes recurring friction. Tier 3 prioritizes systemic issues and allocates strategic support. And the most important piece is what happens after Tier 3: the decisions, resources, and clarity must flow back down quickly.

Tier 1 (07:00): Start where the work happens

Sergio D'Amico, CSSBB emphasizes a short huddle, not a long discussion. Ten minutes is enough if the structure is tight.

What Tier 1 should cover

He references SQDCP, a simple set of lenses that keep the conversation factual:

Safety
Quality
Delivery
Cost
People

At Tier 1, the goal is to answer: "Are we normal today? If not, what is the abnormality, and what is the immediate containment?"

What good looks like

Operators surface blockers immediately (missing material, a tool issue, an out-of-spec trend, a staffing gap)
The team leader captures it in a visible tracker (board or digital) with a clear owner
Anything solvable within the team is solved on the spot or queued with a due time

The key rule

If it cannot be solved here, it moves. Not as a complaint, but as a well-formed escalation with facts.

"Unresolved problems flow upward with clear ownership."

That last part matters. Escalation without ownership is just noise. Ownership without escalation is heroics.

Tier 2 (08:30): Turn isolated issues into coordinated action

At Tier 2, Sergio D'Amico, CSSBB points out three jobs: spot trends, assign cross-team resources, and remove systemic friction.

This is where many plants either overreact or underreact. A single downtime event might be a fluke. Three similar events across two lines is a pattern. Tier 2 is the pattern detector.

What Tier 2 should do differently than Tier 1

Look across cells and lines, not just one team
Identify shared constraints (maintenance capacity, changeover support, quality tech coverage)
Make tradeoffs explicit (who gets the mechanic first and why)

A practical way to run Tier 2 is to review Tier 1 escalations in a fixed order:

Safety first
Quality containment and disposition
Delivery risks for the shift
Cost or scrap signals that suggest a bigger issue
People constraints (training, absenteeism, coverage)

When Tier 2 cannot resolve an issue because it requires budget, policy changes, staffing decisions, or prioritization across departments, it escalates again, packaged for leadership.

Tier 3 (10:00): Prioritize systemic issues and unlock support

Sergio D'Amico, CSSBB describes Tier 3 as the place where managers and the plant director review compiled system issues, set priorities, and allocate strategic support.

This is where the cascade either builds trust or loses it.

The trust test: does help flow back down?

If Tier 3 becomes a status theater, frontline teams will stop escalating. If Tier 3 sends resources, clears roadblocks, and communicates decisions quickly, the entire culture changes.

Support flowing down can look like:

Approving overtime for maintenance to eliminate repeat downtime
Reprioritizing production to protect a customer shipment
Assigning engineering to permanently fix a chronic quality defect
Clarifying a standard that teams are interpreting differently
Funding a simple fixture or tool that removes a daily workaround

The frontline does not need leaders to solve every tactical problem. They need leaders to remove constraints the frontline cannot remove.

Why this structure beats micromanagement and silence

Sergio D'Amico, CSSBB called out two common failures that tiered meetings prevent:

Leaders micromanage tactical floor problems
Frontline teams feel unheard and stuck

I have seen both. When leaders skip the cascade and go directly to the floor for every issue, they unintentionally create two side effects: team leaders stop leading, and problems get solved in one-off ways that do not scale. On the other hand, when the floor has no reliable escalation path, people stop speaking up and start working around issues, which creates hidden factories, rework, and resentment.

A tiered cascade creates a healthier division of labor:

Tier 1 owns stability and immediate containment
Tier 2 owns coordination and recurring friction
Tier 3 owns priorities, resources, and systemic fixes

Making the cascade work in the real world

The concept is simple. The execution requires discipline. Here are the practical details I would add to Sergio D'Amico, CSSBB's model if you are implementing it.

1) Use a single visual tracker across tiers

The same issues should travel up and down without being retyped into three different formats. Whether it is a physical board photographed daily or a shared digital log, keep fields consistent:

Problem statement (observable facts)
Impact (safety risk, defect count, downtime minutes, schedule risk)
Owner (named person)
Next action and due time
Status (new, contained, in progress, escalated, closed)

2) Define escalation criteria so it is not emotional

Examples:

Any safety incident or near miss escalates immediately
Any quality escape risk escalates within the hour
Downtime over X minutes escalates to Tier 2
Any issue that repeats 3 times in a week escalates as "systemic" to Tier 3

3) Close the loop publicly

Nothing builds credibility like visible closure. When support flows back down, capture it:

"Decision made"
"Resource assigned"
"Countermeasure implemented"
"Standard updated and trained"

If a problem cannot be solved today, that is fine. But the next step must be clear today.

4) Protect the timeboxes

Tier 1 is ten minutes for a reason. If Tier 1 runs long, people stop coming. Deeper problem-solving belongs after the huddle with the right people.

What results should you expect?

Sergio D'Amico, CSSBB listed outcomes that consistently show up when the cascade is run well: faster resolution, clear ownership, alignment, same-day action, and trust.

I would add two more leading indicators to watch:

Fewer surprises at the end of the shift (because risks surfaced early)
Less firefighting behavior (because systemic causes get prioritized)

Or as Sergio D'Amico, CSSBB put it, high-performing plants do not rely on heroics. They rely on routine, discipline, and follow-through.

If your plant already has meetings, consider this question: do your meetings create a reliable path for problems to rise and for help to return the same day? If not, you do not need more meetings. You need a better cascade.

This blog post expands on a viral LinkedIn post by Sergio D'Amico, CSSBB, I talk about continuous improvement and organizational excellence to help small business owners create a workplace culture of profitability and growth.. View the original LinkedIn post →