Daily Standup
Also known as: daily scrum, standup meeting, morning check-in, async standup
A daily standup (also called a daily scrum in the Scrum framework) is a short daily team meeting designed to coordinate work and surface blockers.
Each participant briefly answers three questions: What did I do yesterday? What will I do today? Is anything blocking me? The format is intentionally time-boxed (typically 10-15 minutes) and should focus on coordination, not detailed problem-solving. Standups are a core ceremony in agile software development but have been adopted across many team types. They can be run synchronously (everyone on a call at the same time) or asynchronously (each person posts their standup in Slack or a tool like Geekbot).
Daily Standup, explained at three levels
At home
A daily standup is a short daily check-in meeting where each team member quickly shares three things: what they accomplished yesterday, what they're working on today, and whether anything is blocking their progress. The whole meeting should take 10-15 minutes. It's not a detailed status report -- it's a quick coordination moment to help the team stay aligned and catch blockers before they cause problems.
At work
Standups keep a team aligned without requiring long meetings. In one brief daily touchpoint, the team knows who is working on what, whether work is moving forward, and what help is needed. Blockers (things preventing someone from making progress) are surfaced immediately to the team, rather than sitting unnoticed for days. The format enforces brevity -- detailed problem-solving happens after the standup with only the relevant people.
At home
Standups fail when they become status reports rather than coordination meetings. The purpose is not for management to hear what everyone is doing -- it's for the team to coordinate among themselves and surface blockers quickly. Signs of a poorly run standup: people report to a manager rather than speaking to each other; discussions run over 15 minutes regularly; topics come up that aren't blockers for anyone; and participants see no value in attending. These symptoms indicate the format has drifted from its original purpose.
At work
Async standups in Slack (using Geekbot, DailyBot, or manual posting) allow distributed teams to share updates in their local morning rather than synchronizing on a global call time that is inconvenient for some. The standup bot prompts each team member at their local start time and posts their response in a shared channel. This format works well when team members are self-disciplined about updates and the culture supports reading and responding to async posts. It fails when people skim posts without reading them or when blockers go unresponded to for long periods.
At home
Walking the board (reviewing task progress on a sprint board or Kanban wall) is an alternative standup format where the focus is on the work in progress rather than what individuals are doing. Rather than 'I did X yesterday, I'll do Y today,' the team reviews each card on the board column by column, asking: 'Is this moving? What's needed to advance it? Is there a blocker?' This format keeps focus on the work's flow rather than individual busyness.
At work
Research on standup effectiveness is mixed: a 2016 study by Cohen et al. found that standups where participants stood rather than sat were shorter and resulted in equal decision quality. Research on meeting frequency (daily vs. less frequent) and its impact on team coordination and output shows context-dependent results -- high-interdependency teams benefit more from daily coordination than teams with more independent work streams. For knowledge work teams with long-horizon individual tasks (researchers, writers, solo technical contributors), daily standups provide minimal coordination value and the interruption cost may exceed the benefit.
Real-world examples
At home
Lena's three-person freelance team ran a quick 10-minute Zoom standup every morning. The structure was strict: 3 minutes each, only the three questions, all problem-solving happens after. The team caught a missed deadline risk on day 2 of a project when one person mentioned their blocker -- the client hadn't sent the required assets. Resolving it that day instead of day 5 saved the project schedule.
At work
Carlos managed a 12-person software team across two time zones. Synchronous standups at 9am ET (6am PT) were resented by the West Coast team. He switched to async standups via Geekbot -- each person posted at their local 9am. A bot aggregated all updates in one daily Slack post. He reviewed the compiled updates each morning, responded to blockers directly, and held a 30-minute weekly sync video call for anything requiring real-time discussion. The team preferred the new format and blocker response time actually improved.
Common confusions
- Many teams treat the daily standup as a meeting where problems are solved — The standup is for identifying problems (specifically blockers), not solving them. When someone mentions a blocker, the standup response is to note who will help and move on -- then that smaller group meets after the standup to resolve it. Solving problems during standup derails the format and makes it run long, causing the majority of participants who aren't involved in the problem to disengage or resent the meeting. 'Take it offline' is a standup facilitator's most important tool.
- Some assume daily standups must be synchronous (everyone on a call at the same time) — Standups originated as synchronous because the original teams were co-located. Async standup formats using Slack bots or written posts achieve the same coordination goals for distributed teams without requiring everyone to be on a call simultaneously. For teams spanning time zones, async standups often work better than synchronous standups with awkward call times, because each participant posts at their natural start of day when they're freshest.
For analysts
When a team's daily standups regularly run 30-45 minutes, the meeting has drifted from coordination to status reporting or problem-solving. This is a common failure mode that makes standups resented rather than valued. Recommend returning to the strict three-question format, setting a 15-minute hard stop (with a visible timer), and explicitly directing all problem-solving to post-standup sessions with only the relevant people. Most standup overruns are solvable with facilitation discipline, not tool changes.
History & origin
The daily standup is rooted in the Scrum framework, developed by Jeff Sutherland and Ken Schwaber in the early 1990s. The Scrum Guide formalized the 'Daily Scrum' as a 15-minute daily event for the development team. The name 'standup' (participants stand during the meeting to encourage brevity) was adopted from earlier practices in software development teams. Standups became ubiquitous in the agile adoption wave of the 2000s and 2010s. Async standup tools (Geekbot, DailyBot, Status Hero) emerged in the 2010s, allowing teams -- particularly distributed ones -- to run standups asynchronously in Slack or Teams. The format spread beyond software teams to marketing, operations, and leadership teams, sometimes losing its focus on three specific questions and becoming a general status meeting.