Latest / Work-Life Balance with Fexingo: Boundaries, Time Management, and Avoiding Career Overload / The Asynchronous Communication Experiment That Changed Our Team
Transcript
- Lucas: So a few weeks back I came across this case study from a SaaS company called Flowium — about seventy engineers, fully remote — and they decided to try something pretty extreme. Luna: Extreme how? Lucas: They declared that for two weeks, no internal meetings would be scheduled unless there was a written proposal shared at least 24 hours in advance. And even then, the default answer was no. They called it 'async-first'. Luna: Wow. That sounds like a recipe for chaos, honestly. How did the team react? Lucas: That's the thing — they tracked everything. Before the experiment, the average engineer was spending about 12 hours a week in meetings. By the end of the two weeks, that dropped to just under five. And they actually shipped more features. Luna: Twelve hours down to five — that's a massive shift. But I have to imagine some people felt left out of the loop. Lucas: That was the biggest complaint. Especially from senior engineers who were used to being the 'decision-maker in the room.' Suddenly, decisions were being made in shared documents, and they felt like they were losing visibility. Luna: So the async experiment actually exposed a power dynamic issue. Lucas: Exactly. It wasn't really about the tool — it was about control. One manager admitted he scheduled meetings because it was faster than writing a clear brief. Luna: I love that honesty. Because writing a good brief is hard. It takes time. But it also forces you to think clearly. Lucas: Right. And that's the hidden benefit. The team found that when they wrote proposals, the quality of ideas improved. Bad ideas got filtered out before they ever reached a Zoom room. Luna: So what tools did they use to replace meetings? I'm guessing it wasn't just email. Lucas: No, they used a mix — Loom for async video updates, Notion for written proposals and decision logs, and Slack with a strict rule: if a message needed more than two replies, you had to move it to a thread or a doc. Luna: I like the two-reply rule. That's a simple heuristic. I might try that myself. Lucas: And here's the interesting part — they didn't ban meetings entirely. They just changed the default. If you wanted a meeting, you had to justify it. And a lot of meetings just... didn't happen. Luna: So what was the biggest productivity gain? The time saved from meetings, or something else? Lucas: Both, but the real surprise was the reduction in context-switching. Engineers reported that without meetings breaking up their day, they could enter deep focus for three- to four-hour blocks. That's rare in a typical workday. Luna: If today was actually useful to you, the way these episodes stay ad-free is listener support. Buy me a coffee dot com slash fexingo. Lucas: Yeah, it really helps. We keep the show independent, and listeners like you make that possible. So thank you. Luna: Alright, back to the experiment. One thing I'm curious about — did they have any meetings that were actually better in person? Like, some things just don't work async. Lucas: Great question. They kept a handful of meetings: weekly all-hands, one-on-ones with direct reports, and any brainstorming session that required whiteboarding. Everything else was fair game. Luna: So they were intentional about which meetings stayed. That's key. Lucas: Absolutely. And they found that the one-on-ones actually improved because managers came prepared with written updates from the async week. So the meeting time was spent on real coaching, not status updates. Luna: I think a lot of teams would benefit from this kind of experiment. Maybe not two weeks, but even a single async day. Lucas: Totally. One team I know does 'No Meeting Wednesdays' and they've seen a noticeable bump in code commits and creative output. Luna: But here's my worry — doesn't async communication lead to more written documentation, which can become overwhelming? I've worked at places where the Notion was a graveyard of outdated proposals. Lucas: That's a real risk. Flowium addressed it by appointing a 'doc owner' for each major project — someone responsible for keeping the decision log current. And they archived old docs after 30 days. Luna: A doc owner — that's smart. It prevents the 'everyone's responsible, so no one is' problem. Lucas: Right. And they also set a norm: if a doc hasn't been edited in two weeks, it gets a warning tag, and after a month it's archived. Keeps the signal to noise ratio high. Luna: I can see how this would scale to non-engineering teams too. What about customer support or sales? Those roles are inherently synchronous. Lucas: True. The experiment was limited to engineering and product. Support and sales kept their normal rhythms. But even there, they found that internal coordination between teams could go async — like a salesperson submitting a feature request via a form instead of pulling an engineer into a meeting. Luna: So the principle is: default to async for internal coordination, keep sync for external-facing and creative work. Lucas: Exactly. And the results were compelling enough that Flowium made the policy permanent after a three-month trial. They now average about six hours of meetings per engineer per week, down from twelve. Luna: That's a 50 percent reduction sustained over months. That's not a fluke. Lucas: Not at all. And the employee satisfaction survey showed a 15-point increase in 'ability to focus' scores. People felt like they actually had time to do their jobs. Luna: I wonder if smaller teams could replicate this without the formality. Like, just a team agreement: 'Before you book a meeting, write a doc.' Lucas: That's exactly how most async-first teams start. It doesn't have to be a company-wide mandate. A single team can adopt the practice and demonstrate the value. Luna: Alright, I'm going to try this with my team for a week. Just a one-week async experiment. I'll report back. Lucas: I'd love to hear how it goes. And if any listeners try it, let us know — we might do a follow-up episode. Luna: Sounds like a plan. Thanks for breaking it down, Lucas.