Standup is not a status report. It’s a daily alignment check. The goal is to make sure the team is focused on the same thing and to surface anything that’s getting in the way.
If your standup feels like everyone is taking turns reading their to-do list to a manager, something is broken. A good standup is short, focused, and ends with the team more aligned than they were five minutes ago.
When you need this#
- People are working on the wrong things, or on things that were quietly deprioritized.
- Blockers sit unresolved for days because nobody knew about them.
- Stakeholders or the team lead keep pinging individuals for status updates throughout the day.
- The team feels disconnected, especially on remote teams where there’s no hallway chatter to fill the gaps.
Once a team adopts standup, a subtle habit can form. Someone finishes a ticket, hits a blocker, or makes a decision that affects the team, but instead of sharing it right away they think “I’ll just mention it in standup tomorrow.” Nobody decides to do this. It just happens organically. The mere existence of a daily sync gives people a reason to wait, and waiting feels reasonable because “there’s a meeting for that.” The standup becomes a reason to delay communication instead of improving it.
This directly undermines the work you’re doing to keep the project board reflecting reality. If someone finishes a ticket at 2pm but doesn’t update the board or tell anyone until standup the next morning, the board is lying for 18 hours. Multiply that across the team and you’ve got a board that’s always a day behind.
Standup is for alignment and blockers, not for breaking news. Updates to the board and quick Slack messages should happen in real time. If someone’s standup update is always “I already posted this in Slack yesterday,” that’s a good sign, not a bad one.
Who should be there?#
At startups, this can be company-wide. At larger companies it should be focused on the people building the thing, plus the team lead. If someone is in the standup but never speaks or never gets value from it, they probably shouldn’t be there. Keep the group tight.
The format#
1. Restate the goal#
Every standup opens with the same thing: the goal for the week.
(As a reminder,) the goal(s) for this week are: ____
This should not change day to day. Repeating it is the point. It’s a forcing function to keep the team focused as a group, especially on remote teams where it’s easy to drift into solo mode.
If the goal changed since yesterday, say so explicitly and explain why. Don’t just quietly swap it out.
2. Individual updates#
Each person answers three questions:
- Anything notable to share from yesterday?
- What are you working on today?
- Any blockers?
A couple of things to keep in mind:
“Anything notable from yesterday” is often nothing. That’s fine. Don’t force people to narrate their whole day. If they made progress on their ticket and nothing unexpected happened, a quick “nothing to add, still on the same ticket” is a perfectly good update. The goal is to surface surprises, not to prove you were productive.
Blockers are the most important part. A blocker is anything preventing someone from making progress: waiting on input from another person, waiting on a PR review, a decision that hasn’t been made, time off that’s eating into their capacity. When someone raises a blocker, the team lead’s job is to make sure it gets resolved today, not “soon.”
3. Wrap up#
Look at the board together. Adjust any assignments to better align with the week’s goal. If someone finished their ticket, make sure they know what to pick up next.
This is also the moment to catch WIP limit violations. If three tickets are “In Progress” on a team of four, ask why.
Common problems#
Standup takes too long. It should be under 10 minutes for a team of 4-6 people. If it’s running longer, people are either giving too much detail, having side conversations, or problem-solving in the standup itself. Side conversations should be taken offline: “let’s sync on that after standup.”
Nobody mentions blockers. This usually means people don’t feel safe raising them, or they’ve learned that raising a blocker doesn’t lead to action. If blockers consistently go unresolved, people stop mentioning them. The team lead needs to follow through visibly.
The goal never changes. If the weekly goal is the same for three weeks straight, it’s either too vague (“make progress on the project”) or the team is stuck and not talking about it.
People skip standup regularly. On remote teams this is a signal that standup isn’t providing value. Before mandating attendance, ask why people are skipping. The answer usually points to a format problem, not a discipline problem.
If you are a new team it may be a good idea to start standup with an icebreaker. I like to use a “question of the day” that folks answer as part of their turn in standup. It adds 30 seconds per person and goes a long way toward building rapport on a remote team.
- What was your favorite vacation spot growing up?
- What did you want to be as a kid?
- Which sport is your LEAST favorite to watch?