The Daily Huddle: Why Five Minutes Matters More Than You Think

A five-minute stand-up meeting at the start of your day costs almost nothing and prevents the problems that destroy your day. Here is how to run one that actually works.

What a Daily Huddle Actually Is

A daily huddle is simple: everyone on the workshop floor gathers for five minutes at the start of the day. Not ten minutes. Not fifteen. Five. You talk through four things. Then you get to work.

That is it. No agenda documents. No formal meeting structure. Just five minutes of face-to-face conversation that stops the day’s problems before they happen.

Most workshops do not do this. The idea of stopping work to have a “meeting” feels like wasted time. Techs want to get into the bay. Admin wants to start processing jobs. Foremen want to get moving. So you skip it.

That is the mistake.

Why Workshops Skip the Huddle (And Suffer for It)

Without a huddle, here is what happens instead: you start the day assuming everyone knows what they are supposed to do. A customer rings about a job and nobody knows the status. A part does not arrive and your team does not find out until 11am when they are ready to fit it — so they swap jobs, which throws everything else out. A tech finishes their work at 2pm and has nothing to do because you have not told them what comes next.

By lunch, the day is already chaotic. By 4pm, you are having difficult conversations about priorities and delays. By close of business, you have a list of unfinished work and frustrated customers.

None of that had to happen. If you had spent five minutes talking it through at 7:45am, you would have known about the delayed part. You would have assigned work strategically. You would have flagged the customer inquiry and had an answer before they called.

The huddle does not add time to your day. It removes waste from it.

The Four Questions That Structure a Huddle

Do not wing it. Run the same four questions every day. Consistency is what makes it work.

Question 1: What is on today?

Walk through the day’s jobs. Which ones are already in the workshop? Which are coming in? Highlight the big ones — long jobs, difficult diagnostics, roadworthy inspections, anything that needs serious attention. Give your team the picture of the day so they can pace themselves.

Question 2: Any blockers?

A blocker is anything stopping work. Parts on back order. Awaiting customer approval for a quote. A vehicle waiting on diagnostic results. Tooling or equipment issues. Call them out now. If a part is not arriving until tomorrow and the job cannot proceed, do not let your tech find out at 10am when they are ready to start. Tell them now so they can move to something else.

Question 3: Who needs parts?

This one sounds admin-focused but it is critical. If you know upfront that three jobs need parts today, your admin can ring suppliers first thing. You avoid the 2pm scramble trying to source parts while techs are sitting idle waiting. And your team knows whether parts are arriving same-day or if they need to prioritise other work.

Question 4: Anything from yesterday?

Comebacks. Jobs that were supposed to be done but are not. Quality issues that have just been noticed. Customers ringing about something from the previous day. If there is unfinished business, it comes back into today’s schedule so nothing gets forgotten.

That is it. Four questions. Five minutes. Boom.

How the Huddle Prevents Problems Before They Happen

Think about your worst days. What usually goes wrong? A job that needs approval takes six hours because the customer did not respond to a call. A part does not arrive and you do not know until it is too late. Two jobs get behind schedule and cascade into the rest of the week. A quality issue is found at the end of the day instead of the start.

All of these are preventable with a huddle. When you know the bottlenecks upfront, you can work around them. When your team knows what is coming, they can sequence jobs better. When you flag customer approvals at the start of the day instead of the end, you have time to get them.

The huddle is not magic. It is just information flow. The problems exist whether you talk about them or not. But if you talk about them at 7:45am instead of discovering them at 3pm, you control your day instead of your day controlling you.

The Cultural Shift a Huddle Creates

Here is what happens after three weeks of running a daily huddle: your team starts thinking like a team instead of like individuals.

Instead of “I have my job for today and whatever happens happens,” they think “here is what we are all doing and how I fit into it.” When blockers come up, people offer to help. “I can grab that part from the supplier.” “I can start on the prep work for that job.” Suddenly you have people working toward the same goal.

Admin stops feeling like they are reacting to tech requests all day. They have a list upfront. Techs stop feeling like they are waiting for information to come to them. They have it at the start of the day. Managers stop fire-fighting from 9am to 5pm.

And something else happens: accountability becomes obvious. If a job does not get done, everyone knows it was assigned. If a blocker was mentioned and nobody dealt with it, it is harder to blame circumstances. The huddle creates transparency. And transparency creates responsibility.

How to Run It Without It Becoming a 30-Minute Meeting

The key is discipline. Set a timer. Five minutes. That is it.

Have one person (usually the foreman or a senior tech) run it. Not you, unless you are in the workshop every day. They know the work. They keep it tight. They move through the four questions fast.

Do not solve problems in the huddle. Flag them and move on. If a part needs sourcing, note it and the admin deals with it after. If a job needs approval, note it and the manager calls the customer after. The huddle is information sharing, not problem-solving.

Run it at the same time every day. 7:45am works well because it is just before the 8am start. It becomes habit. Your team shows up for it. They do not wonder if it is happening today.

And keep it standing if possible. Do not sit down. Standing meetings end faster. People do not get comfortable.

Real Examples of What the Huddle Catches

The discovery situation: A customer brings in a car for a roadworthy inspection. In the huddle, the foreman mentions it is arriving at 8:30am and the inspector needs to see it by 11am. Your admin immediately rings the customer: “We can get it done if you can pick it up by lunchtime, otherwise it will be Friday.” Customer agrees to lunchtime and the day is planned. Without the huddle, the car arrives at 8:30, gets diagnostic work started, and at 10:30 you realise you are not going to make the window. Now you have rushed work and an upset customer.

The supply chain save: A technician needs a gearbox for a major rebuild. It is ordered Monday. In Tuesday’s huddle, the question comes up: has the part been confirmed? Admin realises it has not. They ring the supplier, find out it is actually on back order for a week, and immediately contact the customer. The customer decides to source the part themselves. Without the huddle, the tech has been planning the week around getting that gearbox. When it does not show up, half their week is wasted.

The comeback prevention: A quality control tech mentions in the huddle: “That brake work from yesterday — I want to double-check the pads are seated properly before we call it done.” Foreman sends someone to verify. They find a pad that was not seated correctly. Caught before the customer picks up the car instead of after they hear a noise.

These are not rare situations. They happen weekly in most workshops. A five-minute huddle catches them.

Getting Started

Do not overthink it. Tomorrow morning, gather your team at 7:45am. Tell them you are running a five-minute huddle. Ask the four questions. Time it. Five minutes. Done. Then do it again the next day.

By the end of week one, your team will know the rhythm. By the end of week three, they will wonder how they ever worked without it. By the end of month one, you will wonder how you were running your business before.

A tiny investment in information flow prevents enormous amounts of chaos.