Kill the daily standup. Send a morning brief.
A daily standup is a synchronisation meeting for people who share a room. If your team is spread across sites, vehicles and shifts, it costs everyone fifteen minutes to deliver information that mattered to two of them — and the person who most needed to speak up usually did not.
The replacement is not "one more chat group". It is three things: a personal morning brief, a blocked status that people can actually use, and one weekly number worth looking at.
Key takeaways
- A standup is a status-collection mechanism, and it is a slow and unreliable one.
- A morning brief is personal. Each person gets their own day, not everyone else's.
- Blocked must be a status, not an announcement — surfacing a problem should not require speaking up in a meeting.
- Yesterday is the wrong window. Review weekly; days are too noisy to act on.
- Cancel it as an experiment, with a date to review. Cancellations that are permanent get resisted.
Why do standups stop working?
Because the cost is paid by everyone and the value goes to a few — and that ratio gets worse as the team spreads out.
Three failures are near-universal:
- Most of it does not apply to you. Fourteen people describe their day; two items concern you.
- It rewards sounding busy. A verbal round-robin is a performance format, and it is answered accordingly.
- Nobody raises the real blocker. Saying "I have been stuck for three days" out loud, to everyone, is socially expensive. So it gets discovered on the deadline.
For a team in one room, those costs are small enough that the meeting still nets out positive. For a team of site supervisors and drivers, it does not — you are pulling people off work to attend a ceremony designed for a shared office.
What should replace it?
A brief that goes to each person individually, a status that makes blocked work visible without a meeting, and a weekly review.
| Standup does | Replace with |
|---|---|
| Tells you what is on today | A morning brief with your tasks, meetings and routines |
| Surfaces blockers | A Waiting-on and Blocked status, showing days stuck |
| Gives managers a status feel | A day view and a weekly report |
| Creates a moment of accountability | Reminders that escalate on their own |
| Occasionally produces a real conversation | Keep one weekly meeting for exactly this |
Note the last row. The one genuinely valuable thing a standup sometimes produces is a conversation two people needed to have. Do not delete that — move it to a weekly slot where it has room, instead of squeezing it into a round-robin.
What goes in a morning brief?
One person's day, short enough to read in a chat message: what is overdue, what is due today, their meetings, and any routines they run.
The word that matters is personal. A brief listing everything for everyone is a newsletter, and it will be skimmed and then ignored. If someone has to work out which three of the twenty lines apply to them, you have rebuilt the standup in text.
Let people choose when it arrives — a driver's useful moment is not an accountant's. An optional evening wrap suits some roles and irritates others, so it should be exactly that: optional.
Delivery should reach people where they already are. For most teams that is WhatsApp rather than an app they would have to open. See WhatsApp task management: the complete guide.
How do blockers surface without a meeting?
By making Waiting-on and Blocked ordinary statuses that cost nothing socially to set.
This is the piece people miss when they cancel the standup, and its absence is why some teams reinstate it. If the only states are done and not-done, a stuck person has no way to tell you except by messaging — which feels like an admission — so they wait, and you find out at the deadline.
Give them a Waiting-on state that shows how many days it has sat, and a Blocked state with its own column and filter. Now the information arrives on day one, and it arrives as a fact rather than a confession. Your job becomes reading the blocked column each morning, which takes about ten seconds.
One rule makes it work: treat a rise in blocked items as information about the process, never as a mark against the person who reported it. Punish the report and you will stop getting it.
What should you look at weekly instead?
Trends, not yesterday. Completion, what was late, and whether the same person is stuck for the fourth week running.
A day is too noisy to act on — one late task means someone had a bad Tuesday. A week is long enough to show a pattern and short enough to fix.
Worth reading weekly:
- Who closed what, and what was late.
- A reliability measure combining on-time delivery with the state of the open pile, tracked week over week.
- Where the hours went — meeting time by person and department is often the most uncomfortable and most useful number available.
- What never got picked up at all.
A weekly summary sent to managers turns this from a report someone has to remember to open into something that arrives.
How do you actually cancel it?
As a two-week experiment with a review date, and with the replacement running first.
- Turn on the brief first, and let it run for a week alongside the standup. People need to see that the information still arrives.
- Make blocked visible, and say explicitly that using it is welcome.
- Cancel for two weeks, with a date in the diary to review. Reversible decisions get far less resistance than permanent ones.
- Keep one weekly meeting for the conversations that actually need people in the same call.
- At the review, ask what people lost. Usually it is one specific thing, and usually it is fixable without reinstating a daily meeting.
Sitatu sends a morning brief at a time each person chooses, with an optional evening wrap, and gives managers a weekly summary of last week's numbers on WhatsApp. See the features page or start a free trial. On the chasing side, read why your reminders get ignored.
Frequently asked questions
What is the alternative to a daily standup?
A written or automated morning brief that reaches each person individually with their own tasks, meetings and routines, combined with a visible blocked status so problems surface without a meeting, and one weekly review that looks at trends rather than yesterday.
Why do daily standups fail for distributed teams?
Because a standup is a synchronisation meeting for people who share a room. When the team is spread across sites and shifts, the meeting costs everyone the same amount of time while returning information that was only relevant to two of them.
Does removing the standup mean losing visibility?
No, provided the status is readable somewhere. The standup was a slow, unreliable way of collecting status verbally. A day view, a blocked column and a weekly report all give more accurate answers without booking anyone's time.
What should a morning brief contain?
Just that person's day: what is overdue, what is due today, their meetings, and any routines they run. It should be short enough to read in a chat message and specific enough that no one has to work out which parts apply to them.