Daily Standup Meeting: Agenda, Template, and the 15-Minute Rule

A daily standup is a 15-minute coordination meeting where a team syncs on what's moving, what's stuck, and what's at risk — not a status report for the manager. Below is a copy-paste agenda, the two formats that actually work, and what meeting researchers found about why standups quietly turn into status theater.

The Daily Standup Template (copy this)

Keep it to 15 minutes, same time every day, everyone standing or on camera. The point is to surface things the team needs to act on today — then get out.

The one rule that makes this work: the standup surfaces problems, it does not solve them. The moment two people start debugging, you've lost the other six.

Two Formats: Pick One

Format A — The three questions (classic)

Each person answers three things, in under 90 seconds:

1. What did I move yesterday?

2. What am I moving today?

3. What's blocking me?

Simple and familiar. The risk: it rewards sounding busy. People narrate their day instead of flagging what the team needs to know.

Format B — Walk the board (better for most teams)

Instead of going person by person, go work-item by work-item, starting with whatever is closest to shipping. Ask three questions of the board, not the people:

1. What's blocking this from moving?

2. Who's picking it up next?

3. Is anything stale — sitting untouched for days?

This keeps the focus on finishing work, not on performing effort. It also exposes the silent killer of most sprints: tickets that are "in progress" but haven't actually moved in three days.

What the Research Says About Why Standups Drift

Two meeting scientists, Nale Lehmann-Willenbrock and Simone Kauffeld, coded thousands of real team meetings statement by statement. They sorted what people say into buckets: procedural ("let's take that offline," "who owns this?"), solution-focused ("here's what we could try"), and counteractive — complaining, criticizing, looping on the same frustration.

Their finding is blunt and useful. Teams whose meetings were heavy on procedural and solution-focused statements were measurably more productive. Teams that fell into "complaining cycles" — one person vents, others pile on, nothing gets decided — performed worse, and the effect still showed up in company results years later.

A standup is short, so it rarely becomes a complaint spiral. Its version of the same trap is the rabbit hole: one blocker pulls two people into live problem-solving while everyone else waits. The talk-time collapses onto two voices, the meeting runs long, and the team learns that standup is optional.

What to do about it

Treat time-in-standup and talk-time balance as health signals, not trivia. A standup that keeps creeping past 15 minutes is almost always one that slid from coordination into problem-solving. When a blocker needs real discussion, name it, assign an owner, and park it: "Maria and Sam, stay after for two minutes on the API timeout." Then move on.

Do You Even Need a Daily Standup?

Daily is a default, not a law. The question isn't "should we do standups" — it's "how often does this team actually need to re-coordinate?"

A tightly coupled team shipping a shared feature benefits from daily syncs. A team of independent owners working parallel tracks often doesn't; for them, three live standups a week plus an async thread on the other days is enough, and it hands back two hours of focus time. Match the frequency to how interdependent the work really is.

Common Mistakes

Turning it into a status report for the manager

If everyone's answers are aimed at the lead instead of the team, it's not a standup — it's a daily performance review. People optimize for sounding productive. Face the answers at the work and the team, not at the boss.

Solving problems live

The fastest way to kill a standup is to let one blocker become a 10-minute debugging session. Surface, assign, park. Deep-dives happen after, with only the people who need to be there.

No follow-up on blockers

A blocker named every morning for four days straight isn't a standup item — it's a process failure. Track how long blockers stay open. If the same one keeps resurfacing, the standup isn't the fix; escalation is.

Running it out of habit

A daily meeting a team doesn't need is just a recurring tax on focus. If standups feel like going through the motions, cut the frequency and see what actually breaks.

How Spry Keeps Standups Honest

The standup is cheap on paper — 15 minutes — but it's daily, and daily recurring meetings are exactly where hidden time goes. Spry's calendar analytics show how much of each person's week is actually spent in recurring syncs, how that load compares across teams, and how much focus time is left around them. If your standups have quietly stretched to 30 minutes or multiplied into three overlapping syncs, it shows up in the data instead of staying a vague feeling. It's the visibility to make sure your most frequent meeting is still earning its place on the calendar.

Trying this with your team? I'd love to hear how it goes — DM me on LinkedIn.

FAQs

How long should a daily standup be?

Fifteen minutes is the cap for most teams, and shorter is fine. If it regularly runs longer, that's a signal the meeting has drifted into problem-solving — move those discussions to a parking-lot session with only the people involved.

What are the three standup questions?

The classic version: what did you move yesterday, what are you moving today, and what's blocking you. A stronger variant walks the board instead of the people, asking what's blocking each work item, who takes it next, and whether anything has gone stale.

Should standups be synchronous or async?

Synchronous when the team is tightly coupled and needs to react to each other in real time. Async works well for independent or distributed teams — a short written thread captures the same information without pulling everyone into the same 15 minutes.

Who should run the daily standup?

Ideally the team, not the manager. Rotating the facilitator keeps it from becoming a report up the chain and keeps ownership of the meeting with the people doing the work.

Do we need a standup every day?

Only if the work is interdependent enough to need daily re-coordination. Teams of independent owners often do better with two or three live standups a week plus async updates on the rest, which protects more deep-work time.