A daily production meeting is a 15-minute stand-up at the board, at the same time every day. It covers safety, yesterday's output and OEE, the top three stop causes, quality and today's plan, and ends with actions that each have an owner and a date.
What the meeting is for
The daily production meeting is a short stand-up at the line or at a board. The team looks at yesterday's numbers, picks the biggest problems and agrees who does what today.
It is not a status round and not a place to solve problems. It is a place to decide. Solving happens afterwards, at the machine, with the two or three people who need to be there.
A 15-minute agenda that works
Keep the same order every day. People learn the rhythm and come prepared. Here is a simple split.
| Minutes | Topic | What is covered |
|---|---|---|
| 0-2 | Safety | Any incident or near miss, any risk for today |
| 2-5 | Yesterday: output and OEE | Plan against actual, OEE for the line, in one number |
| 5-9 | Top 3 stop causes | Minutes lost per cause, from the log |
| 9-11 | Quality | Scrap, rework, holds |
| 11-13 | Today | Plan, changeovers, materials, people |
| 13-15 | Actions | Open actions: owner, date, status |
The times add up to 15 minutes. Cut a block rather than run over.
- Safety2 min
- Yesterday3 min
- Top 3 stop causes4 min
- Quality2 min
- Today2 min
- Actions2 min
Worked example: what the board shows
Example: a line has an ideal rate of 60 units a minute and a scheduled time of 450 minutes. Yesterday it made 18,000 good units.
= 18,000 ÷ 60 ÷ 450 = 300 ÷ 450 = 66.7%
The line stopped for 120 minutes in total. It ran for 330 minutes and made 18,810 units in that time, of which 18,000 were good. That gives the loss split below, as a share of the 450 scheduled minutes.
- OEE (good output)66.7%
- Stops26.7%
- Slow running3.7%
- Scrap and rework3.0%
The 120 stop minutes are the part the team can act on today. The log shows the top three causes:
| Cause | Minutes | Share of the 120 |
|---|---|---|
| Changeover | 45 | 37.5% |
| Film jam (many short stops) | 30 | 25.0% |
| Waiting for material | 25 | 20.8% |
| All other stops | 20 | 16.7% |
Top three causes are 100 of the 120 minutes. The meeting spends its time on these.
So the meeting asks three questions:
- Why did the changeover take 45 minutes?
- Where do the jams happen?
- Why did the material arrive late?
Each gets an owner and a date. Nothing else needs the room's time.
This is the same split you see in the OEE calculation. The method is the one in Overall Equipment Effectiveness (R. C. Hansen, 2001): OEE plus all the loss shares equals 100% of scheduled time.
Rules that keep it short
- Stand up, same time, same place. At the board, at the start of the day or just after the shift change.
- Data is ready before the meeting. Someone fills the board before the team arrives. The meeting is not the time to look for numbers.
- One problem, one owner, one date. An action without all three is dropped from the list.
- No problem solving in the room. If a topic needs more than two minutes, it goes to a "parking lot" and the right people meet after.
- Start on time, end on time. Late people miss it. That teaches everyone to be on time.
- Same numbers every day. Do not change what the board shows every week. Trends need a steady view.
Hansen advises using OEE at every level and posting it often, each shift if possible, and investigating any disturbance quickly (Overall Equipment Effectiveness (R. C. Hansen, 2001)). The daily meeting is where that habit lives.
Who comes
The shift or area supervisor leads. Operators or team leads from the line, a maintenance technician, and someone from quality and materials planning join.
Keep it to people who own an action. If a person has nothing to say for three days in a row, ask whether they need to be there.
Action log template
| # | Problem | Action | Owner | Due | Status |
|---|---|---|---|---|---|
| 1 | Changeover took 45 min | Video the next changeover, list steps | Team lead | Fri | Open |
| 2 | Film jam on labeller | Check guide wear, replace | Technician | Wed | Open |
| 3 | Material late 25 min | Move order trigger one hour earlier | Planner | Tue | Done |
Example rows. Review the whole log at the end of every meeting and close what is done.
Common mistakes
- The meeting turns into a status round where everyone reports and nothing is decided.
- Too many numbers. Output, OEE, three stop causes and scrap are enough.
- Actions are never reviewed, so they pile up and nobody believes the list.
- The loudest problem wins, not the biggest. Rank by minutes lost.
- The numbers are used to blame a crew. Then the log gets quieter, not the line.
Prepare the board before the meeting
The best meetings are short because the work was done earlier. Whoever owns the board spends about ten minutes before the meeting on these steps:
- Write yesterday's plan and actual output for each line.
- Work out OEE with the simple method: good units ÷ ideal rate ÷ scheduled time.
- Add up the stop minutes by cause from the log and mark the top three.
- Write the scrap and rework counts.
- Update the action log: close what is done, mark what is late.
If the numbers come from several sheets, this takes longer than the meeting. That is a sign to simplify the sheets or to collect the data from the machine. See OEE data collection methods.
What good looks like after a month
After four weeks you should see three things:
- People arrive on time and know the order.
- The same causes show up in the top three less often, because actions are closing.
- The action log has more "done" than "open".
If the same cause stays in the top three for four weeks, the action is not working. Do not repeat it. Send the cause to a root cause session and put the result on the board.
Hansen notes that what you measure drives behavior, and that people need information to improve. Showing the numbers every morning, where everyone can see them, gives them that information (Overall Equipment Effectiveness (R. C. Hansen, 2001)).
What to do next
Print the agenda, fill one board for one line, and run it for ten working days. Use the shift report software page if you want the numbers filled in for you. To go deeper on a cause, walk to the line with the gemba walk, and for tracking the causes read how to track downtime. The meeting is also the place where kaizen ideas get an owner.
The meeting is only as good as the numbers on the board. Fabrico is a light MES for OEE: stops, speed and counts come live from the machine, operators tag the cause at the line, and OEE is shown per line and shift, so the board is ready before the team arrives. See how Fabrico's light MES tracks OEE.
What people ask next
How long should a daily production meeting be?
Fifteen minutes is a good target for one line or area. If you need more, you are probably solving problems in the room. Move those to a parking lot and a follow-up with the right people.
What should be on the board?
Safety, yesterday's plan against actual, OEE, the top three stop causes in minutes, scrap, today's plan and the open actions. If you want the hourly view, see the hour-by-hour production board.
How is it different from a gemba walk?
The meeting is at a fixed time and looks at numbers. A gemba walk goes to the place where the work happens to see the process itself. Use the meeting to pick what to look at, and the walk to understand it.
What if we do not have good data yet?
Start with what you have: planned units, good units and a handwritten list of stops. Even rough numbers show the biggest cause. Improve the data as you go. See OEE data collection methods.
Daily or weekly: which is better?
Daily for the line team, because problems are fresh. Weekly for trends and for bigger projects. Many plants hold both, and the weekly one looks at the top causes from the seven daily logs.
Related guides: Plant Manager OEE KPIs: What to See Each Week · OEE Dashboard Examples: 6 Layouts That Work · Shop Floor Reporting: What to Report and When · MES Dashboard: What to Show and Who Acts on It