Skill Drill: Running Effective Meetings for Manufacturing

Direct Answer

This drill builds the skill of running a tight, decision-producing meeting on a manufacturing floor — a shift handoff, a production stand-up, a quality review, a continuous-improvement huddle — so the meeting ends with owned actions instead of restating problems everyone already knew.

A plant manager, value-stream lead, or shift supervisor runs it with a team of 4–12 in 45 minutes (compressible to 5, extendable to 60). The team walks away able to run a meeting against a fixed agenda, surface and rank issues, and assign every action an owner and a due date — built on the EOS Level 10 Meeting structure and the Amazon 6-pager discipline of writing before talking.

Why This Drill Matters in Manufacturing

Manufacturing meetings are where production time goes to die. A morning production meeting in a metal-fab or injection-molding plant runs 50 minutes, covers the same OEE shortfall it covered yesterday, and breaks up with no owner assigned to the downtime on press line 3. The Gemba walk turns into a standing complaint session.

The quality review re-litigates a customer reject without anyone writing down who closes the 8D. Tier 1, 2, and 3 huddles bleed into each other because nobody enforces the agenda or the clock.

The cost is concrete: a supervisor in a plant running 20 people at a loaded rate of roughly $45/hour burns about $750 in labor on a single bloated hour-long meeting — and that's before the cost of the decision that didn't get made, which shows up as a repeat reject or another shift of unplanned downtime.

The bottleneck isn't that people don't care about throughput, scrap, or safety. It's that the meeting has no structure that forces a problem to become an owned, dated action before the room breaks up.

Two named methodologies fix this. The EOS Level 10 Meeting (from Gino Wickman's *Traction*, EOS Worldwide) gives a fixed weekly agenda — segue, scorecard, rock review, headlines, then the heart of it: IDS (Identify, Discuss, Solve) on a prioritized issues list, ending with a to-do list and a rating.

The Amazon 6-pager discipline (Jeff Bezos's narrative-memo practice that replaced PowerPoint) gives the manufacturing analog: bring the data written down — the shift report, the Pareto of defects, the downtime log — and read it silently first, so the meeting argues about a decision, not about what happened.

We'll also use Lean daily management / Tiered huddles (the Toyota Production System tradition, codified by firms like the Lean Enterprise Institute) as the manufacturing frame the agenda lives inside.

What You'll Need (5 min prep)

• Group size: 4–12. This drill works best with the actual crew that meets together — a shift team, a value-stream team, a tier huddle group.
• Room setup: a table everyone can see, a visible timer (phone or kitchen timer projected), and a whiteboard or the team's existing tier board.
• Materials: print the Level 10 agenda card (Segue / Scorecard / Rock Review / Headlines / IDS / To-Dos / Rating). Print one real, recent one-page "shift report" with three or four genuine issues on it (downtime, a quality reject, a staffing gap, a maintenance backlog).
• Handouts: a blank to-do tracker with three columns — Action / Owner / Due.
• Leader prep: pick the real shift report you'll use. Decide who plays the meeting facilitator first (it should not always be you).

Round 1 — Diagnose a Bad Meeting (6 min)

Don't start by teaching the agenda. Start by naming the pain. Read this aloud:

"Think about our last production meeting. How long did it run, and how many decisions came out of it with a name and a date attached? If the honest answer is 'fifty minutes and zero,' that's normal — and that's what we're fixing. By the end of today every meeting we run ends with owned, dated actions or it doesn't end."

Put two columns on the board: "What our meetings do now" and "What a good meeting produces." Let the team fill the left column fast — re-hashing, no owners, runs long, same issue daily. Then introduce the two tools: the Level 10 agenda for structure, and the Amazon 6-pager rule — *read the data before you discuss it.*

What good looks like: the team admits, out loud, that their current meeting produces talk, not decisions. The contrast is visible on the board.

Round 2 — Read Before You Talk (7 min)

This is the Amazon move, translated to the floor. Hand out the real one-page shift report. Set the timer for 4 minutes of silent reading — no talking, everyone reads the downtime log, the defect Pareto, the staffing note. This feels strange the first time; that's the point.

Read this aloud before the silence:

"Bezos killed PowerPoint at Amazon because slides let people bluff. Everyone reads the memo in the room, in silence, first. We're doing the manufacturing version — read the shift report cold so when we talk, we argue about what to DO, not about what happened."

After 4 minutes, ask each person to silently write the single most important issue on the page. Then collect them. You now have a raw issues list — the input to IDS.

What good looks like: real silence, then a list of issues that's mostly consistent across the team — which tells you the data spoke clearly. Where they diverge, you've found the issue worth discussing first.

Round 3 — Run the Reps: IDS (15 min)

This is the heart of the Level 10 Meeting and the heart of the drill. Put the collected issues on the board. Run IDS out loud as a team, with a rotating facilitator:

• Identify: the team votes the issues list down to the top three by impact. Coach: "Identify the root issue, not the symptom. 'Line 3 ran 60% OEE' is a symptom. 'The changeover on line 3 has no standard work' might be the issue."
• Discuss: spend the discussion only on issue #1 first. Set a 4-minute timer per issue. The facilitator keeps the room on the actual problem and cuts re-hashing with one line: "We've identified it — what do we DO?"
• Solve: every issue closes with an entry on the Action / Owner / Due tracker. No owner, no due date, it's not solved.

Rotate the facilitator after each issue so three different people practice running the clock and forcing the solve. The leader coaches from the side, not the chair.

What good looks like: three issues become three rows on the tracker, each with a real name and a real date. Discussion on each issue does not exceed its timer. The facilitator successfully cuts at least one re-hash.

Round 4 — Pressure Test the Clock (9 min)

Now break the meeting on purpose so they learn to recover. Re-run one IDS cycle, but the leader (and a couple of planted teammates) deliberately do what real crews do — drift to a tangent ("well that reminds me, maintenance never…"), re-litigate yesterday's reject, or try to solve an issue with no data.

The facilitator's job is to use named recovery lines:

"That's a new issue — parking it on the list, back to this one." "We don't have the data to solve that here. Action: pull the downtime log by tomorrow, owner is ___." "We've discussed it. Decision or park it — clock's at one minute."

Give the room two "tangent" tokens to throw when someone drifts; the facilitator must catch it and redirect. This is where the discipline gets muscle memory.

What good looks like: the facilitator parks tangents instead of chasing them, converts a data-less argument into an action ("go get the number"), and brings the cycle in on time despite the noise.

Round 5 — Debrief & Lock It In (8 min)

Read the completed Action / Owner / Due tracker back to the room, out loud, name by name and date by date. That readout IS the deliverable — it proves the meeting produced decisions. Then ask the team two questions: "What's the standing agenda we'll use every day starting tomorrow?" and "Who keeps the timer?"

Agree on a meeting rating (the Level 10 close): everyone scores the meeting 1–10 on whether it produced owned actions. Anything under 8 gets one concrete fix named for next time.

What good looks like: a tracker with real owners and dates, an agreed standing agenda posted at the tier board, a named timekeeper, and a meeting rating with a fix if it's under 8.

Scaling It: 5-Minute, 30-Minute, and 60-Minute Versions

• 5-minute version (start of a real huddle): Skip the diagnosis. Hand out today's actual shift report, 2 minutes silent read, run IDS on the single biggest issue, assign one owner and one date, done. This becomes the permanent shape of the daily huddle.
• 30-minute version: Round 1 (diagnose), Round 2 (silent read), Round 3 (one full IDS round with rotation). Cut the pressure test. Two-minute debrief and rating.
• 60-minute version: Full sequence, plus a second pressure-test round and a clinic where every person facilitates one issue and gets 30 seconds of peer coaching. End by building the team's permanent agenda card and assigning the standing facilitator rotation.

Common Mistakes & Coaching Cues

• Solving the symptom, not the issue. Coach: "60% OEE is the symptom. Make them name the actual root before anyone proposes a fix."
• No silent read — straight to talking. Coach: skip the Amazon read step and the meeting will argue about what happened instead of what to do. Protect the silence.
• Leaving an issue without an owner or a date. Coach: "Action / Owner / Due — if any column is blank, it's not solved, keep the cycle open."
• The leader facilitates every time. Coach: rotate the chair so the skill spreads. A meeting that only works when one person runs it is a single point of failure.
• Letting discussion run past the timer. Coach: the clock is the tool that forces the solve. "Decision or park it" at one minute left.
• Re-hashing yesterday's issues. Coach: scorecard and headlines are for status; IDS is for new decisions. Catch the re-hash with "we covered that — what's the action?"

FAQ

Isn't a daily 30-minute meeting just more wasted time? Only if it produces talk. A meeting that reliably ends with three owned, dated actions pays for itself the first time it prevents a repeat reject or an hour of unplanned downtime. The drill is about output per minute, not eliminating the meeting.

My crew won't sit through silent reading — it feels corporate. Frame it as the floor version of reading a print before you run the job: you don't start cutting until you've read the drawing. Two to four minutes of reading the shift report cold is the same idea. After the first time, they see it shortens the talking.

How does this fit our existing Tier 1 / Tier 2 / Tier 3 huddles? The agenda and IDS slot directly into any tier. Tier 1 (line) runs a 5-minute version on one issue; Tier 2 (value stream) runs a 15-minute IDS; Tier 3 (plant) runs the full structure. Same skill, different altitude.

What if the biggest issue can't be solved in the meeting? Then the "solve" is an action to go get what's missing — pull the data, run the trial, escalate to maintenance — with an owner and a date. A meeting can't fix everything live, but it can always produce the next owned step.

Who should keep the timer and the tracker? Rotate the timer so it's not always the boss; the tracker should live on the visible tier board, owned by whoever facilitates that day. The point is the discipline outlives any one person.

How often should we re-run this drill? Run the full 45-minute version once to install the habit, then re-run it quarterly or whenever meetings start drifting long again. The daily 5-minute version is the meeting itself — that's the habit you're building.

Bottom Line

After this drill, the team can run a meeting against a fixed agenda, read the data before arguing about it, identify the real issue instead of the symptom, hold each discussion to the clock, and close every issue with an owner and a due date — then rate the meeting and fix it if it scored low.

Install it once with the full version, then run the 5-minute version every day and re-drill quarterly.

Sources

• EOS Level 10 Meeting — EOS Worldwide
• Traction (Gino Wickman) — Traction Library
• Amazon's 6-pager narrative memo — Jeff Bezos shareholder letter (2017)
• Lean daily management & tiered huddles — Lean Enterprise Institute
• HBR: How to Design an Agenda for an Effective Meeting
• HBR: Stop the Meeting Madness
• ATD — Association for Talent Development

*running effective meetings skill drill — a runnable team training exercise for manufacturing, with verbatim scripts, timing, and coaching cues. Effective meetings drill review, rating, and review 2027.*