By Andreas Pettersson, Founder, Leaders ADAPT
A team huddle is the cheapest meeting a manager can run and the one most often run badly. Done right it is ten minutes, standing, and the blockers that would have cost a day are gone by 9:15. Done wrong it is a 40 minute status meeting that happens to be daily, and the team learns to dread the sound of the calendar.
This page is the agenda, the four rules that hold it to ten minutes, how it differs from a stand up, and the four ways a huddle dies within a month.
I run Leaders ADAPT and wrote the 5-Minute Leader. The huddle below is the daily piece of the Rhythm Protocol in it, the one that replaced my own habit of being the person everybody waited for.
Quick answer: A team huddle is a daily, standing meeting of 10 to 15 minutes where each person answers three questions in thirty seconds: what did I commit to yesterday and did it happen, what is my one thing today, what is blocking me. The manager adds the one number the team is watching. Problems go to a parking lot and get solved after by the two people they concern.
What a huddle is for
A team huddle is a short daily meeting whose only job is to make every blocker visible before it costs a day, so that the manager clears it afterwards and the rest of the team keeps moving. It is not a status report, not a planning session and not a place to solve anything.
The reason it works is time. A blocker raised at 9:05 is cleared by 10. The same blocker raised in a weekly meeting on Thursday has already cost three days, and the person who was blocked has usually filled the time with something less important. Multiply by the number of people on the team and the huddle pays for itself every morning. The meeting cost calculator will show you what fifteen minutes of your team costs, and it is less than one unblocked day.
The 10 minute team huddle agenda
Same time every day. Standing, because sitting adds ten minutes. Each person, thirty seconds, three questions.
| Minute | Who | What |
|---|---|---|
| 0 to 1 | Manager | The one number the team is watching this week, and where it stands today |
| 1 to 8 | Each person, thirty seconds | Did yesterday's one thing happen. What is today's one thing. What is blocking me |
| 8 to 9 | Manager | Reads back the blockers and names who will clear each, with whom, after the huddle |
| 9 to 10 | Anyone | One sentence of recognition for something specific somebody did yesterday |
That is the whole thing. The manager's number at the top is what turns a round of updates into a team. Without it, people report to the manager. With it, people report to the number.
Boomerang check: does your work stay delegated, or does it come back?
Three questions, scored to the protocol that fixes the leak. The 5-Minute Leader is the four protocols, Delegation, 1:1, Accountability and Rhythm, written down so a manager can run them in about five minutes a day, so tasks stop boomeranging back half done.
Get the 5-Minute Leader or see what is inside the 5-Minute Leader.
The four rules that keep it at ten minutes
Thirty seconds each. The manager keeps time out loud, and "thirty seconds" said kindly on day one saves the huddle in month two.
No solving. The moment two people start working a problem, the other six are waiting. The manager says "parking lot" and the two of them take it after. The huddle is for surfacing, not fixing.
Same time, same place, no exceptions. Nine o'clock means nine o'clock, and it runs whether the manager is there or not. A huddle that moves to suit the manager's calendar becomes the manager's meeting, and the team stops owning it.
Blockers get an owner before the huddle ends. "I am waiting on finance" is a blocker. "Sam is calling finance at 9:30" is a blocker with an owner. The read back in minute eight is where the second sentence gets said.
Team huddle versus stand up versus weekly meeting
Managers who run all three usually run two of them badly, because the content leaks between them.
| Team huddle | Stand up | Weekly team meeting | |
|---|---|---|---|
| Cadence | Daily | Daily | Weekly |
| Length | 10 to 15 minutes | 15 minutes | 60 to 75 minutes |
| Where it comes from | Operations, retail, sales, healthcare | Software, Scrum | Everywhere |
| Job | Surface today's blockers | Surface today's blockers | Review the week's numbers, decide on the biggest issue |
| Solving allowed | No | No | Yes, one issue, in depth |
A huddle and a stand up are the same meeting with different names, and the stand up meeting page covers the software version. The weekly meeting is where the parking lot items that outlived the day get decided, with a scorecard and a deep dive, and the operating cadence page shows how the daily and the weekly fit together without overlap.
The four ways a huddle dies
Every huddle I have seen fail went one of four ways, and all four are the manager's doing.
It becomes a status report to the boss. The tell is that each person looks at the manager while speaking. Fix: the manager stands in the circle, not at the front, and the number on the board is what people report to.
It starts solving. One problem gets worked for eight minutes, the huddle runs to thirty, and by the second week attendance drops. Fix: parking lot, said out loud, every time, including when the manager is the one who wants to solve it.
It becomes optional. The manager cancels it twice for other meetings, then the team does. Fix: it runs without you. Rotate who leads it from week two.
It stops carrying a number. Without the one number at the top, the huddle is a round of "working on the same thing as yesterday", and people start to wonder why they are standing. Fix: pick one number the team can move this week, and open with it every day.
The huddle is the daily piece of a weekly system
A huddle on its own surfaces blockers. A huddle inside a rhythm, with a weekly meeting and a weekly 1:1, clears them and keeps them cleared. The Rhythm Protocol in The 5-Minute Leader is that system, the version I ran at a company of more than 150 people. Four protocols, Delegation, 1:1, Accountability and Rhythm, each about five minutes a day, so the work moves without the manager being the one who moves it.
The Rhythm Protocol holds the 15 minute stand up with its three questions and four rules, the weekly meeting agenda with its five sections and timings, and the four Rhythm Killers, the habits that quietly turn a good cadence back into a calendar full of status meetings.
One of the four Rhythm Killers is something most managers do in the first week of a new huddle and believe is helping.
Team huddle FAQ
What is a team huddle?
A team huddle is a short, standing, daily meeting, usually 10 to 15 minutes, where each person says what they are doing today and what is blocking them, and the manager clears the blockers after the meeting rather than inside it. It is the same thing as a stand up outside software teams, and it replaces the status email nobody reads.
What should be on a team huddle agenda?
Three items per person: the one thing they are doing today, whether yesterday's one thing happened, and what is blocking them. Then one line from the manager: the number the team is watching this week and where it stands. Anything that needs discussion goes to a parking lot and is handled by the two people it concerns after the huddle ends.
How long should a team huddle be?
Ten minutes for a team of up to eight, fifteen for larger. Thirty seconds per person is the rule, and the manager keeps time out loud. If it regularly runs past fifteen, something that belongs in the weekly meeting or a 1:1 is being done in the huddle, and the fix is to name it and move it, not to extend the huddle.
What is the difference between a team huddle and a stand up?
Nothing in the structure. A stand up is the software team name for the same meeting, with roots in Scrum. A huddle is the name used in operations, retail, healthcare, sales and most other teams. Both are short, daily, standing and built on the same three prompts. If your team is not building software, call it a huddle and run it the same way.
Should a team huddle be daily or weekly?
Daily, at the same time, if the work changes day to day and people depend on each other to get it done. If the work is weekly in shape, a weekly meeting is enough and a daily huddle becomes a ritual with nothing in it. The test is whether yesterday's blockers would still be worth hearing about on Friday. If not, daily.
What are some team huddle ideas to keep it fresh?
Do not. A huddle that needs ideas to stay interesting has lost its purpose, which is to surface blockers fast. The variation that helps is rotating who runs it, so the manager stops being the bottleneck and the team learns the format. Recognition of one specific thing someone did yesterday, in one sentence, is the only decoration a huddle needs.
Start it tomorrow at nine
Pick the number. Pick the time. Tell the team tonight that the team huddle starts tomorrow, ten minutes, standing, thirty seconds each, and that it runs with or without you. Run it for two weeks before you judge it. By the end of week one the blockers will be arriving at 9:05 instead of Thursday, and that is the whole return.
What is the one number your team could stand around tomorrow morning?


