← Back to Field Notes

September 30, 2025 · The Bloomfield Team

How to Run a Production Meeting That Actually Produces

The production meeting at a 55-person job shop in Pennsylvania used to run 45 minutes every morning. Eight people sat around a conference table. The scheduler read the board. Each department head gave an update. The plant manager asked about two or three jobs by name. Everyone nodded. Nothing changed. The same late jobs were late the next morning.

The new plant manager cut it to 15 minutes, moved it to the shop floor, removed the chairs, and changed the format to three questions. Within 60 days, on-time delivery moved from 76% to 88%. The meeting was the single largest contributor to that improvement.

Why Most Production Meetings Fail

Production meetings fail because they report status instead of driving action. The scheduler tells everyone what is on the board today. That information is already visible to anyone who walks past the scheduling board or checks the ERP. Reciting it in a meeting adds no value.

The meeting's job is to identify the three to five things that will go wrong today if nobody intervenes, assign someone to intervene, and confirm the next morning that the intervention happened. Everything else is noise. The first hour of every shift determines whether the production plan survives contact with reality. The meeting is where that hour gets organized.

The 15-Minute Format

Three questions. One whiteboard. No chairs. The shift lead updates the board before the meeting starts.

Question 1: What ships this week, and is every job on track? The scheduler identifies every job with a ship date in the next five business days. Green means on track. Yellow means at risk. Red means behind. The meeting focuses only on yellows and reds. Green jobs do not need discussion.

Question 2: What is the single biggest risk to delivery this week? One risk. Named specifically. A machine down for maintenance. A material shipment delayed. A first-article inspection waiting for customer approval. An operator out sick on a critical cell. Name the risk, name the owner, and define the action that happens before end of day.

Question 3: Did yesterday's action items get completed? The plant manager reads the two or three action items from yesterday's meeting. Each one gets a yes or no. If no, the item escalates. If yes, it clears the board. This 30-second accountability check is the mechanism that turns meeting decisions into floor results.

What Changes on the Floor

When the production meeting drives action instead of reporting status, three things change.

Problems surface earlier. A machinist mentions during the meeting that a bore is running 0.0002" toward the upper limit on a 200-piece run. The quality manager flags it for mid-run inspection rather than discovering it at final inspection when 180 parts are already complete. That early intervention prevents a $12,000 scrap event. Without the meeting format that asks for risks, the machinist mentions it to his lead at lunch and the lead forgets to escalate it.

Handoffs improve. The meeting creates a daily checkpoint where operations, quality, shipping, and scheduling all hear the same priorities at the same time. When the scheduler says "Job 4271 needs to ship Thursday," the operations lead knows to prioritize it over the larger job that has three more weeks of lead time. Without the meeting, both jobs compete for the same machine based on queue position rather than ship date urgency.

Accountability becomes visible. When every action item from yesterday gets reviewed in front of the team, follow-through improves. Not because people are being policed, but because public commitment drives completion. The team sees that the meeting produces results, which makes them take the meeting seriously, which produces more results. The cycle reinforces itself.

What Does Not Belong in the Meeting

Detailed technical problem-solving. If a tooling issue requires a 20-minute discussion between the engineer and the machinist, that conversation happens after the meeting with the two people involved. The production meeting identifies the problem. The resolution happens separately.

Customer relationship updates. Sales conversations, contract negotiations, and new business pipeline belong in a separate weekly meeting. The production meeting is about what ships this week and what is at risk.

Long-term planning. Capital equipment discussions, hiring plans, and process improvement projects have their own forums. The production meeting operates on a one-week horizon. Anything beyond five business days is a planning conversation, not a production conversation.

The Data Foundation

The meeting only works if the data feeding it is current and accurate. The scheduler needs a real-time view of job status. The operations team needs to know which machines are running, which are down, and which are set up for the next job. Quality needs visibility into open NCRs and pending first-article approvals.

If that data requires 30 minutes of pre-meeting preparation to assemble from three different systems, the meeting will not sustain. The shops that run the most effective production meetings are the ones with production visibility systems that deliver current data without manual assembly. The meeting format creates the demand for better data. The data system makes the meeting format sustainable.

Run the meeting at the same time, in the same place, with the same format, every working day. Consistency is the mechanism. Within 30 days, the team will internalize the rhythm. Within 60 days, on-time delivery will reflect the discipline. Within 90 days, you will wonder how the operation ever ran without it.