Latest / Future of Work Tech with Fexingo: Remote Tools, AI Productivity, and Workplace Software / How Async Video Replaces Standup Meetings
Transcript
- Lucas: You know that daily standup meeting — the one where everyone on a remote team logs into a video call and says what they did yesterday, what they're doing today, and what's blocking them? Luna: Oh, the classic 'yesterday today blockers' format. I've been on teams where that fifteen-minute standup somehow always turns into thirty. Lucas: Right. And the thing is, a growing number of remote-first companies are deciding that live standup is the wrong format. They're replacing it with short, asynchronous video updates — recorded on your own time, watched by the team whenever they can. Luna: Like a video version of a Slack status update? I can see the appeal — no scheduling, no waiting for latecomers. But do you lose something by not being live? Lucas: We'll get to that. But first, let's look at who's doing this. GitLab — the DevOps platform — they've been fully remote since day one. They've documented their async video approach in their internal handbook. They call it 'daily async standup' and it's a three-minute video recorded each morning. Luna: Three minutes — that's strict. I've seen teams try five-minute limits. But GitLab has, what, over two thousand employees? That's a lot of videos. Lucas: Exactly. And they don't expect everyone to watch every single one. The videos are tagged by team and project. You watch the ones relevant to your work. The rest you can skip. It's less about broadcasting status to the whole company and more about creating a searchable archive. Lucas: If today's conversation about async work gave you something useful — a tool, a method, a way of thinking about your own team — that's exactly why we do this. We deliberately don't run ads on these episodes. If you want to support that choice, the link is buy me a coffee dot com slash fexingo. Luna: Yeah, listener support is what keeps this ad-free. Every contribution helps us stay independent and focused on the ideas that matter. Lucas: So back to GitLab. They've found that recorded video actually carries more context than text. Tone of voice, facial expression — you can tell if someone sounds excited about a breakthrough or stuck on a bug. Text-based async, like a Slack message, flattens that. Luna: That's a good point. I've misread tone in text more times than I can count. But video can also be exhausting if you're watching twenty three-minute clips a day. Lucas: That's where discipline comes in. The best practice at GitLab is to limit video length strictly. Also, they encourage 'loom-style' screen captures with face in a corner — so you see the code or document while the person talks. It's not just talking head. Luna: Zapier does something similar, right? I remember reading they use async video for standups and even for some one-on-ones. Lucas: Yes. Zapier has been remote since 2011. Their approach is a bit looser — they use a tool called Soapbox, which is now part of Wistia. People record updates as needed, sometimes only two or three times a week. They found that forcing daily video can create resentment if there's nothing new to report. Luna: So it's not about replacing the standup with video every single day. It's about using video when there's something visual or nuanced to convey. Lucas: Exactly. And there's data now. A 2025 study by Otter.ai — the transcription company — looked at fifty remote teams that switched from live standup to async video for at least three months. They found a 40% reduction in total meeting time across those teams. And a 30% increase in self-reported satisfaction with information clarity. Luna: Interesting — clarity improved. I would have guessed that talking live would be clearer because you can ask questions immediately. Lucas: That's the trade-off. The Otter study noted that while clarity increased, spontaneous problem-solving decreased. People were less likely to jump in and say 'oh, I had that same bug last week, here's the fix.' So some teams now do one live sync per week — often Monday — to capture that serendipity, and use async video the rest of the week. Luna: A hybrid async-sync model. That makes sense. So the standup isn't dead — it's evolving into a weekly live huddle plus daily video updates. Lucas: And that hybrid approach seems to be winning. Another company, Automattic — the parent of WordPress.com and Tumblr — they've been fully distributed for years. They use a tool called P2, which is like a blog for team updates. Some teams there use text, but many now embed short video clips directly into P2 posts. Luna: So it's not just about replacing the meeting format. It's about embedding video into the existing async workflow — like a comment that plays in line. Lucas: Right. And I think the key insight is that video works best when it's not a production. You don't need perfect lighting or a script. GitLab's handbook literally says 'record in one take, don't edit.' The value is in the informal, authentic update. Luna: That's a hard sell for some people who hate being on camera. I've worked with engineers who would rather write a five-paragraph email than record a thirty-second video. Lucas: And that's fine — not everyone needs to use video. The async principle is about choosing the medium that communicates best. If a written update is clearer for a specific person, do that. But for team-wide visibility, video seems to build more connection. Luna: Do you think this trend will kill the live standup entirely in remote-first companies? Or will it always have a place? Lucas: I don't think it disappears, but I think it becomes rarer and more intentional. The live standup survives for teams that are co-located or that value the social ritual. But for distributed teams, forcing a synchronous daily meeting is increasingly seen as inefficient. The data from Otter.ai and the practices at GitLab, Zapier, and Automattic suggest that async video will become the default. Luna: So the future of the standup might be a weekly sync for social glue, and daily video updates for information flow. That feels workable. Lucas: And it leaves more time for deep work. Which is the whole point of async work tools — to protect focus. I think we'll see more tools designed specifically for this: lightweight, threaded video updates that integrate with project management platforms. Luna: Are there any downsides you're worried about? Like, could video standups increase the pressure to always be 'on'? Lucas: That's a real risk. If a team expects everyone to post a video every morning, that can feel like surveillance. The best practices emphasize that videos are optional — you can post text if you prefer. And they should be recorded asynchronously, not live-streamed. If you're watching them in real-time, you've lost the async benefit. Luna: And there's the issue of accessibility — not everyone can easily produce or consume video. Transcripts should be standard. Lucas: Absolutely. GitLab auto-generates captions and provides a text summary. That's essential. Async video is a supplement to text, not a replacement. Luna: So what's the one concrete takeaway for a team leader listening who wants to try this? Lucas: Start small. Pick one team that struggles with meeting overload. Replace their daily live standup with a three-minute video update for two weeks. Use a simple tool — Loom, Soapbox, even your phone. Have everyone post to a shared channel. At the end of two weeks, ask: did you feel more informed? Did you save time? Then decide if you want to keep it. Luna: And if they want to keep the social ritual, they can schedule a weekly check-in call. Best of both worlds. Lucas: Exactly. The standup as a daily live meeting is a practice born in the co-located era. Asynchronous video offers a way to preserve the information-sharing function without the meeting overhead. Luna: So the question becomes: what else are we doing out of habit that could be async? Lucas: That's exactly the question. And I'd argue it applies to more than just standups — status updates, project reviews, even some client meetings. The principle is universal: if it doesn't need to be live, don't make it live. Luna: Well said. Alright, I think that's a solid place to leave it. Thanks, Lucas. Lucas: Thanks, Luna. Talk to you next time.