Running an Effective Team Huddle

Why this matters

A daily huddle is the cheapest management tool a shop has. Done right, it surfaces problems before they reach the customer, keeps the whole crew pointed in the same direction, and runs in under fifteen minutes. Done wrong, it becomes a rambling status meeting that everyone dreads and you eventually cancel. The difference is structure. A good huddle is short, standing, same time every day, and built around a fixed set of questions so nobody wanders.

Step 1: Set a fixed time, place, and length

Pick a time tied to a natural anchor: just before trucks roll, or right after the first coffee. Same time, every working day. Variable timing kills attendance because nobody can plan around it.

• Keep it standing. People sit down and a fifteen-minute huddle becomes forty. Standing keeps it honest.
• Cap it hard. Ten to fifteen minutes for a crew under fifteen people. If a topic needs more, name it and take it offline with only the people involved.
• Phones down. A huddle full of people half-reading texts is theater.

Step 2: Run the same three questions every day

A huddle is not a status report, it is a coordination and obstacle-clearing tool. Run a fixed agenda so it is predictable and fast. Each person answers, in one or two sentences:

1. What are you on today? The headline jobs, not a play-by-play.
2. Anything in your way? Missing parts, an access problem, a permit not pulled, a customer who needs a callback before you arrive.
3. Anything the rest of us need to know? A heads-up that affects another tech, a tool that broke, a callback risk on yesterday's job.

The second question is the whole point. The huddle exists to catch blockers while there is still time to fix them today. If a tech says "I am waiting on a part for the Reyes install," that is your cue to solve it now, not at noon when the day is already lost.

Step 3: Capture blockers and assign them on the spot

A blocker named but not assigned is a blocker you will hear about again tomorrow. As each one surfaces:

• Name the owner: who is going to clear it.
• Name the by-when: today, before lunch, by end of day.
• Write it down where it is visible. A whiteboard, a shared list, the job record. Memory is not a system.

Do not solve the blocker in the huddle if it only involves two people. Say "Mike, you and I will sort the part after this," and move on. Solving a two-person problem in front of eight people wastes the other six.

Step 4: Keep it forward-looking, not a post-mortem

A huddle looks at today and tomorrow. It is not the place to dissect yesterday's bad job in detail. That is a separate, scheduled after-action review with only the people involved. If something went wrong yesterday, the huddle gets one line ("we had a callback on the Tan job, I will follow up with the crew separately") and nothing more. Dragging the whole crew through a post-mortem they were not part of is how huddles die.

Step 5: Handle the recurring failure modes

Every huddle drifts toward the same problems. Name them so you can correct them:

• One person dominates. Cut in politely: "Good, let us keep moving, we will dig into that after." Protect the clock.
• It turns into a gripe session. Gripes are fine if they name a fixable obstacle. "The scheduling is a mess" is a gripe. "Two of us got double-booked Thursday" is a blocker. Redirect vague complaints into specific asks.
• The same blocker appears every day. That is not a huddle problem, it is a process problem. Pull it out and fix the root cause separately.
• It stops being useful. Ask the crew what is and is not working. A huddle they helped shape is one they show up to.

Step 6: Close with the one thing

End by naming the single most important thing for the day, the one that matters most if everything else slips. "If we do nothing else today, the commercial job has to be inspection-ready by three." A clear top priority does more for a crew's day than a perfect schedule.

When to skip it

A huddle every day is the goal, but it is not a religion. On a day when the whole crew is solo on long jobs across town, a group message with the same three prompts can stand in. The format serves the coordination, not the other way around.

References

• See related: Meeting vs Message vs Walk-Over Decision Tree
• See related: After-Action Review: Learning From a Bad Job
• Trade-standard practice for daily field-service operations