How to Run a Weekly Standup: A Practical Guide
The weekly standup is the simplest meeting in management: each person says what they did, what they’re doing next, and what’s blocking them. Fifteen minutes, once a week, and everyone leaves knowing where the team stands. But simple doesn’t mean self-running. Without structure, the standup slides into status theatre, long monologues, side conversations, and the one blocker that actually matters buried at minute forty.
This guide shows how to use the Weekly Standup Notes Template to keep the standup short, honest, and useful. It’s written for team leads and managers who want the alignment without the drag.
When to Use This
Use a weekly standup when a team of three to twelve people works on overlapping tasks and needs regular coordination, software teams, marketing teams, operations teams, any group where one person’s delay becomes another person’s blocker.
The standup is a coordination meeting, not a problem-solving meeting. Its job is to surface information: progress, plans, and obstacles. If an issue needs more than two minutes of discussion, it gets taken offline with the relevant people, the standup just identifies it. Teams that respect this boundary finish in fifteen minutes. Teams that don’t finish when the calendar says so.
How to Fill It Out
Section 1: Meeting header. Date, time, facilitator, and attendees, including who was absent. If someone regularly misses the standup, that’s a signal: either the meeting isn’t valuable to them or their work isn’t visible to the team. Both are worth addressing.
Section 2: Last week’s completed work. For each person, one or two lines on what was finished. This isn’t a brag sheet, it’s the team’s shared memory. “Lena: completed the client onboarding checklist for the Hartley account; finalised the March newsletter draft.” Completed work tells the team what’s real and builds momentum. Keep it factual and brief; the standup is not the place for detailed demos.
Section 3: This week’s priorities. What each person plans to work on, in priority order. Two or three items each is right; a list of eight means nothing is actually the priority. Writing priorities down before the meeting is what separates a standup from an improv session, ask the team to fill in their section before they arrive, and the meeting becomes a review, not a composition exercise.
Section 4: Blockers and dependencies. The most valuable section. Each blocker needs a name, a description, and who can unblock it. “Blocked: waiting on legal’s review of the vendor contract (sent 9 April). Unblocker: Daniel in legal.” If a blocker has been open for two weeks, escalate it, a blocker that survives multiple standups without escalation is a standup that’s failing at its job.
Section 5: Key metrics or highlights. A few numbers that show the team’s trajectory: tickets closed, leads contacted, orders shipped. Choose metrics the team can influence and that change week to week. Static vanity metrics (“total website visitors since 2019”) don’t belong here.
Section 6: Parking lot. Topics raised during the standup that need real discussion get parked here with the names of the people who’ll discuss them and when. “Parking lot: office move timeline, Lena, Tomas, and the office manager, Thursday 2pm.” The parking lot is how you respect the issue without derailing the standup.
Common Mistakes
1. Turning updates into presentations. When “what I did last week” becomes a ten-minute narrative with backstory, the standup is over. Two minutes per person is the ceiling. If someone’s update genuinely needs more time, that’s a separate conversation, the standup just flags it.
2. Skipping the blockers. Teams are polite. People will describe their week without mentioning the thing that’s stuck, because admitting a blocker feels like admitting failure. The facilitator has to ask directly: “What’s blocking you?” Make it safe to answer honestly, a blocker raised early is a week saved.
3. No follow-up on last week’s blockers. If you record blockers but never check whether they were resolved, the team learns that blockers go into the notes and die there. Start each standup with last week’s blockers: resolved or still open? Still open means escalate.
4. The manager doing all the talking. A standup where the lead reports on everyone’s behalf is a broadcast, not a standup. Each person speaks for themselves. The facilitator’s job is timekeeping and drawing out the quiet blockers, not summarising the team’s week.
Who Needs to Sign Off
The team lead or manager facilitates and owns the notes. Nobody needs to formally approve weekly standup notes, they’re a working document, not a record. But the lead should scan them before they’re filed: if the priorities section shows the team drifting from the quarter’s goals, that’s a conversation to have this week, not next month.
How Often to Review and Update
The notes themselves are reviewed weekly, that’s the point. Every quarter, review whether the standup is still earning its slot: is it finishing in fifteen minutes? Are blockers getting resolved faster? If the standup has become a ritual people endure, change the format, rotate the facilitator, try a different day, or replace it with written updates for a month and see what’s lost. The template stays; the habit gets audited.
Download the free Weekly Standup Notes Template.