Standups quietly eat twenty minutes a day. Add the context-switch on either side and the real cost is closer to forty-five. We moved ours entirely into Copera — threads, not meetings — and got the coordination without the calendar hold. Here’s the exact setup we run.
The daily standup is one of those rituals everyone keeps because the alternative feels like chaos. But the synchronous version has a design flaw: it forces a distributed team into the same fifteen minutes, penalizes anyone in the wrong timezone, and produces almost no durable record. By the afternoon, nobody remembers who said they were blocked. This is a practical walkthrough of the async standup we’ve run for over a year, why each piece exists, and how to copy it in an hour.
What a standup is actually for
Strip away the ritual and a standup does three jobs: it surfaces blockers early, it keeps priorities visible, and it gives the team a lightweight sense of momentum. Notice that none of those jobs require everyone to be online at once. They require the information to be captured and seen — which is exactly what a good async system does better than a live call.
A meeting is the most expensive way to share information that could have been a thread.
The setup, step by step
We run the whole thing in a single channel with one automation. You can build the same thing in Copera in about an hour.
- One dedicated channel. Create a
#standupchannel and add the whole team. Not just engineers — design, PM, and anyone whose work has dependencies. Visibility is the point. - A scheduled prompt. Set an automation to post the same three-question prompt every weekday at 9:30 in each person’s local morning: What did I move yesterday? What am I focused on today? What’s blocking me?
- Replies as threads. Everyone answers in a thread on that prompt. Threads keep the channel scannable — you see the day’s roster at a glance and open only the updates you care about.
- Blockers get a tag. Any update that mentions a blocker gets a 🚩 reaction. A second automation collects flagged threads into a short digest for the team lead. Blockers stop hiding in the middle of a paragraph.
The rules that make it work
Tools don’t create discipline; norms do. Three norms carry ours:
- Write for the person who’s asleep. Assume your reader has zero context and won’t reply for six hours. That one habit forces the specificity that makes async faster than a call.
- Blockers are a request, not a status. “Blocked on the API contract” is a status. “Blocked on the API contract — @priya, can you confirm the response shape by noon?” is a request. Only the second one gets unblocked.
- No standup theater. If you genuinely have nothing to report, a single line is fine. The goal is signal, not attendance.
What changed when we stopped meeting
The obvious win was the reclaimed time — roughly three hours per person per week across the team once you count the switching cost on both ends of a live call. But the changes we didn’t predict mattered more.
Blockers started surfacing earlier, because people wrote them down at 9:30 instead of waiting to say them out loud at 11. Timezones stopped being a tax: a teammate five hours ahead posted before we woke up, and their blocker was already handled by the time they logged back on. And because every update was written and searchable, “what was the status of that migration last Tuesday?” became a search instead of an interrogation.
When a live sync still earns its place
Async isn’t a religion. Some conversations are genuinely better live: a thorny design debate, a tense decision with real disagreement, or the human maintenance a team needs to stay a team. The trick is to reserve synchronous time for the work that actually benefits from it, and to stop spending it on status updates a thread handles for free.
Move the reporting to writing, keep the meetings for thinking, and you get the best of both: a team that stays coordinated all day and a calendar that finally has room in it.
