Insights

What a daily huddle should show, and what it should not

A daily huddle is a short standing meeting at the start of the shift. Done well, it is the most useful few minutes of the day. Done badly, it is a status meeting nobody wants to attend.

The difference is almost always what the huddle shows.

What it should show

Keep it to a handful of things. The same ones every day, in the same order.

  • Yesterday against plan. What did we say we would do, and what did we do? One line per area.
  • The constraint. How did the pacing machine, cell or dock do? Was it ever starved or blocked?
  • Cost that moved. Overtime, rework, rush freight. Anything that cost money yesterday that the plan did not expect.
  • Today's plan and risks. What has to ship, what is short, who is out.
  • Owners and next steps. Every problem raised leaves the huddle with a name next to it.

That's it. If it doesn't fit on one board or one screen, it is too much.

What it should not show

A huddle is not a report-out. Leave these off:

  • Long lists of metrics. If nobody acts on a number, it does not belong on the board.
  • Old news. Last month's results belong in a monthly review, not the morning huddle.
  • Blame. The huddle exists to surface problems early. If people get punished for raising them, they will stop.
  • Long problem-solving. Name the problem, name the owner, and take the discussion somewhere else.

Keep it short, and keep it daily

The huddle works because of rhythm. Same time, same place, same board.

When it gets skipped "just this week," it fades fast. When it runs every day, problems show up while there is still time to act, not at month-end.

Short matters too. People protect a meeting that respects their time. They avoid one that doesn't.

The data has to be honest

A huddle is only as good as the numbers on the board. If the board says one thing and the floor knows another, people stop trusting it. Then the huddle turns into a show.

That is why the numbers should come from tools the team already uses, updated by the people who know the work. When someone says "that number is wrong," treat it as a gift. Fix the source, not just the board.

It also helps to have someone outside the daily rush check the data now and then. Small errors creep in. A regular check keeps them from adding up.

Who runs it

The owner should not run the daily huddle. The team should. A lead or operations manager runs it, and the owner joins when they can.

That is how you know the system works: it keeps going when the owner is on the road.

Start small

You don't need a perfect board on day one. Start with yesterday against plan, and the constraint. Add cost once those numbers are trusted. Adjust the board every few weeks, based on what the team actually uses.

The goal is not a beautiful board. The goal is a team that sees the day clearly and acts on it before it turns into next month's surprise.

Want help setting one up on your own tools? Book a floor walk.

Book a floor walk.

We walk your floor together and find the one constraint holding your margin back.