How to Run Effective Remote Standups (Without the Meeting)

The daily standup is one of the most cargo-culted practices in remote work. It was designed for co-located teams: stand up (so it stays short), share what you did yesterday, what you're doing today, and what's blocking you. Three questions. Done in 10 minutes.

In theory, remote video standups should work the same way. In practice, they rarely do.

Why Remote Video Standups Don't Work

Time zone problems. A 9am standup for New York is 2pm for London and 3am for Singapore. Distributed teams end up with a standup window that genuinely doesn't work for a significant portion of the team.

They're status theater. Most video standups become a round-robin of "I'm working on X" that no one actually needs in real-time. The information could be read in text in 2 minutes.

People perform instead of communicate. In a video call, team members say things that sound good rather than flagging real blockers. Blockers are vulnerable to admit in front of an audience. In a written update, people are more honest.

They start 3 minutes late and go 12 minutes over. The human tendency to add context, ask tangential questions, and discuss things that could be handled offline consistently makes 10-minute standups take 25 minutes.

They produce no record. When the standup is done, the information exists only in the memory of whoever was paying attention. No searchable record, no documentation of blockers over time.

The Async Standup Formats That Actually Work

Format 1: Written Channel Update (Best for Most Teams)

Designate a dedicated Slack channel (or a standup section in your project tool) where each team member posts a brief update at the start of their workday.

Template:

Yesterday: [What you completed]
Today: [What you're working on]
Blockers: [What's in your way — or "none"]

Rules that make this work:

• Posts happen by a designated time (e.g., within the first hour of the workday)
• Managers read and respond to blockers same day
• The channel is for updates only — discussions about blockers move to the relevant task thread

Why it's better than a meeting: It takes 3 minutes to write and 5 minutes to read the whole team's updates. It creates a searchable record. Team members in different time zones can participate on their own schedule.

Format 2: Short Async Video (Best for Complex Status)

Some work is hard to describe in text. Design reviews, architectural decisions, and nuanced blockers communicate better in video.

How it works: Team members record a 1–3 minute Loom video (or similar) for their standup update. Share the link in the standup channel.

When to use it: Good for teams where work is highly visual or technical. The video communicates context that text can't.

The catch: Videos take longer to watch than written updates. Use this format selectively — not every standup needs to be a video.

Format 3: Bot-Triggered Check-In (Best for Accountability)

Tools like Geekbot, Range, or Zlyqor's check-in features send automated prompts to each team member at their local start time. Responses are collected and shared in a channel or project view.

How it works:

1. Bot pings each team member with standup questions at their configured local time
2. Team members reply in the bot (text, no video required)
3. Bot posts a formatted summary to the team channel

Why it's better than a manual channel: The automated prompt reduces the friction of remembering to post. The formatting is consistent. You can run reports on blockers over time.

Popular tools: Geekbot ($2.50/user/month), Range (free for small teams), or the built-in standup features in project management tools.

What to Do With Blockers

The whole point of a standup — any format — is surfacing blockers early enough to unblock people. Async standups are only better than meetings if someone is actually reading the updates and acting on blockers.

The rule: Any blocker in a standup update gets acknowledged and addressed within 4 hours by the relevant manager or teammate. If blockers get posted and ignored, the team learns to stop posting real blockers.

Practical setup: In your project management tool, flag tasks that have a blocker status. The standup update should reference the specific task. The manager resolves the blocker in the task thread.

Making the Transition

Teams that have done daily video standups for years don't drop them overnight. A gradual transition works better:

Week 1: Keep the video standup but ask everyone to post a written update 30 minutes before the call. The call is optional for anyone whose update is clear.

Week 2–3: Replace 3 of the 5 weekly standups with written-only updates. Keep Monday and Friday as video calls.

Week 4+: Drop the daily video standup entirely. Keep a weekly sync for discussion and connection.

Most teams find that after the transition, they recover 2–3 hours per week per person and maintain better awareness of team status than they had with the daily meeting.

The broader context on async communication at async vs. sync communication explains why standups are one of many meetings that translate better to async.

The Template (Copy and Use)

Here's a ready-to-use async standup template for Slack or a project channel:

**[Your name] — [Date]**
Yesterday: 
Today: 
Blockers: 

Short. Clear. Done in 3 minutes. Better for your whole team.

Ready to Make the Switch?

Zlyqor includes built-in async standup features and project task tracking so your team's daily updates stay connected to the actual work — not floating in a chat channel.

Start free →