Latest / The Productivity Podcast with Fexingo: Output, Efficiency, and Long-Term Economic Growth / The Hidden Productivity Cost of Meeting Recovery Time
Transcript
- Lucas: You know that moment when you come out of a meeting and you just stand there for a minute, staring at your screen, trying to remember what you were working on before the notification popped up? Luna: Oh, I live that moment. Multiple times a day. It's like my brain needs to reboot. Lucas: That reboot has a name in productivity research. It's called 'meeting recovery time,' and it might be one of the biggest silent drains on knowledge-worker output that companies are still ignoring. Luna: Okay, so is this different from just the time spent in the meeting itself? Lucas: Completely different. The meeting time is obvious — you block an hour, you spend an hour. But recovery time is the cognitive switching cost of shifting contexts. When you move from deep focused work — say, writing code or analyzing a spreadsheet — into a meeting, your brain has to disengage from that task and engage with the new context. And when the meeting ends, you can't just snap back. It takes, on average, 10 to 15 minutes to get back into a flow state. Luna: That doesn't sound like a lot, but if you have four meetings a day... that's 40 to 60 minutes of recovery time. Lucas: Right. And for a lot of knowledge workers, it's worse. A 2024 study from Microsoft's Workplace Analytics group looked at data from tens of thousands of employees across different industries. They found that the average knowledge worker attends about six meetings a day. That's an hour to an hour and a half of recovery time alone. Plus the actual meeting time — which averaged about four hours in their sample. So suddenly, your eight-hour day has less than three hours of contiguous deep work. Luna: That's brutal. And I'm guessing not all meetings are created equal. Some probably have higher recovery costs than others. Lucas: Exactly. The study found that meetings requiring high engagement — like brainstorming sessions, difficult negotiations, or performance reviews — had recovery times at the upper end, closer to 15 minutes. More routine status updates, where you're mostly listening, had recovery times around 7 to 10 minutes. But even the low end adds up. Luna: So what's the fix? Do we just declare all meetings banned and go full asynchronous? Lucas: That's the extreme version. But there's a more measured approach that a company called ModSaaS tried. ModSaaS is a mid-size software firm, about 800 employees, and they were seeing a common complaint: engineers and product managers felt they had no time to actually build things. So in early 2025, they implemented a 'no-meeting Wednesday' policy. Luna: One day a week, completely meeting-free. Lucas: Exactly. And they tracked the results over six months. Output per employee, measured in terms of code commits for engineers and completed design reviews for product people, went up by about 12 percent. But here's the interesting part: employee satisfaction scores related to focus and productivity jumped by 25 percent. Luna: So the output gain is real, but the satisfaction gain is even bigger. That suggests there's a hidden cost beyond just productivity — a morale cost. Lucas: Right. The feeling of being fragmented all day is itself draining. The Microsoft study also measured something they called 'focus fragmentation index' — basically the number of context switches per day. They found that workers with an index above a certain threshold reported 40 percent higher burnout risk. So meeting recovery time isn't just about lost minutes; it's about accumulated cognitive fatigue. Luna: I wonder if the recovery time varies by personality type. I know some people who can bounce between meetings and tasks like it's nothing. Lucas: There is some evidence that it does. A smaller study from the University of California, Irvine found that people who self-identified as 'multitaskers' actually had longer recovery times, not shorter. They thought they were good at switching, but their brains were taking a bigger hit each time. The people who did best were the ones who deliberately protected their focus — they'd block time on their calendar for deep work and treat meeting invites as interruptions. Luna: That's counterintuitive. The people who think they're good at multitasking are the ones who suffer most. Lucas: Right. It's like the Dunning-Kruger effect for attention management. But the larger point is that the cost of meetings is systematically underestimated. Companies measure meeting hours — they can see how many hours people spend in meetings. But they rarely measure the recovery time, because that's invisible. It's just 'staring at the screen' time that doesn't show up on any timesheet. Luna: So how do you make it visible? Are there tools that can track this? Lucas: There are emerging tools — Microsoft's Viva Insights, for example, can estimate focus time based on calendar data and digital activity patterns. But the simpler approach is just to ask employees. ModSaaS did a pre- and post-survey asking 'how many hours of uninterrupted focus did you get today?' Before the policy, the average was 1.8 hours. After, it was 3.4 hours on Wednesdays, and about 2.5 hours on other days because the culture started to shift. Luna: So the Wednesday policy had a spillover effect — people started being more protective of their time on other days too. Lucas: Exactly. The policy itself was just a nudge. But it signaled that the company valued deep work. Managers started to question whether a meeting was really necessary before they scheduled it. And that cultural shift might be the biggest lever. Luna: I'm thinking about the economics of this. If recovery time costs, say, an hour per worker per day, and you have 800 workers, that's 800 hours a day of lost productivity. At, say, $50 an hour fully loaded, that's $40,000 a day. Over a year, that's over $10 million. Lucas: You're in the right ballpark. The Microsoft study estimated that for a company of 10,000 knowledge workers, the annual cost of meeting recovery time could be as high as $100 million in lost output. That's not direct expense — it's opportunity cost. But it's real. Luna: So what's the counterargument? Surely there are benefits to meetings that this calculus doesn't capture. Lucas: Absolutely. Meetings build relationships, align teams, spark ideas that wouldn't happen over Slack. The point isn't to eliminate meetings. It's to reduce the low-value ones and to design the high-value ones better. For instance, ModSaaS found that after the policy, the meetings that did happen were more focused and shorter. People came prepared because they knew there wasn't an endless supply of meeting slots. Luna: So scarcity made them better. Lucas: Exactly. And that's a lesson that goes beyond ModSaaS. If you cap meeting time, you force prioritization. The most productive teams I've seen in my reporting are ones where meetings are treated as a scarce resource, not a default response to any question. Luna: I want to ask about the recovery time itself. Is there a way to shorten it? Like, can you do something in those 10 minutes to get back into flow faster? Lucas: There's some research on 'transition rituals.' Simple things like closing your email tab, putting on headphones, or writing down the next single task you need to do. The act of writing down a task seems to reduce the cognitive load — it's like you're offloading the reminder from your brain to the paper. Luna: So it's about creating a deliberate gap. Not just jumping from one thing to the next. Lucas: Right. And some companies are experimenting with 'meeting buffers' — scheduling meetings to end 10 minutes early, so there's a natural buffer. That's actually a pretty cheap intervention. No policy change, just a calendar setting. Luna: I've seen that in some workplaces — meetings scheduled for 50 minutes instead of 60. I always assumed it was for bathroom breaks. Lucas: That's part of it. But the recovery time benefit might be bigger. If you give people a 10-minute buffer, they can use it to reset, jot down notes, prepare for the next task. And you don't have the back to back cascade where every meeting starts five minutes late and ends five minutes late, compounding the fragmentation. Luna: So what's the takeaway for a manager listening to this? Should they just declare 'no-meeting Wednesdays' tomorrow? Lucas: You could, but it might backfire if you don't address the underlying reasons for all those meetings. ModSaaS had buy-in from leadership and a clear rationale. They communicated that this was about protecting deep work, not about reducing collaboration. I'd say start by measuring — survey your team on how many hours of uninterrupted focus they get. Then experiment with one meeting-free day or even a meeting-free morning. Track the output and satisfaction. The data will tell you if it's working. Luna: It seems like such a small change — just one day — but the ripple effects sound huge. Lucas: It's remarkable how much leverage there is in reducing cognitive switching. We spend a lot of time optimizing the visible parts of work — processes, tools, office layouts. But the invisible cost of context-switching might be the bigger opportunity. And meeting recovery time is a concrete, measurable piece of that. Luna: I know what I'm doing after this recording: I'm blocking out two hours of focus time on my calendar right now. Lucas: Just make sure you don't schedule a meeting to discuss the focus time block. Luna: Too late. I already have a meeting about it tomorrow. Lucas: There's a joke in there about the meeting recovery time from the meeting about focus time, but I think we've made our point. Luna: We definitely have. I think this is one of those episodes that will make people look at their calendar differently. Lucas: That's the hope. And if one listener decides to experiment with meeting buffers or a no-meeting day, and sees a boost in their team's output, then we've done our job. Luna: Alright, next episode — maybe we look at the productivity cost of Slack notifications? I have a feeling that's another hidden drain. Lucas: It's on the list. But that's a whole other conversation.