The weekly standup that actually works (and the one that doesn't)
Most weekly standups quietly die by week three. Here is the cadence and the shape of a standup that small teams stick with.
Every new team lead reinvents the weekly standup. The first version is usually a 30-minute Zoom where everyone reads their Jira board aloud. The second version is a Slack thread that nobody reads after Wednesday. The third version is a Notion template that gets filled out by two people and abandoned.
This pattern is not a failure of discipline. It is a failure of design.
What a weekly standup is actually for
Before fixing the shape, be clear about the job. A weekly standup is not a status report. It is not a meeting. It is a short, repeated act that keeps a team aligned on three things:
- Focus: what is the one thing this week is about?
- Ownership: who is doing what, out loud?
- Friction: what is in the way, and who can unstick it?
If your current standup is not answering those three questions every week, it is doing something else. Probably theater.
Three touchpoints, not one
A live 30-minute Monday meeting is too much ceremony. A single async Wednesday update is too little signal. The lightest cadence that still catches problems in time to fix them is three short touchpoints a week.
- Monday — plan. The team lead picks the week's focus. Goals and tasks get claimed. Ten minutes, live or async.
- Wednesday — adjust. Each teammate updates status: moved, stuck, changed. Blockers are named with context. Thirty seconds per person.
- Friday — review. What shipped, what didn't, what rolls to next week. Five minutes of reading. Celebrate wins out loud.
Nothing happens in between except the work.
Why this shape beats the alternatives
Daily standups are too much ceremony for small teams. They catch problems fast but cost half a focused morning a day.
Weekly one-touchpoint standups are too little. A week is long enough for a project to quietly go sideways. You can lose four days before anyone notices.
Mon/Wed/Fri is the minimum viable rhythm. Two days between touchpoints is short enough that problems cannot hide; long enough that the team is not performing standup for its own sake.
The shape of each touchpoint
Monday plan
Answer three questions, in this order:
- What is the theme of this week?
- Which team goals does it serve?
- Who owns what?
Write it down in one place everyone can see. Keep it short. A focused paragraph beats a pretty dashboard.
Wednesday adjust
Each person answers one question: status on what I own. Three options only.
- On track. No action needed.
- Moved. What changed, and why.
- Stuck. What is blocking me, and who can help.
The team lead reads the whole page in five minutes and unblocks on the spot.
Friday review
Each person closes out. Three questions:
- What shipped?
- What didn't, and what should happen to it?
- What is worth celebrating?
Then the team lead writes a one-paragraph wrap-up. That wrap-up is the context Monday starts from.
What kills a standup every time
- Too many questions. If there are more than three, skip gets cheap.
- No owner on the standup itself. Someone has to close Friday. Usually the team lead.
- Perfect format. Spending two months designing the page is a common way to avoid actually running the rhythm.
- No rollover. If last week's unfinished work disappears silently, no one trusts the format. Rollover must be automatic or explicit.
Start with the cheapest version
You don't need a tool to try this. A shared doc is enough for week one. Run it for three weeks. If the rhythm sticks and you are rebuilding the same template every Sunday, that is when a purpose-built weekly tool starts to pay.
Most small teams discover that the template is the product. The rhythm is the thing you are buying.