Latest / The Productivity Podcast with Fexingo: Output, Efficiency, and Long-Term Economic Growth / The Productivity Cost of Switching Tabs
Transcript
- Lucas: Luna, how many times today have you switched tabs, checked a notification, or glanced at Slack while you were trying to write something? Luna: Oh, I don't even want to count. Probably dozens. And I know I'm not alone. Lucas: You're definitely not. There's a concept in productivity research called 'attention residue'—the idea that when you switch tasks, part of your brain stays stuck on the previous task. And the cost is real: a Microsoft study found that it takes an average of 23 minutes to fully refocus after a single interruption. Luna: Twenty-three minutes? That seems almost too high. But then I think about how long it takes me to get back into a writing flow after checking email, and yeah, it checks out. Lucas: And that 23 minutes is just for one interruption. If you're interrupted six times an hour—which many knowledge workers are—you're basically never at full focus. The cumulative cost is enormous, and it's almost entirely invisible on a spreadsheet. Luna: Look, I think a lot of listeners have felt this. And if walking through the economy with us has made something click for you, we want to mention that we deliberately don't run ads on these shows. If you want to support that choice, the link is buy me a coffee dot com slash fexingo. Lucas: Yeah, it's a small way to keep this ad-free. And honestly, the fact that we don't have to sell you anything makes it easier to dive into weird, specific topics like this one. Luna: Exactly. So back to attention residue—I want to hear about that Danish design firm you mentioned. Lucas: Right. The firm is called DDC—Danish Design Centre—though the principles apply anywhere. They redesigned their entire workflow around blocking context switches. Instead of letting emails come in all day, they batch communication into two windows: 10 AM to 11 AM, and 2 PM to 3 PM. Outside those windows, they don't check messages. Luna: That sounds great in theory, but what about urgent stuff? Do clients just have to wait? Lucas: They set up a separate channel for truly urgent issues—basically a 'fire alarm' flag. But they found that after the first month, almost nothing was actually urgent. The culture of 'reply within five minutes' was self-imposed. When they stopped feeding the habit, the urgency vanished. Luna: So the switching cost was mostly self-inflicted. That's both encouraging and a little humbling. Lucas: Exactly. And they tracked one metric: deep work hours per employee per week. It went from about 10 hours to 18 hours. That's an 80% increase in focused output, just by reducing context switches. Luna: That's huge. But I wonder—does that hold for all roles? A customer support person can't batch their messages the same way a designer can. Lucas: Fair point. The DDC model works best for roles where deep, uninterrupted thinking is the main output. For reactive roles, the fix is different—maybe rotating who handles interruptions in hourly shifts, so not everyone is interrupted all day. Luna: That makes sense. So we've been talking about the cost. But what about the fix? Are there tools or techniques that actually reduce the switching tax? Lucas: One approach is 'monotasking'—doing one thing at a time. But the reality is, we need to switch sometimes. The key is to make switches deliberate, not reactive. For example, if you decide ahead of time that you'll check email at 10:30, you're in control. If a Slack notification pulls you away, your brain is reacting. Luna: So the cost is higher when the switch is forced rather than chosen. That aligns with the research on cognitive load—your brain has to process the interruption itself, not just the new task. Lucas: Right. And that's where AI assistants come in. Some researchers argue that AI could reduce the switching tax by handling the 'mental cleanup' between tasks—for instance, automatically summarizing what you were working on when you got interrupted, so you can pick up faster. Luna: That sounds promising, but I've also seen AI tools that make switching easier—like, you can ask it to switch contexts instantly—which might encourage even more switching. Lucas: Exactly. It's a double-edged sword. If the AI reduces the pain of switching, you might switch more often, defeating the purpose. The net effect on productivity is still an open question. Luna: So the real fix might be cultural, not technological. Companies need to value focus over responsiveness. Lucas: I think that's the bottom line. And there's some nice economic framing here. Economists talk about 'search costs'—the time and effort to find information. Switching tabs is a search cost. But attention residue is a 'post-switch cost'—the hangover from the previous task. Most productivity tools only reduce the search cost, not the residue. Luna: So if you invest in a tool that makes switching faster, you might actually increase the total cost, because you switch more and leave more residue. Lucas: That's the counterintuitive insight. There's a 2023 paper in the Journal of Experimental Psychology that showed exactly that: participants who used a 'quick switch' interface switched 40% more often and had worse performance on both tasks than those who had a slight delay built in. Luna: So friction is actually good. A little delay forces you to ask: is this switch really worth it? Lucas: Precisely. Some teams have started adding a 10-second delay before a new tab opens, or a popup that says 'Are you sure?' It sounds silly, but it cuts context switches by a third. Luna: I love that. So what's the one thing a listener could do tomorrow to start reducing their switching tax? Lucas: Two things. First, turn off all non-essential notifications for at least one two-hour block per day. Second, batch your communication. Even if you can't do the whole day, try one morning window and one afternoon window. The research suggests you'll get back more than the time you lose. Luna: I think I'll try the batching this week. But I'm curious—does the switching tax affect different industries differently? Like, is it worse in tech than in manufacturing? Lucas: Great question. In manufacturing, the switching cost is often physical—moving from one machine to another. But in knowledge work, it's cognitive, and it compounds. A factory worker might switch tasks a few times a day. A knowledge worker might switch dozens of times. So the tax is higher per worker in knowledge industries, but manufacturing has its own costs like setup time. Luna: So the productivity podcast is really about how we work as knowledge workers, not just macro productivity. Lucas: Exactly. And the macro implications are big. If knowledge workers waste 20% of their time on switching costs, that's a drag on GDP growth. Reducing that even a little could boost long-term productivity. Luna: Alright, so next time you feel the urge to check your phone mid-sentence, remember the 23-minute rule. Maybe that pause is worth it. Lucas: And if you want to dive deeper, we'll link to the Microsoft study and the DDC case on our site. For now, I'm going to close all my tabs except this one. Luna: Same here. See you next episode.