Deep work.
What is it, why we're all getting less of it and how to change that.
RescueTime tracked 185 million working hours and found that the average knowledge worker gets 2 hours and 48 minutes of genuinely productive work done per day. Not just focused work, but any productive work in any form. If you narrow it to the kind of concentrated, uninterrupted thinking that actually moves things forward, this number is even lower.
The reason isn't necessarily laziness or poor discipline. It's that the structure of a normal working day makes sustained concentration genuinely difficult. Meetings scattered through the afternoon. Slack running in the background. A phone on the desk. A calendar that treats every open hour as fair game. In that environment, even motivated, capable people end up spending most of their time on tasks that feel productive but don't require or produce their best thinking.
Deep work is the opposite. Cal Newport coined the term in his 2016 book, but the research behind it goes back decades. This guide covers what that research actually says, why it matters, and how you can achieve more deep work.
What is deep work?
Newport's definition is professional activity in a distraction-free environment that pushes your cognitive capabilities to their limit. Work that creates real value, improves your skill, and produces output that's hard for others to replicate.
The opposite is shallow work. Emails, status updates, most meetings and administrative tasks. Things you can do while half-distracted and that someone else could do just as well with a bit of context. Shallow work is often genuinely necessary. The problem is that it competes for the same resource as deep work — your attention — while requiring completely different conditions.
A useful test is to ask yourself the follow questions
Does this task need sustained, undivided focus to do well?
Does it push toward the edge of what you're currently capable of?
Would it take someone else real time and effort to produce the same output?
If yes to all three, it's deep work.
Why your brain needs uninterrupted time
The case for deep work isn't just theoretical. There's a large body of research that backs it up.
Focused attention builds skill faster. Anders Ericsson spent decades studying elite performers across various fields: musicians, chess players, surgeons, and athletes. His finding was that what separates the best from the merely good isn't the total hours they put in, but the quality of attention during those hours. Concentrated, effortful practice drives the brain to strengthen the neural pathways involved in the work. Distracted practice produces measurably less improvement. Two hours of real focus doesn't just feel different from four hours of split attention. It produces a different outcome, in the work and in the person doing it.
→ See: Deep Work and Protected Focus Blocks
Interruptions cost far more than the interruption itself. Gloria Mark at UC Irvine found that after being interrupted, it takes an average of 23 minutes to fully regain concentration. A two-minute Slack message can cost upto 23 minutes of reduced-quality work, even after you've put the phone down and you're back on your task.
→ See: Interruption Recovery Cost
Mark also found that a single phone notification, even one you don't act on, disrupts attention almost as much as actually picking the device up. The disruption is in seeing that something is waiting, not in responding to it.
→ See: Notification Distraction
Switching between tasks has a tax. Sophie Leroy's research found that when you move from one task to another, part of your attention stays on the previous task, especially if it was unfinished. She called this attention residue. You start the new task with less mental capacity than you'd have if you hadn't switched, and it takes time for that residue to clear. In a day full of context switches, those residues accumulate. By the afternoon, you're trying to concentrate under conditions shaped by every transition you've made since morning.
→ See: Attention Residue and the full guide: The Real Cost of Context Switching
Research from Rubinstein, Meyer, and Evans put the combined cost of switching between different types of demanding cognitive work at up to 40% of productive time. Across a full working day, that's a significant amount of time wasted switching between tasks.
→ See: Task Switching Costs
Willpower runs out. Roy Baumeister's research showed that the ability to make decisions, including the decision to stay focused on a task rather than check your phone, depletes across the day. By afternoon, you have less of it than you did in the morning. This is partly why deep work is harder to protect later in the day. So it's often easier to reach flow state earlier in the day.
Four ways to structure deep work into your day
Newport described four approaches to help achieve deep work:
The monastic approach means eliminating or drastically reducing shallow work commitments altogether. Think of a writer who doesn't do email during the months they're drafting a book. This works for a small group of people who have full control over their schedule. For most people with team obligations, clients, or employees, it's not realistic. But it sets the ceiling for what's possible when someone takes the conditions for deep work seriously.
The bimodal approach divides time into clearly defined deep and shallow periods at the level of days or weeks. A consultant who blocks Monday through Wednesday for focused project work and keeps Thursday and Friday for calls and communication is using this approach. The key is that the deep periods are fixed in advance and treated as non-negotiable, not as preferences that are flexible when something more urgent arrives. This requires real control over your calendar, but when that's possible, it creates a cleaner separation between the two types of work than anything else.
The rhythmic approach is the most practical for most people. Protect the same block of time every day. I.e. the first two hours of the morning, before anything else claims them and do it consistently. The research on habit formation supports this: a fixed time becomes a trigger for the behaviour over time. The decision shifts from "will I do deep work today" to "this is just what happens at 9am." → See: Habit Formation Timeline
The journalistic approach means switching into deep focus whenever a gap in the schedule appears, on demand. Newport named it after journalists who learn to write on deadline, anywhere, regardless of conditions. This is the hardest to do well and it requires the ability to enter concentration quickly, which most people need years of practice to develop.
For most founders and knowledge workers, the rhythmic approach is where to begin. One protected block, same time every day, until it becomes automatic.
Getting a block to actually hold
The calendar block is the easy part. What happens when it starts is where most intentions fall apart.
The scheduling decision is made in advance, in a calm moment, with good intentions. But the execution happens in a real environment — usually after a morning that already involved some email, on a machine with 20 open tabs from yesterday, with Slack running in the background and a notification badge on the phone. The block exists in the calendar. The environment doesn't know that.
At 9am the laptop opens. The email preview shows a message from someone relevant. Slack has a badge. There are tabs from yesterday's half-finished research. None of this needs to be acted on. But the awareness that it's all there — the sense of things waiting — creates a working state that is nothing like concentration, regardless of what the calendar says is happening right now.
The fix is environmental, not motivational. Narrowing the screen to one task, closing the tabs, putting the phone in another room, turning off notifications — these aren't productivity tips. They're the practical implementation of what the research on attention residue and decision fatigue actually recommends. Reduce the things that pull at your attention and you reduce the cognitive load of staying in the work. The environment does the job that willpower runs out of capacity to do.
This is exactly what Aftertone's Focus Screen is built for. When your deep work block starts, the interface narrows to the current task. Everything else disappears. The decision about what to work on was already made in the calendar. The execution environment just enforces it.
→ See: Flow State Conditions
A few things that determine whether the block holds day to day:
Name the task, not the slot. "Deep work, 9am" is easy to sacrifice when something comes up, because nothing specific is lost. "Write the first draft of the Q2 board update, 9am" is harder to let go of, because there's a named thing being abandoned. Specificity also matters at the start of the session — knowing exactly what the output is supposed to be means you start working immediately rather than spending the first 20 minutes deciding.
→ See: Specificity Effect, Zeigarnik Effect
Front-load it. The earlier in the day, the more decision-making capacity you have available to defend the block against competing demands. Research by Wieth and Zacks also shows that analytical performance peaks at chronotype-optimal windows — for most people, this is earlier in the day, though not for everyone.
→ Find your optimal window: Chronotypes and Productivity
Keep it away from meetings. A block immediately before a meeting fills up with preparation and the mental background noise of what's coming. A block immediately after a meeting carries the attention residue of that meeting into the first 20-30 minutes of the session. Buffer time on both sides isn't optional — it's what makes the block actually usable.
→ See: Buffer Time and Transition Periods
Don't over-schedule it. Newport is clear: very few people can sustain more than four hours of genuine deep work per day. Most people starting out should aim for 90 minutes. The instinct to block six hours on a clear Monday and expect deep work throughout is how people burn out on the practice within two weeks.
→ See: The Planning Fallacy
The hidden cost in a normal calendar
There's a version of this problem that operates at the level of the week rather than the day, and it's worth spelling out because most calendar views make it invisible.
A developer with a 9:30am stand-up, an 11am check-in, and a 2pm 1:1 doesn't have three 30-minute meetings. They have three meetings that break the day into windows of roughly 90 minutes each — with the actually usable concentration time inside each window significantly shorter, because the preparation before each meeting and the attention residue after it eat into both ends. What looks like a day with plenty of working time often has less than two hours of genuine deep work availability in it, distributed across fragments that each require rebuilding context from scratch.
This isn't an unusual calendar. It's a typical one. And it goes a long way toward explaining why knowledge workers in meeting-heavy environments routinely feel busy and underperform relative to their ability at the same time.
→ See: Buffer Time and Transition Periods
The answer isn't usually to eliminate meetings. It's to batch them — to create full days or half-days with no meetings at all, and to treat those as structurally protected rather than aspirationally protected. A standing rule (Tuesdays are no-meeting days, always) requires far fewer individual decisions to maintain than a weekly intention to protect time when possible.
How to know if it's actually working
Most people block the time, sometimes complete the session, and have no real view of whether the practice is producing results over time. Whether the blocks are being eroded week by week. Whether the weeks that felt most productive shared structural features. Whether the gap between scheduled and completed deep work is growing or shrinking.
Without that view, the practice can't improve. It continues or it doesn't, and you can't tell why.
The number worth tracking is simple: how many uninterrupted 90-minute blocks did you actually complete this week, versus how many you scheduled? Most people don't know this figure. The gap between those two numbers is often the most important data point in the week, and almost no tool surfaces it automatically.
Teresa Amabile's research — across 12,000 working diary entries from 238 people — found that the single biggest driver of a good working day was making meaningful progress in the work. Not praise, not incentives. Progress. The weekly view that shows what actually moved, not just what was planned, is what turns a deep work practice into something that compounds rather than just continues.
→ See: Progress Principle, Self-Monitoring and Progress Tracking, Reflection and After-Action Reviews
Deep work for different types of work
The principles are the same across roles, but where the friction lives varies enough that it's worth being specific.
Founders and operators face a version where the shallow work is often genuinely urgent — real fires, real decisions, real people who need responses. The structural shift that works is treating the deep work block as the fixed point around which everything else schedules, rather than the other way around. Reactive work expands to fill whatever space it's given. It needs a container, not access to the whole calendar.
→ Best Productivity Apps for Founders and Entrepreneurs
Developers need longer continuous blocks than most roles because of how much context has to be held in working memory at once. Reasoning about a complex codebase, tracking the implications of a change, and writing code that actually solves the problem correctly requires building up a mental model that takes time and collapses quickly under interruption. A developer interrupted every 45 minutes can produce code. They can't consistently produce the quality of reasoning their role requires.
→ Best Mac Calendar Apps for Developers
Writers and researchers often face an internal version of the distraction problem as much as an external one. The pull to research one more thing, check one more source, read one more article before starting is a form of task avoidance that looks like preparation. The block needs to be treated as execution time, not extension of the preparation phase.
→ Best Time Blocking Apps for Writers
People with ADHD often find that the rigid version of deep work scheduling creates more problems than it solves. Time-blindness makes strict minute-by-minute structure feel punishing rather than protective. The research suggests flexibility inside the session — protecting the block at the container level while allowing what happens within it to be responsive — tends to work better than a schedule that doesn't account for how ADHD attention actually functions.
The methods that support it
Deep work isn't a productivity method. It's the outcome that good methods are trying to protect. A few of them address different parts of the same problem.
GTD handles the open loops — all the unfinished commitments and unresolved tasks that create attention residue and mental noise during the block. A reliable system where everything is captured and every open task has a clear next action reduces the background cognitive load that makes concentration harder to maintain.
The Eisenhower Matrix helps with the decision that comes before the block: what to actually spend the deep work time on. It separates important from urgent, which is the distinction that matters when choosing between the work that generates real output and the work that feels pressing.
Time blocking is the direct structural support for deep work — scheduling exactly when you'll do a task, rather than keeping it on a to-do list and hoping time appears.
→ How to Time Block Your Day, Time Blocking Template
The weekly review is how the practice gets better over time. Looking at what actually happened last week — which blocks completed, which got eroded, where the time actually went — creates a feedback loop that makes the following week structurally better.
→ Weekly Review and Planning Rituals
The shutdown ritual is the part most people skip, and it matters more than it sounds. A deliberate end to the working day — reviewing what's open, deciding what moves to tomorrow, and formally closing — is what allows genuine psychological detachment from work during the hours that are supposed to be recovery. Research across 26,000+ participants found that psychological detachment during off-hours is the single strongest predictor of reduced fatigue. You can't sustain concentrated work without real recovery, and recovery requires actually stopping.
The tools question
Tools matter less than most people assume when they first start thinking about deep work. The conditions that enable concentration are mostly environmental — protected blocks in the calendar, notifications off, one task visible on screen. These things matter more than which specific app creates the calendar block.
Where tools do vary meaningfully is in the specific things that determine whether a practice holds over time. Whether the tool makes it easy to create and protect named blocks. Whether it reduces the decisions required at the moment the block starts. And whether it shows you the gap between what you planned and what you actually completed — the feedback that makes a practice improve rather than just repeat.
Most scheduling tools do the first. Very few do the third. And the third is where most deep work practices quietly erode.
→ Best Deep Work Apps for Mac → Best Deep Work Scheduling Apps 2026 → Best Focus Apps for Mac
What actually breaks most deep work practices
The failure mode isn't usually a lack of commitment. It's structural — a mismatch between how the working day is set up and what concentrated effort actually requires.
The block scheduled immediately before a meeting. The task named as a category rather than a specific output, leaving the decision of what to do until the moment the session starts. The afternoon block that has to compete with a depleted attention system. No weekly view to show that meeting creep has been gradually eating the protected hours over the past month. No shutdown ritual, so the open loops of today bleed into the evening and the recovery that makes tomorrow's concentration possible never quite happens.
These aren't discipline failures. They're design problems. The research on interruption, attention residue, decision fatigue, and habit formation describes what the conditions for deep work actually are. Getting there is mostly a question of building those conditions into the structure of the day rather than relying on willpower to create them moment by moment.
The people who sustain a deep work practice over time tend to share one thing: they treat the conditions for good work as something worth designing, not something that will naturally appear when everything else is handled.
Related reading:
Last updated: April 2026