By Andreas Pettersson, Founder, Leaders ADAPT
The stand up meeting was invented by software teams, and almost every guide to it still assumes you have a sprint, a backlog and a board full of tickets. Most teams do not. They have a sales pipeline, a warehouse, a clinic schedule or a month end close, and the stand up they copied from the engineering team has quietly become a 35 minute status meeting that happens to be daily.
This page is the stand up for everyone else. The same 15 minutes, the same three questions, the four rules that keep it short, and the two changes to make when nobody in the room ships code.
I run Leaders ADAPT and wrote the 5-Minute Leader. The 15 minute stand up in its Rhythm Protocol is this meeting, and it is the one that replaced me as the person everybody waited for in the morning.
Quick answer: A stand up meeting is a daily, 15 minute, standing meeting where each person answers three questions in thirty seconds: did yesterday's commitment happen, what is today's one thing, what is blocking me. No solving, blockers get an owner before the meeting ends, same time every day, and it runs without the manager. Outside software, add one number the team is watching at the top.
Where the stand up came from
A stand up meeting is a daily meeting of 15 minutes or less, held standing, in which each person states what they completed yesterday, what they will do today and what is blocking them. Blockers surface and get an owner within the day. The format comes from the daily scrum, the 15 minute meeting at the heart of Scrum, and was popularized by software teams through the 2000s.
Scrum framed the three questions around progress toward a sprint goal. That framing is the part that does not travel. A sales team has no sprint. An operations team has a week that looks like last week. The questions still work, but the thing they point at has to change.
The 15 minute stand up meeting agenda
| Minute | Who | What |
|---|---|---|
| 0 to 1 | Whoever is running it | The one number the team is watching this week, and where it stands this morning |
| 1 to 12 | Each person, thirty seconds | Did yesterday's one thing happen, yes or no. What is today's one thing. What is blocking me |
| 12 to 14 | Whoever is running it | Reads back every blocker with a name next to it: who clears it, with whom, when |
| 14 to 15 | Anyone | One sentence of recognition for something specific someone did yesterday |
Thirty seconds per person holds eight people inside 12 minutes with room to spare. Beyond ten people, split the team or the meeting.
The four rules
Thirty seconds, kept out loud. Not as a punishment. As a kindness to the other seven people who are standing.
No solving. The moment two people start working a problem, six people are waiting. "Parking lot" is the whole sentence, and the two of them take it the minute the stand up ends. This is the rule that breaks first and the one that, once broken, takes the meeting to 40 minutes within a fortnight.
Blockers get an owner before anyone leaves. "I am waiting on legal" is a sentence. "Priya is messaging legal at 9:20 and I will know by 11" is a blocker with an owner. The read back in minute 12 is where the second version gets said.
Same time, same place, runs without the manager. The manager being late or absent is not a reason to skip it. Rotate who runs it from the second week, and the stand up becomes the team's, which is the only way it survives.
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 two changes for teams that do not ship code
First, add the number. In Scrum the sprint goal was the thing everyone was reporting progress toward. Without it, a stand up becomes a round of updates addressed to the manager. The replacement is one number the team can move this week, said first every morning. Orders shipped, calls booked, tickets closed, cash collected, patients seen. The number turns a status round into a team, because people start reporting to it instead of to you.
Second, make yesterday a yes or no. The software version of "what did I do yesterday" turns into an inventory in a non software team, because the work is varied and everybody touched 12 things. The fix is that each person commits to one thing today, and tomorrow's first answer is whether it happened. Yes or no, then today's one thing. The inventory is gone and the commitment is public, which is the point.
Stand up versus huddle versus weekly meeting
| Stand up | Team huddle | Weekly meeting | |
|---|---|---|---|
| Origin | Scrum, software | Operations, sales, healthcare | Everywhere |
| Cadence | Daily | Daily | Weekly |
| Length | 15 minutes | 10 to 15 minutes | 60 to 75 minutes |
| Job | Surface blockers | Surface blockers | Review the scorecard, decide one issue in depth |
| Solving | No | No | Yes, one issue |
The first two columns are the same meeting. If your team is not building software, the team huddle page says the same things in the language your team already uses, and either name is fine. The third column is where the parking lot items that outlive the day get decided, and the operating cadence page shows how daily and weekly fit together without the content leaking between them. The meeting cost calculator will tell you what the 15 minutes costs, and it is less than the first blocker it clears.
The four ways a stand up dies
It becomes a report to the boss. The tell is eye contact: everyone looks at the manager. Fix: manager stands in the circle, and the number on the board is what people report to.
It starts solving. Fix: parking lot, out loud, every time, including when the manager is the one with the answer.
It becomes optional. The manager cancels it twice, the team cancels it the third time. Fix: it runs without you, and someone else runs it from week two.
Yesterday turns into an inventory. Fix: one commitment, yes or no.
These four are the daily version of what the Rhythm Protocol calls the Rhythm Killers, and they are all the manager's habits, not the team's.
The stand up is one piece of a rhythm
A stand up on its own surfaces blockers. A stand up inside a weekly 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 rhythm, the version I ran at a company of more than 150 people after watching every team copy the engineering stand up and run it for 40 minutes. Four protocols, Delegation, 1:1, Accountability and Rhythm, each run in about five minutes a day, so blockers clear without the manager clearing every one of them.
The Rhythm Protocol holds the 15 minute stand up with its three questions and four rules, the weekly meeting agenda with five timed sections, Wins, Priorities, Blockers, Deep Dive and Recognition, and the four Rhythm Killers.
The second of the four Rhythm Killers is something most managers believe makes the stand up more useful, and it is the reason theirs runs to 40 minutes.
Stand up meeting FAQ
What is a stand up meeting?
A stand up meeting is a short daily meeting, usually 15 minutes, held standing so it stays short, where each person says what they did yesterday, what they will do today and what is blocking them. It began in software teams as the daily scrum and now runs in operations, sales, retail and most other teams, often under the name huddle.
What does each person say in a stand up meeting?
What did I do yesterday, what will I do today, what is blocking me. The Scrum version framed them around progress toward a sprint goal. Outside software, the same three work with one change: yesterday is a yes or no against one named commitment, today is one named thing, and the blocker gets an owner before the meeting ends.
How long should a daily stand up be?
Fifteen minutes is the ceiling, and the Scrum guide that popularized the meeting set it there. Ten is better for a team of six or fewer. Thirty seconds per person is the working rule. A stand up that regularly runs past fifteen is doing a weekly meeting's work in the wrong slot, and the fix is to move the content, not to extend the time.
Should a stand up meeting really be standing?
Yes, where people share a room. Standing is the original reason for the length. Remote teams cannot stand together, so the substitute is a hard stop on the clock, cameras on, and a rule that nobody opens a document or a screen share. The point of standing was never posture. It was that nobody gets comfortable enough to start a discussion.
What should you not do in a stand up?
Solve problems, report to the manager, read a list of everything you touched, or let one person run long. Any of the four turns 15 minutes into 40. Problems go to a parking lot for the two people they concern. People report to the team and the number on the board. Yesterday is one commitment and whether it happened, not an inventory.
Can a stand up meeting be asynchronous?
It can, in a chat thread, and for a team spread across many time zones it may have to be. It loses the thing that makes a stand up work, which is that a blocker said out loud gets an owner in the same minute. If you run it in writing, add a rule: every blocker posted gets a named reply within an hour, or it is a diary.
Run it for ten working days
Pick the number. Pick the time. Tell the team tonight that the stand up meeting starts tomorrow, 15 minutes, standing, thirty seconds each, one commitment each, and that it runs whether you are there or not. Do not judge it before day ten. By then the blockers will be arriving at 9:05 instead of Thursday, and that is the entire return on 15 minutes.
What is the one number your team would stand around tomorrow morning?
