The daily huddle is a fifteen minute team check-in where everyone says what they’re doing and what’s in their way. It costs nothing and needs no software. Which is exactly why the founders who won’t run one are never really arguing about the fifteen minutes.
A CEO told me his people couldn’t huddle because they were scattered across sites, always on the road, never in the same building. Fair enough. So we set it for 8.45am, because it turned out most of them were already parked up outside, sitting in their cars, waiting for the day to start.
He rang me a week later. The place felt different, he said. People felt less on their own.
He’d had a dozen reasons why it couldn’t work. Every one of them was true. None of them mattered.
Of all the things I suggest to clients, this is still the one that gets the most pushback. It’ll break up the day. People are remote. We already have too many meetings. And I’ve come to read those objections the way a doctor reads a patient who won’t book the scan. The reasons are never the reason.
Why does it get harder somewhere around fifty people?
You built the thing on instinct. You knew everything because you were standing in the middle of everything. Decisions happened in corridors and over coffee and nobody needed a process because the whole company could hear each other.
Then somewhere between fifty and a hundred people, it stops working. Not dramatically. It just gets heavier. You’re the last to hear things. Two people spend a fortnight solving the same problem. And you can’t put your finger on when the wheels came off, because they didn’t. The thing that changed is that you can no longer hear the whole company at once.
The huddle is how you get that back. Not the headcount, you’re not getting that back, but the thing the small headcount gave you for free: everyone hearing what everyone else committed to, out loud, every morning. It’s a company small enough to hear itself, reassembled artificially, fifteen minutes at a time.
Where does the daily huddle come from?
John D. Rockefeller ate lunch with his senior people every single day. Not occasionally. Daily, for decades, while building the largest company on earth. Over that lunch he said the same things about what mattered, over and over, until they stopped being things he said and became things they believed.
Verne Harnish took that habit and made it a discipline in Mastering the Rockefeller Habits: a daily meeting, five to fifteen minutes, executive team first, then cascading down through the business. Every company running Scaling Up today is running a version of Rockefeller’s lunch.
Software teams got there by a different road and called it the stand-up, or the scrum. Same fifteen minutes, same three questions, different vocabulary. If your team already says stand-up, keep saying stand-up. Arguing about the word is a great way to avoid doing the thing.
Huddle around the outcome, not the org chart
Here’s where it usually goes wrong. Sales huddles with sales. Finance huddles with finance. Everyone reports upward to their manager, and the whole thing becomes a status meeting in a hurry.
At IT Lab we built them around the customer instead. A huddle was whoever was on the hook for delivering a specific result for a specific client, whatever box they sat in on the org chart. Engineer, account manager, finance, didn’t matter.
That one change alters what people bring. When you report to your manager, you’re accounting for your time. When you speak in front of the four people whose week depends on what you said yesterday, you’re making a promise. Nobody wants to be the one who turns up on Wednesday having quietly not done the thing.
What does a daily huddle look like across a whole business?
At 6 Degrees we cascaded it. Frontline huddled first. Then managers. Then directors. Then the exec team. Three huddles, ninety minutes, whole company.
What that bought was the thing every leadership team says it wants and almost none of them have. By the time the exec team sat down, whatever had gone wrong on the front line at eight that morning was in the room with them. Not in next month’s board pack. Not in a dashboard reporting last week. That morning, while we were in the middle of transforming the business and could still do something about it.
This is the structure I lay out in why your leadership team agreed with you and changed nothing: daily huddle, weekly one-to-one, monthly review, quarterly rhythm and annual planning. Each rhythm feeds the one above it. Skip the daily and every meeting above it is working from stale information, which is how you end up with a board reviewing a problem that was solved, or got worse, three weeks ago.
That’s the scaling up daily huddle. Not a status meeting bolted onto the quarter. The bottom rung of the whole cadence. Get the daily right and the quarterly conversation runs on fresh information, not a memory of what things were like three months ago.
I think of it like a personal trainer. Nobody hires a PT because they don’t know that exercise works. They hire one because someone has to show up, watch the form, and say “again” when the set isn’t finished. Your team would nod if you described the huddle to them. They already know it works. What’s missing is someone insisting they do it anyway. The huddle is the PT for your team’s accountability. Not a new idea. Just someone in the room who won’t let today’s rep get skipped.
When’s the best time to run a daily huddle?
Most people go first thing. But the time isn’t the point, the fixedness is. The HR business I mentioned went at 8.45 because that’s when people were already sitting in their cars. At Foundry Farm we do it twice, start and end of day, which means nothing spills over into tomorrow unnoticed.
Pick a time your people are already there. Then never move it.
What’s the actual purpose of a daily huddle?
The obvious answer is that it saves time. It does. Verne Harnish, who wrote the book this whole habit comes from, found that founders who swap their weekly one-to-ones for an eight-minute daily huddle get somewhere between five and ten times the return on the time spent: thirty-two minutes of daily huddles doing the work of four hours of one-on-ones. Fifteen minutes kills an hour of email per person too, because most email exists to work out what somebody else is doing.
But that’s not why it works.
It works because a commitment made out loud, in front of people you’ll face again in twenty-four hours, is a fundamentally different thing to a commitment made in a Slack thread. One has a witness. The other has a delete key. This is behaviour changing before mindset does, which is the only order it ever happens in. You don’t talk a team into being accountable. You build a habit that makes accountability the path of least resistance, and belief follows behaviour, months later, quietly.
I scaled two companies to £30m. Every week, I'll show you how.
“Every founder who’s told me huddles don’t work was running them wrong. I built Peer 1 Hosting’s UK operation from nothing to 120 people, and the huddle was one of the first habits I put in place. Fix the format and the results follow.”
Dominic Monkhouse, founder of Monkhouse & Company. Managing Director of Rackspace UK and Peer 1 Hosting. Has facilitated more than 200 leadership teams, from pre-revenue startups to companies turning over £3bn.
How do you run a daily huddle?
Start with good news. Anything, doesn’t have to be work. If people shrug at that, ask what they’re thankful for. It sounds soft and it isn’t: it’s the thing that makes people willing to say the hard part later, which is the whole reason you’re in the room.
Then round the room with three questions:
- What did I finish since yesterday?
- What am I doing today?
- What’s in my way?
Not a full task list. One or two things that actually move something.
That third question is where the value is, and it’s the one that dies first. Nobody wants to be the person who’s stuck. Which is precisely why you go first and say what you’re stuck on, before anyone else has to.
Morning Brew co-founder Alex Lieberman has written about five levels of how someone brings you a problem, crediting the idea to Steph Smith. Lieberman expects new hires at Level 4 from day one, moving to Level 5 as trust builds.
| Level | What it sounds like |
|---|---|
| 1 | “There’s a problem.” |
| 2 | Problem, plus the likely cause. |
| 3 | Problem, cause, and some possible solutions. |
| 4 | Problem, cause, options, and the one you’d pick. |
| 5 | Found it, fixed it, here’s the update. |
Most huddles never get past level one, because nobody’s ever told the team there’s anywhere else to go. Run it daily for long enough, in front of people who are visibly further up that ladder than you are, and the level one answers start to feel embarrassing on their own. Nobody has to lecture anyone about ownership. They just hear the gap, every morning, between “there’s a problem” and “I already fixed it.”
Fifteen minutes for eight people means about two minutes each. Use a timer. When someone’s time is up, cut them off mid-sentence, whatever they haven’t said can wait until tomorrow. It feels harsh the first week. People are still telling you about their weekend when the timer goes. Keep doing it and everyone gets faster, because they learn the rule is real. Skip it and the huddle drifts to thirty-five minutes, and within a month it’s dead, and everyone will tell you it’s because huddles don’t work.
Standing up, stand-ups, and scrums
Standing helps, because bodies that are standing want to stop standing, and that pressure keeps you honest. But it’s a trick to enforce brevity, not a principle. If your team sits and still finishes in fifteen, you’ve got a huddle. If they stand and take forty minutes, you’ve got a meeting with sore feet.
Who should be in a daily huddle?
Eight people, maximum. Past that, nobody gets any real airtime and the whole thing becomes a broadcast. Bigger teams split into smaller huddles and cascade, the way we did at 6 Degrees. Trying to run one huddle for thirty people isn’t ambitious, it’s just a badly attended meeting.
Making it stick past week three
Track the same handful of numbers daily, for individuals and for the company, in whatever holds your data. That thread is what connects a Tuesday morning to a quarterly goal. Without it, the huddle is fifteen minutes of talk that’s evaporated by lunch.
And get people thinking about tomorrow’s huddle as the last thing they do today. Where am I stuck, what moved, what am I grateful for. Five minutes at the end of the day is what makes the next morning sharp instead of a room full of people improvising.
Does this work outside software teams?
Sales, ops, finance, the leadership team. Anywhere the work depends on people knowing what everyone else is doing, which is everywhere.
The first question on Gallup’s Q12 employee engagement survey is whether people know what’s expected of them at work. Gallup’s own benchmark puts firms in the top quartile only when 75% of staff score that question five out of five. Most businesses aren’t close. A daily huddle answers that question every morning, for everybody, without waiting for a survey to tell you.
When I interviewed Horst Schulze, who built the Ritz-Carlton chain, he was blunt about how values actually get into a company. Take the things that make you better than the competition. Repeat them. Teach them. Repeat them again, until nobody can remember being told.
His teams did it in a daily huddle. Every day they read out one of their 24 service mantras, then singled out a team member who had embodied it the week before. Small ritual. Every day. That’s how a value stops being a poster.
He also gave every employee, down to the busboys, authority to spend $2,000 fixing a guest’s problem without asking anyone. That’s what it looks like when a company means it. Most don’t. Their people can tell.
Daily huddles are one of the first things I put into a leadership team, and they’re the cheap end of the work. If you want a team that runs the rhythm without you standing over it, that’s what executive leadership team coaching is for.
The same argument, twelve months apart
Now, in fairness, there’s a real objection here. Plenty of businesses run beautifully without a daily anything. Basecamp, Automattic, the deliberately asynchronous crowd. And they’re not wrong, they’ve built a whole culture around writing things down instead of saying them, hired specifically for it, and it works.
But look at what they have in common. None of them are a fifty person company that used to be a twelve person company and is trying to work out why it doesn’t feel the same. They designed for it from the start. You’re retrofitting. Different problem entirely.
Which brings me to the thing I actually wanted to say. The founder who won’t run a daily huddle is usually the same founder who dreads the annual appraisal. Both are avoiding the same thing: finding out whether people are actually doing what they said they’d do. The appraisal asks it once a year, badly, with a year of unsaid things stacked up behind it. The huddle asks it every morning, when the answer is small and cheap and nobody has to brace themselves.
I’d scrap the annual appraisal entirely and replace it with the rhythm, which I’ve argued at length in why annual appraisals are a waste of time. But you can’t run that argument if the daily habit isn’t there, because then the quarterly conversation has nothing real underneath it.
So it comes down to fifteen minutes. Everyone says what they’re doing and what’s in their way, and you find out whether the thing you said was going to happen is happening.
I feel strongly enough about this that it’s non-negotiable with every leadership team I coach. You’re either serious about your goals, in which case you’re running one, or you care less than you think you do. There isn’t a middle option.
If you don’t want to know that, be honest with yourself about why. It was never the fifteen minutes.
Frequently asked questions
What is a daily huddle?
A daily huddle is a fifteen minute team meeting where each person says what they finished yesterday, what they’re doing today, and what’s blocking them. That’s the huddle meaning in business, stripped of jargon: it’s the daily rhythm that keeps a growing business as connected and accountable as it was when it was small enough to hear itself.
How long should a daily huddle last?
Fifteen minutes. Not twenty, and definitely not “just this once, thirty.” The moment it starts overrunning, people begin arriving late and mentally checking out, and the whole habit is dead within a month. Someone in the room has to be willing to be rude about the clock, every single day, without exception.
Is a daily huddle the same as a stand-up or a scrum?
Functionally yes. Software teams tend to say stand-up or scrum, wider business teams tend to say huddle, but underneath the label it’s the same three questions, the same fifteen minutes, and the same discipline of showing up and saying it out loud. Use whichever word your team already uses and don’t waste energy arguing about the name.
Do people have to stand up?
No, but it helps, because a body that’s standing wants to stop standing, and that small discomfort keeps people brief. It’s a device for enforcing pace, not a rule to enforce for its own sake. Sit down if your team can genuinely still finish in fifteen minutes without drifting into a proper meeting.
How many people should be in one?
Eight at most. Beyond that nobody gets real airtime and the whole thing turns into a broadcast instead of a huddle. Split bigger teams into smaller huddles built around a customer or an outcome, then cascade the updates upward, frontline first, then managers, then directors, then the exec team.
What should you do next?
If this post has annoyed you slightly, good. The issue is probably not effort. It is design. The business is asking you to carry decisions, standards and exceptions that should now belong inside the team.
The goal is not to disappear. The goal is to build a company where your best work is not dragged back into every operational tangle.
That is the point. Scaling is not adding more people around the same bottleneck. It is rebuilding the business so the bottleneck is removed.
Four ways to take this further
- Book a call. If growth is now making the company slower, heavier or more dependent on you, I can help you decide whether the constraint is people, strategy, execution, cash or your role as founder. No obligation, no pitch. You will know quickly whether this is the right kind of help.
- Grab the book. F**k Plan B covers these principles in more depth, with the practical founder lessons behind customer obsession, honest communication, hiring, small teams and managers who coach.
- Watch: 5 founder mistakes that kill growth. Five founder bottlenecks that quietly stop growth between 50 and 100 people, and how to clear them.
- Subscribe to the newsletter. Get direct, practical thinking on scaling, founder bottlenecks, leadership rhythm and building a company that can run without you in every room.
Your move. Open Slack, Teams or your inbox. Find the decision that should not have come to you this week. That is where the scaling work starts.