If your team is spread across four time zones, the 9am standup is a fiction. Someone's asleep. Someone's on their second coffee. Someone joins, says "no blockers," and leaves. You learned nothing, and you spent 15 minutes of everyone's overlapping hours doing it.
Async standups fix this, but most of the templates out there are a Notion doc that goes stale by Wednesday or a Slack bot that buries updates in a channel nobody re-reads. This is a standup you build once inside Zoobbe and reuse every day, with the update living next to the actual work instead of in a chat river.
Key takeaways
- A synchronous standup punishes distributed teams by forcing overlap that doesn't exist.
- An async standup works when updates are structured, findable later, and attached to real cards, not lost in chat.
- You can build a repeatable async standup in Zoobbe with a board, custom fields, a scheduled automation, and a page template for the format.
- Blockers become watchable, assignable cards instead of a message someone scrolls past.
- No Slack thread required, and no daily meeting to schedule around.
Why synchronous standups fail distributed teams
The daily standup was designed for a co-located team standing in a room. Move that team across continents and the format quietly stops working. To get everyone in one call, you either pick a time that's brutal for one region or you split into sub-standups that lose the shared context the ritual was supposed to create.
Even when the call happens, the format is bad at its own job. Spoken updates evaporate. If you missed the meeting, you're reconstructing what happened from memory and half a Slack thread. Blockers get mentioned out loud and then forgotten because nobody wrote them down anywhere durable.
Async fixes the time-zone problem, but only if the updates are structured and permanent. A wall of free-text messages is not a standup. It's homework nobody grades.
What a good async standup actually needs
Before the template, the shape. A distributed async standup works when it has four properties:
- Structure. Every update answers the same questions, so they're scannable in seconds.
- Permanence. Yesterday's update is still there next week when someone needs to trace a decision.
- Proximity to the work. An update that lives next to the card it's about beats an update that lives in a channel.
- Actionable blockers. "I'm blocked" should create something someone can pick up, not just a sentence.
Here's how to build all four in Zoobbe.
Building the async standup board
1. Start with a standup board
Create a board with a few lists that match how updates flow: Today's Updates, Blockers, and Cleared. Each person's daily update becomes a card. Blockers get their own card so they don't hide inside a paragraph.
Because you can drag cards across columns, a blocker that gets resolved moves from Blockers to Cleared with one drag, and everyone can see the board state at a glance without reading a word.
2. Add custom fields for the standup questions
The classic three questions map cleanly onto Zoobbe's custom fields. Add a few text fields to your update card so every entry has the same shape:
- Yesterday (text): what you finished.
- Today (text): what you're picking up.
- Blocked? (single-select): Yes / No.
Now every update is filled out the same way. No format drift, no "wait, what did you actually do?"
3. Make blockers real cards
When someone marks Blocked? as Yes, they create a card in the Blockers list, assign the person who can unblock them, and add watchers so the right people get notified. Blockers stop being a sentence someone scrolls past and become an owned, tracked item with threaded comments and @mentions for the back-and-forth.
4. Automate the daily rhythm
This is where async standups stop rotting. Zoobbe automations run on triggers, conditions, and actions, and one of the triggers is a cron schedule. Set a scheduled automation to fire every weekday morning that creates the day's update cards or posts a reminder comment, so nobody has to remember to "start" the standup.
You can layer more on top: when a due date on a blocker approaches, auto-assign or comment. When a card moves to Cleared, notify the watchers. The ritual runs itself.
5. Capture the format in a page template
For teams that want a written narrative alongside the board, Zoobbe's page editor supports rich text with a meeting-category page template. Save your standup format as a template once and spin up a fresh, structured page each day, with the added benefit that pages are edited in real time via CRDT, so two people in different time zones can fill one in without stepping on each other or refreshing.
Why this beats a Slack thread
A Slack standup thread has one job and does it badly: it disappears. Yesterday's updates are buried under today's memes. There's no structure, no status you can see at a glance, and a blocker mentioned at 2am is gone by 9am.
The board version keeps updates structured, keeps blockers assignable, and keeps everything permanent and searchable by title. Live presence shows you who's viewing the board right now, so async doesn't have to mean invisible. And because it all lives next to the actual cards your team works from, the standup connects to the work instead of describing it from a distance.
Make it yours
The setup above is a starting point, not a commandment. Some distributed teams add a Wins list to bank small victories that would otherwise vanish. Others attach a countdown timer to blockers to track how long something's been stuck. The point is that you build the structure once and the automation keeps it alive, so the standup survives past week one.
FAQ
Do I need Slack to run an async standup in Zoobbe?
No. The whole point of this setup is that updates live on the board and on pages, next to the work, with in-app notifications and daily digest emails handling the pings. There's no separate chat tool to maintain.
Does Zoobbe have a ready-made standup board template I can clone?
Zoobbe offers page templates by category, including a meeting category you can use for the written standup format. For the board itself, you set up the lists and custom fields once, then let a scheduled automation reproduce the daily rhythm.
How do blockers get surfaced across time zones?
A blocker becomes a card with assignees and watchers, so the person who can unblock it gets notified through in-app notifications and daily digest email, regardless of when they come online.
Can two people update the same standup page at once?
Yes. Pages use real-time collaborative editing via a CRDT, so teammates in different time zones can edit the same page without refreshing or overwriting each other.
How do I keep the standup from going stale?
Use a scheduled automation with a cron trigger to create the day's update cards or post a reminder every weekday morning. The ritual runs on a schedule instead of on someone remembering to kick it off.
Run your next standup async
If your distributed team is still forcing a synchronous call across impossible hours, the fix isn't a better meeting time. It's a standup that doesn't need a meeting. Build the board once, wire up the automation, and let your team update on their own clock. Set up your async standup in Zoobbe and give everyone their mornings back.
Photo by Patrick Perkins on Unsplash