What a daily standup is
A daily standup is a short recurring team meeting for synchronising work: what got done, what happens next and what is in the way. Two words carry the definition — short and recurring. Everything else is optional: it can run daily or weekly, in a room or on a call, with five people or fifteen.
One difference from a regular meeting matters more than the rest. A meeting exists to decide something. A standup exists to keep things from drifting apart. People report and assign here, they do not deliberate: the moment someone says "let's think through how we'll build this", the standup has quietly become a badly prepared meeting — no agenda, no materials, half the room unnecessary.
The same logic sets the guest list. You invite to a meeting whoever the decision depends on; you invite here whoever's work depends on a neighbour's work. If two people in the room share no dependencies, they have nothing to synchronise.
| Format | Question it answers | When you need it | Timing and size |
|---|---|---|---|
| Daily standup | Who is doing what today and what is stuck | Daily, when work is interlocked and the pace is fast | 10–15 min, up to 9 people |
| Weekly standup | Where the week landed and what we take next | Once a week, at the start of the cycle | 30–45 min, up to 12 people |
| Decision meeting | What are we deciding on this question | When a question needs preparation and a choice | 45–60 min, only those the decision depends on |
| Project status | Are we on schedule and where are the risks | At checkpoints, not on the calendar | 20–30 min, sponsor and leads |
| Retrospective | What to change in how we work | Every two to six weeks | 60 min, whole team |
| Written status | Same as a daily standup, without the meeting | Few dependencies, many time zones | 0 min of meeting, 3 min per person |
That last row is not an exotic option, and we will come back to it: half of all daily meetings exist purely because nobody proposed the written format.
Four formats, each with its own clock
One word covers four different meetings in different companies. Confusing them is expensive: they share neither the size, nor the length, nor what has to remain afterwards.
The daily standup
10–15 minutes, up to 9 people, same time every day. One person — one main task for the day and one blocker. Not a report on yesterday and not a defence of work done: the single purpose is that by 10:15 nobody starts what a colleague is already doing, and whoever is stuck walks away with the name of the person who will unblock them. Nine people at 90 seconds each is 13.5 minutes; the arithmetic is what caps the size.
The weekly standup
30–45 minutes, up to 12 people, Monday or the first working day. Here a horizon is allowed: what closed, what slips, what the one goal of the week is. It differs from the daily by permitting changes to the plan — which is exactly why it cannot run daily: a plan revised every morning is not a plan.
The cross-team standup
30 minutes, one representative per team. Its purpose is not reporting but seams: marketing is waiting on a landing page, support has not heard about the release, sales promised a customer something that does not exist yet. The size rule is strict — one voice per team: once "two more, just to stay in the loop" start arriving, the meeting grows to twenty people within a month and dies of its own weight.
The leadership standup
45–60 minutes, 5–8 people, weekly. The only format where discussion belongs: everyone at the table can decide on the spot. The split still applies — some questions take a minute, others move to a prepared meeting. A standup that turns into a three-hour deep dive costs five departments their week at once: each manager drops out of their own work and reschedules their own meetings.
If the content fits into one message in a shared channel without losing anything, then it was a message in a shared channel. A meeting earns its place when something changes on it: a plan, a priority, someone's task for today.
Standup questions: a ready list
The main reason these meetings stretch is open questions. "How's it going?", "Everything fine?", "Anything to discuss?" sound polite and mean nothing: they get answered either with "fine" (useless) or with a five-minute story (expensive). A good question constrains the answer in advance, in both shape and length.
1. WHAT I CLOSED since yesterday
Finished things only. "Worked on" is not an answer, it is not a result.
2. THE MAIN TASK for today
One. Not a list of seven — a list means the priority was never chosen.
3. WHAT IS BLOCKING ME and WHO UNBLOCKS IT
A person's name and what exactly is needed from them.
No blocker — say "clear" and pass the turn on.
1. THE WEEK'S GOAL met or not — one word: "yes" / "no" / "partly" 2. WHAT SLIPS and why — the reason in one sentence 3. ONE GOAL for next week — the one worth moving other things for 4. RISKS already visible — not "things might go wrong", something specific 5. WHAT I NEED from a neighbouring team — with a name and a date 6. WHAT MOVES OUT into its own discussion — topic, people, when The facilitator does not answer first: the team calibrates to their wording, and you will hear an echo of your own words instead of the actual state.
Almost everyone uses some variant of the first three questions. What matters is not their wording but that the list is closed: it makes drift visible — the person who starts on a fourth topic hears "that is not on the list" rather than "you are rambling".
Timing: why 15 minutes works and 45 does not
There is no magic in the number. Fifteen minutes works because you physically cannot deliberate in it — only report. The constraint is built into the format and does not have to be defended out loud each time. Forty-five minutes fails for the mirror-image reason: time expands to fit whatever fills it. Give a meeting 45 minutes and a 45-minute conversation will be found — and it will be indistinguishable from a useful one, because every remark in it is on topic.
It is worth costing this once. Nine people for 15 minutes is 2 hours 15 minutes of team time per day. Stretched to 45 minutes it becomes 6 hours 45 minutes — nearly a full working day, every day. Hence the criterion: the time is justified if every participant leaves with at least one change to their own plans.
Starting is a separate matter, and three rules do the work.
- Same time, start sharp. A floating start turns the meeting into ambient waiting: nobody begins deep work because "the standup is soon".
- No recaps for latecomers. One recap, and within two weeks everyone is late, because being late turned out to cost nothing.
- Go down a list, not "who wants to speak". The facilitator names the next person aloud. Without it, a third of the time goes to pauses and "shall I go then?".
How to cut a discussion without cutting the person
The facilitator's core skill is ending a conversation so that it does not read as "your topic does not matter". The mechanism is simple: the discussion needs an address to be moved to. Then you are not refusing, you are routing.
"This matters and it is not a fifteen-minute thing — Anna, Sergey, stay on after, will twenty minutes do?"
"Into the parking lot: billing integration. We come back Thursday, I will book it."
"Stop — we are solving the problem, and we only need the blocker named. Who unblocks you?"
"This concerns two of the eight. Everyone else is free, you two — five more minutes."
The essential part of every phrase is a name and a time. "Let's discuss it later" does not work: it is a polite refusal, and within a month people stop raising things at all.
The first standup: agree on the rules out loud
The first standup sets the format for months, so spend its opening not on work but on a contract: why we gather, how long it takes, what we don't do here, what remains afterwards. Three points, two minutes. Without it the team invents the rules itself — usually in the direction of reporting to a manager, the most familiar shape a recurring meeting has.
And set a review date immediately: three weeks, after which you honestly decide — keep, change the format, or drop it. A recurring meeting without a review date runs for years on inertia: somebody introduced it once, and nobody feels entitled to cancel it.
What to do with the outcome
A meeting after which nothing is written down is spent time, however lively the conversation was. Two days later participants remember different things, and arguing about who promised what costs more than writing it down. A full formal record is not the answer either: fifteen minutes do not deserve a two-page document, and nobody will keep producing one.
Three lines are enough.
DECISIONS
· Release moves to Thursday — the data migration is not ready
TASKS (owner and date are mandatory)
· Sergey — verify the migration on a database copy, by Wednesday 12:00
· Anna — warn support about the move, today
BLOCKED
· Dima is waiting on access from security — I escalate, by end of day
The value of those three lines is not the archive but the checkability: the first item of the next standup is "what from yesterday's list is closed". Without that check a daily call degenerates into reading aloud and stops affecting the work.
For heavier formats — leadership, a review with a client — a proper record of decisions is worth keeping: how sensible meeting minutes are built, and why a task list with an owner and a date beats a retelling, we covered in the piece on action items after a meeting.
Remote standups
The remote format breaks somewhere other than expected: connection and cameras are not the problem. What disappears are the non-verbal cues for whose turn it is, so people either talk over each other or stay silent out of politeness.
- Hold 10–12 minutes instead of 15. Switching between speakers costs more remotely: the pause, the "can you hear me", the audio lag.
- The facilitator names the next person aloud and announces the order in advance. It is the only thing that replaces a glance across the table.
- Links, numbers and names go into the call chat. Nobody transcribes a dictated document address correctly.
- Screen sharing belongs outside the standup. The moment sharing starts, the meeting turns from synchronisation into a review, and reviews are not fifteen minutes.
- Different time zones are a reason to switch to written status. A call at 7 a.m. in somebody's time zone works right up until their first holiday.
When you do not need a standup at all
Four signs that a recurring meeting should be cancelled rather than improved.
- One person speaks 80% of the time. That is not a standup, it is a broadcast with a voice. Broadcasts have a written form and it is cheaper.
- In a month, no item changed anyone's plans. Synchronisation without consequences is a report, and reports can be read with the eyes.
- People prepare for it. If someone spends twenty minutes preparing for a fifteen-minute meeting, you are paying twice.
- Participants share no dependencies. Five people on five independent tasks have nothing to coordinate except access to you.
The replacement is an asynchronous status: a short message in a shared channel before an agreed time, following the same closed list of questions. It wins on three counts: no simultaneous presence, one minute to read instead of fifteen, and it stays as text you can search. It loses on one, and it matters: tone is invisible — you will not catch "everything's fine" from someone for whom nothing is fine. A sensible compromise is written status daily and one live meeting a week.
Where Whisperer fits
Even with a closed question list and hard timing, manual work remains: somebody has to listen, remember and write down those three lines. In a short meeting that lands on the facilitator — and capture is the first thing to fall away, because running a discussion and recording it at the same time is not possible.
Whisperer is an AI workspace where meetings, tasks, documents and knowledge live in one system. For short recurring meetings it looks like this:
- A live transcript of the call. Recognition runs in real time, during the conversation — by the end of the meeting the text already exists, with nothing to wait for.
- Speaker labelling. Two independent audio streams — your microphone and system audio — are handled separately, so the transcript shows who said what. Here that is essential: a promise without a name is useless.
- Tasks and decisions do not get lost. The breakdown pulls out commitments and decisions with a quote from the conversation, and tasks reach the tracker as suggestions — with an owner and a date that a human confirms.
- Search across past calls. "What did Sergey say about the migration last week" becomes a question to the meeting history rather than to someone's memory.
- Real-time speech translation — if the team is distributed and the call runs in a language some participants find heavy going.
- The Leo agent with tools and actions: draft the summary, find open promises, assemble the picture of the week.
How this class of tools works in general, and where it gets things wrong, is covered in the reference piece on AI meeting assistants.
The limits, stated up front. Whisperer works on a live call: you cannot upload a finished audio or video file — recognition is streaming only, during the conversation. A remote standup is entirely its scenario; a standup in a room with no call is not, because there is no second audio stream and speaker labelling will not work. There are macOS and Windows clients plus a web account; the free tier is 60 minutes.
Frequently asked questions
How long should a daily standup be?
Ten to fifteen minutes with up to nine people: that is 90 seconds per participant plus a minute for the facilitator. Weekly — 30 to 45 minutes. A leadership standup can run to an hour, because decisions are allowed there. If a daily meeting regularly takes more than twenty minutes, the problem is not the clock but that people are deliberating instead of synchronising.
What is the difference between a standup and a meeting?
Purpose. A meeting exists to reach a decision: it has an agenda, materials and a narrow set of people the decision depends on. A standup exists to align work: short, recurring, attended by those whose tasks interlock. Discussion during a standup is a sign that somebody failed to schedule a meeting in time.
What questions should you ask in a standup?
Closed ones, identical for everyone: what I closed since yesterday, my main task for today, what is blocking me and who unblocks it. Avoid open ones like "how's it going" and "anything to discuss" — they either carry no information or turn into a five-minute story. Ready-made lists are above in the article.
How do you run a standup remotely?
Cut it to 10–12 minutes, announce the speaking order in advance and name the next person aloud — there is no non-verbal queue online. Put links and numbers in the call chat and move screen sharing outside the meeting. If participants sit in different time zones, replacing the daily call with a written status is the honest answer.
What time of day is best for a standup?
Early in the working day, but not in its first minute: people need time to open tasks and mail. A practical option is 30–60 minutes after the team typically starts. The hour matters less than the consistency: a floating time turns the meeting into ambient waiting, and nobody commits to deep work.
How do you run the first standup?
Start with the contract: why we gather, how long it runs, what we do not do here, what remains at the end. Two minutes on rules, then straight into the question list. And set a review three weeks out: a format with no review date runs for years on inertia.
Does a standup have to happen every day?
Only if the team shares dependencies and moves fast: releases, sales, support, operations. When people run independent tasks, a daily meeting gives them nothing new and a weekly one is enough. The test is simple: over the past month, did anyone's plans change because of it? If not, it is time to stop.
The bottom line
A standup costs exactly the number of people present multiplied by its length — it is the one meeting whose price is visible immediately. The formula is not complicated: a closed list of questions, hard timing, discussions moved out with names and times, and three lines at the end with decisions, tasks and blockers.
The easiest way to test the format is on your next call: create an account — 60 free minutes a month — turn on the transcript and compare two lists: the one you write from memory right afterwards, and the one assembled from the conversation. The gap between them is what the team loses every day.