How to run a daily standup meeting

TL;DR: Your daily standup works when you focus on team coordination, not individual status reporting. Keep it to 15 minutes by walking the board right-to-left, shifting "what I did yesterday" updates to async channels like Slack, and parking complex technical discussions for follow-up syncs. For teams spanning time zones, async standups with a consistent template protect deep work without losing alignment. Granola captures standup transcripts so you stay present and focused on the conversation rather than typing, and Granola's standup template structures your enhanced notes consistently every time you run the meeting.

Most daily standups fail for one reason: teams treat them as individual status reports to the manager rather than coordination rituals for each other. When that happens, developers disengage long before their turn to speak. Copying the standup format without understanding its purpose turns a daily coordination ritual into a daily interruption, and developer velocity suffers as context-switching overhead compounds.

The fix is simpler than most teams expect. This playbook gives you a standup format that stays under 15 minutes, handles remote and async teams, and produces reliable documentation without adding admin overhead.

Driving team alignment in daily standup meetings

The Scrum Guide defines the Daily Scrum as a 15-minute event for the Developers of the Scrum Team, held at the same time and place every working day of the Sprint. That definition is deliberately narrow: it is a coordination event, not a reporting event.

The psychological difference matters. When team members feel they report to a manager, they focus on sounding productive. When they feel they coordinate with each other, they focus on what the team needs next. Scrum Alliance's guide to the Daily Scrum makes this distinction explicit: the Daily Scrum is an opportunity for self-managing team members to synchronize with one another, not for a manager to see who is on schedule and who is behind.

The practical implication: the facilitator's job is to direct conversation toward blockers and delivery flow, not to collect updates. Questions like "What does the team need to move this forward?" tend to surface blockers and dependencies more effectively than "What did you work on?"

Defining the essential standup agenda

Two formats dominate in practice. The first is the classic "Yesterday/Today/Blockers" round-robin. The second is "Walking the Board."

Walking the Board moves through each work item from right to left on the Kanban board, starting with items closest to completion and working back toward items just started. The team asks what each item needs to reach completion, rather than what each person did yesterday.

Walking the Board also surfaces invisible problems. Work that has no current owner can be harder to spot in a round-robin standup. On a visual board, it's easier to identify.

Scrum compliance note: The Daily Scrum is one of five official Scrum events and is mandatory under the Scrum framework. Developers can select whatever structure and techniques they want, as long as the meeting focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work. Format is flexible. The 15-minute limit is not.

Setting clear daily standup expectations

Before the first standup of a new sprint or with a new team, establish three ground rules:

1. Arrive prepared: Know your update before the meeting starts. Walking the board means knowing which items you own and whether anything is blocked.
2. Keep updates brief: One to two sentences per item. Save the detail for the parking lot.
3. Speak to the team: Updates are for teammates, not the facilitator. Direct language toward the people who can help.

Founder and executive protocol: When founders or executives attend the standup as observers, consider having them remain silent unless directly asked a question about a blocker. Their presence alone shifts team dynamics. Active participation during the standup often turns coordination into upward reporting. If leadership needs a status update, a separate sync after the standup with relevant team members can preserve the standup's focus.

Keep sensitive or confidential topics, including organizational changes, budget decisions, or personnel matters, in a separate private sync. Moving these topics out of the standup protects the 15-minute format and keeps the standup psychologically safe.

Adapting standups for non-engineering teams

The Scrum Guide permits any structure, as long as the meeting focuses on the Sprint Goal and produces an actionable plan. Discovery and research-heavy teams can adapt Walking the Board to their own pipeline:

• Walk hypothesis cards from "validated" back to "in progress," asking what each hypothesis needs to move forward: another customer interview, synthesis time, or a stakeholder decision.
• Replace "blockers" with "confidence gaps": what evidence would change your recommendation? This reframe surfaces research risks the way blockers surface delivery risks.
• Replace "next steps" with "learning goals": which assumption are you testing next? This keeps the standup focused on delivery of insight rather than delivery of features.

This mirrors how discovery call documentation captures pain points and next steps without losing participant context.

Standing or sitting for daily standups

Physical standing during a standup creates natural time pressure. People move toward the exit when the conversation lingers. For remote teams, that cue disappears, so a hard timer visible to everyone substitutes for it.

For hybrid teams where some members are in a room and others are on video, treat the meeting as fully remote. Use a shared digital board that all participants can see equally. Physical proximity in the room should not create an information advantage over remote participants.

Keep your daily standup meeting under 15 minutes

15-minute cap for daily standup meetings

The Scrum Guide sets 15 minutes as the hard limit. If your standup regularly runs past 15 minutes, that is a diagnostic signal, not just a scheduling inconvenience. It usually means status reporting has crept back into the format, blockers are being problem-solved live instead of deferred, or too many people are attending who do not need to be there.

Managing overruns in daily standups

When a team member starts diving into technical detail during the standup, the facilitator's job is to redirect quickly. Two phrases that work without breaking rapport:

• "Let's capture that and continue after the standup with the relevant people."
• "That sounds like a parking-lot item. Can you hold that thought for 10 minutes?"

Designate a timekeeper role and rotate it weekly. When someone other than the facilitator watches the clock, the facilitator can stay focused on the content of the conversation rather than its duration.

Parking lot tactics for brief standups

The parking lot, sometimes called "the 16th minute," is a structured space immediately after the standup for topics that need more time. Only the people directly involved stay for it. Everyone else leaves.

The key is capturing parking-lot items during the standup rather than after it. The facilitator writes each deferred topic in a shared doc as it comes up. At the 15-minute mark, you have a clear list, the right people stay, and the meeting ends on time for everyone else. Meeting minutes templates structured specifically for standups can help formalize this pattern.

Running efficient standups across time zones

Camera policy for remote standups

For short meetings, cameras help with attention and engagement, but camera fatigue is a real concern regardless of meeting length. A reasonable default is to encourage cameras while allowing exceptions without judgment: poor internet connections, early morning calls, and personal circumstances all warrant flexibility. What matters more than a camera mandate is active verbal participation from every attendee.

Scheduling global standups

For teams with partial overlap, the most reliable default is to treat async as the baseline and use sync time only when async is insufficient. Identify your overlap window and reserve it exclusively for blockers and decisions that require real-time input. Everything else becomes async.

For teams with no overlap, full async is the right default. A written update template sent at the start of each person's workday gives teammates the context they need before their own day begins.

Scaling standup meetings with async updates

Identifying async standup triggers

Move to async standups when any of these conditions apply:

• The team spans multiple time zones with minimal working-hours overlap.
• Focus time blocks are being interrupted by the standup on high-concentration days.
• The synchronous standup consistently produces low signal because the team does not need real-time coordination to align.

Structuring daily standup reports

A clear async template removes ambiguity and keeps updates consistent. This three-field format works for most engineering and product teams:

1. Focus: What you are working on today.
2. Blockers: What is preventing progress, and who can help.
3. Next: What you plan to pick up after current work completes.

Recording brief daily standup updates

Short video or voice updates preserve the conversational quality of a synchronous standup without requiring schedule coordination. Keep individual video updates brief to maintain engagement and make them easier for teammates to consume.

Documenting standups with Granola

Granola acts as an AI notepad during the live standup: it captures your device audio and transcribes the meeting in real time. The Slack integration (available on Business plans and above) then delivers structured output to async teammates: add the note to a Slack-enabled folder and the summary posts to the configured channel, so the live session feeds the async record without manual copy-paste. You jot rough notes during the standup, and Granola enhances them with transcript context once the meeting ends. Your notes stay in black, AI additions appear in gray, and you control what stays or gets deleted.

This human-in-the-loop approach means you control what gets documented and shared, while the AI fills in context from the transcript that you might have missed during the conversation.

Granola already includes a standup template that structures your enhanced notes consistently, so every session comes out in the same shape without post-meeting reformatting.

Granola Chat adds cross-meeting intelligence. After a few weeks of captured standups, you can ask "Which blockers have come up more than once this sprint?" and get an answer drawn from your standup history. That kind of pattern recognition is impossible to do manually across a month of daily meetings.

Transparency and consent

Granola also offers transparency features so participants know you are transcribing. The automated in-chat message posts a notification when Granola starts, and the watermark displays a visible indicator on your video throughout the call.

Identify and correct standup anti-patterns

Limit status reporting to async channels

The single highest-impact change most teams can make: move "what I did yesterday" to Slack before the standup starts. This frees the synchronous 15 minutes entirely for blockers, coordination decisions, and dependency surfacing.

When status reporting happens in writing, it also creates a searchable record. Teammates who missed the standup can catch up without interrupting someone else's flow. Meeting notes vs. meeting minutes covers how to distinguish between the documentation you need for async updates versus formal records.

Use separate syncs for complex issues

Technical deep-dives during the standup are the most common cause of overruns. When a problem requires more than a minute or two to explain, move it to a follow-up sync with only the relevant people. The facilitator's job is to recognize that threshold quickly and call it.

The parking lot is the mechanism. At the end of the standup, schedule follow-up syncs for parking-lot items with only the specific team members who need to be involved. A focused sync with two people solves problems that a whole-team standup never will.

Capping standup meetings at 15 minutes

A hard stop at 15 minutes, enforced by the timekeeper without exceptions, can change team behavior over time. People arrive more prepared. Updates become more concise. Blockers get surfaced earlier in the day rather than saved for the standup.

The first few hard stops feel uncomfortable. That discomfort is the mechanism working. When teams copy the standup format without understanding its purpose, the ritual becomes a daily interruption rather than a coordination tool. The 15-minute limit exists to protect the team's focus for the other seven hours of the day.

Pausing standups to protect deep work

On no-meeting days, increasingly common at companies managing developer velocity, pause the standup entirely. A 15-minute synchronous meeting still breaks a flow state even when it runs efficiently. On days where the team needs uninterrupted blocks, async updates through Slack replace the live meeting.

Standup health checklist

Use this checklist to audit your standup weekly:

• Meeting ends at or before the 15-minute mark without a hard cut
• Status updates happen in writing before the meeting, not during it
• The conversation focuses on blockers and work flow, not individual tasks
• Parking-lot items are captured and scheduled before the meeting ends
• Every attendee has a direct role in the team's current sprint work
• Action items are documented and assigned within 10 minutes of the meeting ending
• The board reflects current work accurately before the standup begins

Try Granola for free: download the Mac or Windows app, connect your calendar, and run your next standup to see how enhanced notes look in practice.

FAQs

Who must attend a daily standup?

Only the Developers are required attendees under the Scrum Guide. The Product Owner and Scrum Master may attend but are not required to. Observers and external stakeholders may join but should remain silent to protect the 15-minute timebox.

What should you say if you have no updates or blockers?

Use a standard phrase like "No updates, no blockers" and pass to the next person or item. This prevents pressure to invent minor tasks and keeps the meeting moving at pace.

How do you stop someone from talking too long in a standup?

The facilitator uses a short redirect: "Let's capture that for the parking lot and keep moving." A designated timekeeper role, rotated weekly, helps enforce the timebox without putting the full burden on the facilitator.

Is the daily standup mandatory in Scrum?

Yes. The Scrum Guide lists the Daily Scrum as one of five official Scrum events, all of which are mandatory within a Sprint. Format is flexible, but attendance for the Developers of the Scrum Team is not.

How do you capture action items from a standup without losing focus?

Granola captures your standup transcript in real time, so you can stay focused on the conversation and review your enhanced notes once the meeting ends. Granola's standup template structures the output consistently every time the meeting runs. The Slack integration (available on Business plans and above) posts the summary to your configured channel when you add the note to a Slack-enabled folder.

Can async standups fully replace synchronous standups?

For teams with significant timezone separation or strong deep-work requirements, yes. Async standups with a consistent three-field template (Focus, Blockers, Next) provide the coordination signal without scheduling overhead. For teams with regular blockers that require real-time negotiation, a weekly or twice-weekly synchronous standup combined with daily async updates often works better than going fully async.

Key terms glossary

Walking the board: A standup format where the team reviews tasks on the Kanban board from right to left, starting with items closest to completion and working back toward items earliest in progress, focusing on moving work forward rather than on individual updates.

Blocker: Any issue, dependency, or technical hurdle that prevents a team member from making progress on their assigned task.

Parking lot: A designated time immediately after the standup for interested parties to discuss complex topics deferred during the 15-minute alignment, attended only by relevant team members.

Async standup: A standup format where team members post daily updates in a written channel or record brief video clips instead of attending a live meeting.

Sprint Goal: The objective the Scrum Team commits to achieving during a Sprint, which the Daily Scrum must focus on as defined by the Scrum Guide.

Round-robin: A sequential standup format where each team member speaks in turn, commonly using the Yesterday/Today/Blockers structure.

Template: A built-in note structure in Granola for a specific meeting type. The standup template formats your enhanced notes consistently after each session, structured around what matters for a standup, without any manual setup.