Why Deep Work Is Disappearing (And How to Reclaim It When Every Tool Interrupts)
Deep work is disappearing not because AI is failing us, but because most people use new tools to add noise rather than protect attention — here's how to fix that.

tl;dr
Most people's problem with focus isn't distraction in the abstract — it's that every new tool they adopt makes the problem worse, not better. Adding a productivity app without changing how you structure attention just adds another source of interruption. The fix is architectural: protect blocks of uninterrupted time first, then decide which tools fit inside them.
The average knowledge worker now switches between 10 to 25 different applications per day. That number isn't a curiosity. It's a structural explanation for why so many people end their workdays feeling both exhausted and unproductive, busy without meaningful output to show for it.
We have more tools than ever designed to help us get things done, and we're getting less of the hardest things done than ever. The tools aren't failing. We're using them wrong.
What's Actually Eating Your Focus

The problem isn't that Slack exists or that email is bad. Most people treat these channels as always-on obligations. A message arrives, attention moves. Another arrives, attention moves again. Multiply that by eight hours and you haven't worked a full day, you've refereed a queue.
Cal Newport's concept of "deep work," the ability to focus without distraction on cognitively demanding tasks, has been discussed widely since his 2016 book. What's less discussed is how dramatically the conditions required for it have deteriorated. The specific culprit isn't AI. It's the default settings of every tool we adopt.
Every new tool adopted with default notification settings is a vote against your own focus.
When a team adopts a project management platform, the default is usually: notifications on, everyone tagged liberally, updates visible to all. That's the path of least resistance, and it fragments attention across the whole team simultaneously. The tool gets blamed. The configuration never gets examined.
The Capacity Trap
The core mistake is using new tools to add capacity rather than protect attention. A new AI writing assistant means you can draft more content. A new scheduling tool means you can handle more meeting requests. A new communications platform means you can stay in contact with more people. All capacity additions. None of them attention protection.
Every tool that makes it easier to do more things also makes it easier to be interrupted by more things. The throughput goes up. The depth goes down.
of workers can't focus for one hour straight
Metaintro Research 2026
That figure, cited in Metaintro's analysis of the distraction economy, points to something structural rather than personal. This isn't a willpower problem affecting a minority of easily distracted people. It's a near-universal condition produced by environments designed, through defaults rather than malice, to prevent sustained concentration.
If four out of five knowledge workers can't hold focus for sixty uninterrupted minutes, the obvious question is: what's being produced in those interrupted minutes? Mostly reactive work. Responses, updates, check-ins. Coordination rather than creation. The stuff that feels productive and produces little that compounds.
Why AI Makes This Worse Before It Makes It Better
AI tools should, in theory, reduce the cognitive overhead of routine tasks and free up time for deeper work. In practice, most teams use AI to handle more volume of the same shallow work rather than to carve out space for harder thinking.
An AI that drafts your emails faster means you send more emails. An AI that summarises meeting notes means you attend more meetings. The freed-up minutes don't automatically flow into deep work. They flow back into the system that generated the shallow work in the first place.
AI adds capacity by default. Protecting attention requires a deliberate architectural decision that no tool makes for you.
The exception is when people use AI intentionally and in batches rather than reactively. If you block 90 minutes to use an AI assistant for research, drafting, and analysis in a single session, rather than pinging it throughout the day between other tasks, you get the productivity gain without the fragmentation. Using structured prompts to batch AI work into focused sessions is one practical way to make this shift. Output quality also improves significantly when you're working with context rather than firing isolated queries into a gap between Slack notifications.
How to Actually Reclaim It

Reclaiming deep work is an architectural problem, and it needs an architectural answer. Three changes that work if you implement them fully rather than halfway:
- Block time before you fill it. Schedule deep work blocks at the start of the week, before meetings, before requests, before anything else lands on your calendar. A 90-minute block at 9am that's already committed is harder to erode than a vague intention to "find time later."
- Treat notification defaults as a choice, not a given. Turn off all non-essential notifications by default and add back only what genuinely requires immediate response. Most things that feel urgent in a notification are not urgent in reality.
- Use tools to protect attention, not just manage tasks. There are tools specifically designed to defend focus time rather than just organise tasks. An AI tool designed to protect deep work time can automatically schedule focus blocks around your existing commitments and reschedule them when meetings encroach, rather than leaving you to fight that battle manually every week.
Remote work data offers a useful signal here. Remote workers reportedly average around 22.75 hours of deep focus per week compared to 18.6 hours for in-office workers, according to research cited by productivity researchers. The mechanism isn't magic. It's reduced ambient interruption and more control over the environment. You can replicate that control without changing where you work, if you change how you configure your tools and your calendar.
what they did
Designated two daily "no-meeting, no-Slack" windows of 90 minutes each for the whole team, disabled all non-critical notifications during those windows, and batched all AI tool usage into one of those two sessions rather than using AI reactively throughout the day
outcome
Reported a measurable increase in long-form output per writer per week within the first month, with fewer revision cycles attributed to context-switching errors
The Decision You're Actually Making
Every time you adopt a new tool without configuring it to protect your attention, you're making a choice: "I'll handle the interruptions." That's fine if the tool's value exceeds the cost of those interruptions. For most tools, on most days, it doesn't.
The question to ask about any new tool is specific: does adopting this make it easier or harder to spend 90 minutes on my most important work without interruption? If the honest answer is harder, either configure it differently before you deploy it, or don't deploy it at all.
verdict
Deep work isn't disappearing because people are lazy or because AI is causing harm. It's disappearing because the default configuration of nearly every modern work tool optimises for responsiveness over depth, and most teams never change those defaults. Fix the defaults, protect the blocks, and batch your tool use into focused sessions — the capacity was always there.

Alec Chambers
Founder, ToolsForHumans
I've been building things online since I was 12 — 18 years of shipping products, picking tools, and finding out what actually works after the launch noise dies down. ToolsForHumans started as the research I kept needing: what practitioners are still recommending months after launch, and whether the search data backs it up. Since 2022 it's helped 600,000+ people find software that actually fits how they work.