Latest / The Productivity Podcast with Fexingo: Output, Efficiency, and Long-Term Economic Growth / The Productivity Deficit Hidden Inside Every Meeting
Transcript
- Lucas: There is a number that haunts me. Forty-seven minutes. Luna: That's not a meeting length. That's something else. Lucas: It is not the meeting. Forty-seven minutes is the average uninterrupted focus block for a knowledge worker in a typical office, according to a Cornell study from late last year. The researchers tracked 1,200 people across finance, tech, and consulting. Their calendars were sliced into tiny little pieces. Luna: Right, because meetings break up the day. But the meeting itself is only part of the cost. Lucas: Exactly. That is the core insight. The study also measured something they called the recovery tax. After a meeting ends, the average worker needs twenty-three minutes to get back to the same level of cognitive focus they had before the meeting started. You close the Zoom window, you stare at your notes, you check email, you try to remember what you were working on. Twenty-three minutes. Gone. Luna: So a thirty-minute meeting actually costs fifty-three minutes of productive time. That's almost double. Lucas: Worse if the meeting runs long. And most knowledge workers have four to six meetings a day. Do the math: you can lose two to three hours just to recovery. That is not a trivial leak. That's a hole in the hull. Luna: The obvious response is fewer meetings. That's what most productivity advice says. Lucas: It is. And I am not against fewer meetings. But the Cornell data suggests that meeting count might not be the only lever. The bigger variable might be spacing. How close together are your meetings? If you back to back three meetings in the morning, you never get a focus block long enough to produce any recovery benefit. You are just in recovery mode all day. Luna: So you could have the same number of meetings but cluster them differently and get more output? Lucas: That is exactly what a mid-sized software firm called Pragma Labs found. They had about four hundred employees. They did not cut any meetings. Instead, they restructured the calendar around ninety-minute focus blocks. They said, 'No meetings between 9 a.m. and 10:30 a.m., and no meetings between 2 p.m. and 3:30 p.m.' Everything else was fair game. Luna: So they preserved two deep-work windows. What happened? Lucas: Developer output, measured by completed story points per sprint, went up twelve percent over three months. Not because they worked more hours. They worked fewer fragmented hours. The focus blocks gave people enough time to enter deep work, hit their stride, and produce something meaningful before the next meeting wave. Luna: And the meetings themselves? Did they get worse because they were packed closer together? Lucas: That is a fair question. Pragma Labs surveyed employees. Meeting satisfaction actually improved slightly. People felt the meetings they did attend were more focused because everyone knew there was a hard stop before the next focus block. No one wanted to be the person who made the whole team lose their deep work window. Luna: There's a behavioral nudge there. If you know your meeting ends at 10:30 and you have to be done, you don't ramble. Lucas: Right. The constraint becomes a forcing function. But not every team can do the morning and afternoon block approach. Customer-facing roles, sales teams, support desks—they have to be reactive. The principle still applies, though: you want to cluster synchronous time together and protect asynchronous time separately. Luna: Let me push on something. The Cornell recovery tax of twenty-three minutes—does it affect all roles equally? Lucas: No. And that is the really interesting part. The tax varies by the type of work you do. For roles that require deep analytical thinking—developers, writers, financial analysts, designers—the recovery time was closer to thirty-two minutes. For roles with more task-switching like managers or account executives, the tax was only about fifteen minutes. They are already used to context switching. Their brains don't need as long to recalibrate. Luna: That's kind of a double penalty, then. The people who most need uninterrupted time are the ones who lose the most when it gets broken. Lucas: Exactly. So if you are a leader, you might want to think about which roles on your team are deep-focus roles and which are collaboration-heavy. The one-size-fits-all meeting policy punishes the deep-focus people disproportionately. Luna: This is classic productivity measurement problem. We count meetings as cost, but we don't count the recovery. So the true cost is invisible. Lucas: Invisible and unmeasured. Most companies track meeting hours. They never track the hours of fragmented focus that meetings create. And that fragmentation compounds over the day. The Cornell study also found that the probability of entering a flow state drops by almost half after the second meeting of the day. By the third meeting, it is nearly impossible for most people. Luna: Flow state is the holy grail of knowledge work productivity. That is where the best ideas and the highest-quality output come from. Lucas: And we are systematically designing it out of the workday. The whole conversation around productivity has been about squeezing more out of each hour. But maybe the real gain is in designing the day so that people can actually get into a flow state in the first place. Luna: One thing I've been thinking about is async versus sync communication. If a meeting is just to share information, it can be an email or a document. But we default to meetings. Lucas: The default is the meeting because it feels efficient. You gather everyone, you talk for thirty minutes, you decide something. But the recovery tax is never part of that calculation. If you factor in the recovery cost, a lot of those information-sharing meetings become very expensive. Luna: So what is the practical alternative? Async-first? That has its own overhead. Lucas: It does. Async documentation takes time to write and time to read. But the trade-off is that people can consume it during their own focus blocks, not during everyone else's. A well-written design document might take two hours to produce and thirty minutes to read. That is three hours of total time. A meeting to cover the same content with ten people for an hour is ten hours. The async version is cheaper even before you add the recovery tax. Luna: And it's searchable. You can revisit it. Meetings vanish. Lucas: Right. So the question becomes: which decisions genuinely need synchronous conversation, and which can be handled asynchronously? Most companies don't ask that question. They just schedule the meeting. Luna: I want to get back to the Pragma Labs example. They kept all their meetings. They just spaced them differently. That seems like a lower-friction intervention than trying to cut meetings. Lucas: It is. And that is why I find it more interesting. The usual advice is 'cancel half your meetings.' But that triggers resistance. People feel their meetings are important. The spacing approach does not take anything away. It just rearranges the timing. And it produced a measurable gain without the political fight. Luna: But it only works if the whole org adopts it. If one team has focus blocks but another team schedules meetings right through them, it breaks. Lucas: That's true. Pragma Labs made it an org-wide policy. The C-suite had to respect the blocks. And they did. It's a coordination problem. But it's solvable. You just need leadership to say, 'These two hours are sacred.' Luna: This conversation about the cost of meetings and how we structure our time—it's the kind of thing that really makes you think about the economics of attention. And if walking through the economy with us has made something click for you, we should mention that this show is listener-supported. A handful of people chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making episodes like this one. Lucas: Yeah, it's a small group, but it makes a big difference. Keeps the whole show ad-free. So if you get value from it, that's the way to keep it going. Luna: Exactly. And with that, let's get back to the data. One thing I want to know: what about the meetings themselves? Are there types of meetings that have a higher recovery tax than others? Lucas: Great question. The Cornell study broke it down. Status update meetings had the highest recovery tax because they require little mental engagement. You listen, you report, you zone out. Then you have to re-engage with your own work. Brain-dump meetings—brainstorming sessions—had a lower recovery tax because you are already in problem-solving mode. The transition is smoother. Luna: So the content of the meeting matters. A well-run collaborative session might not be as costly as a status update that could have been an email. Lucas: Exactly. The recovery tax is not fixed. It depends on how cognitively similar the meeting is to the work you were doing. If you are a writer and you attend a meeting about budgets, your recovery will be long. If you attend a meeting about narrative structure, the recovery is shorter. Luna: That suggests a scheduling optimization. Put similar-topic meetings close together, and put focus blocks between different-topic clusters. Lucas: Yes. Theme your days. Monday is deep work on code. Tuesday is customer meetings. Wednesday is internal collaboration. That kind of approach reduces the number of context switches overall. Some companies are doing it. It's not widespread yet. Luna: Let me play devil's advocate. Some people thrive on variety. They like bouncing between topics. Could this approach backfire for them? Lucas: For sure. The research is about averages. Some people are natural multitaskers or high switch-taskers. But the data suggests they are a minority. For most people, context switching imposes a real cost. The key is to measure it in your own organization. Survey your people. Ask them: 'How long does it take you to refocus after a meeting?' You might be surprised. Luna: And then use that data to design the calendar. That's a nice concrete takeaway. Lucas: It is. And it is low cost. You don't need a software tool. Just a simple anonymous survey. If you find that the average recovery time in your company is twenty minutes, you can start a conversation about how to structure the day to protect focus. Luna: This episode has been about meetings and recovery tax. But I'm thinking about the broader productivity conversation. We often talk about tools and techniques, but this is about time architecture. How you shape the day. Lucas: Exactly. And the data shows that small changes in time architecture can yield real output gains. Twelve percent in the Pragma case. That is not nothing. And it didn't require anyone to work harder. Just smarter. Luna: It is a reminder that productivity is not just about doing more in less time. Sometimes it is about creating the conditions for deep work to happen at all.