Some days end with a full calendar and little progress on work that required your sustained attention. Administrative threads close while the spec, analysis, or design that needed uninterrupted blocks remains unfinished.
Deep Work: Rules for Focused Success in a Distracted World, by computer science professor Cal Newport at Georgetown, splits professional work into two types: deep work and shallow work. In most modern workplaces, the boundary between deep and shallow work blurs fast. Deep work is cognitively demanding execution that compounds expertise and produces differentiated output. Shallow work is coordination, administration, and logistics that keep operations current but rarely advance primary outcomes.
Until you can tell the two apart, your calendar will keep winning and the hard work will keep waiting.
What is deep work?
In Deep Work, Newport defines deep work this way:
In practice, deep work is when you pick one complex task (usually among your most cognitively demanding tasks) and stay with it until that piece of work is done. You try not to jump to email, chat, or other jobs in the middle.
However, deep work tasks require unbroken focus in a distraction free work environment, and most modern workplaces rarely provide one by default. Gloria Mark, a UC Irvine researcher who tracked screen behavior over years, documents a steep decline in dwell time: 2.5 minutes per screen in 2004, 75 seconds by 2012, and a median near 47 seconds today.
When you get interrupted, one study found it can take about 23 minutes to get your focus back to where it was. That refocus tax can quietly consume the tail of an entire deep work session you still counted as something like “writing time.” People often call that multitasking, but usually it is just jumping between tasks very quickly. And that task-switching can cost you about 20-40% in lost productivity. Longer, quieter blocks also make a productive flow state more likely, because you are not paying that refocus cost after every ping.
Newport states the tradeoff directly: "Deep work is becoming increasingly valuable at the same time it is becoming increasingly rare. Therefore, if you cultivate this skill, you'll thrive." He labels this the Deep Work Hypothesis. He also warns that depth rarely feels rewarding in the opening minutes: you usually need more than an hour, and often ninety minutes or more, before the work stops feeling stiff and starts compounding.
What is shallow work?
Deep work pushes core priorities ahead. Shallow work keeps people coordinated and handles routine follow-through, including administrative tasks. Newport describes it as logistical, non-cognitively demanding activity, frequently performed under partial distraction, that contributes little novel value and is straightforward to replicate.
Common forms include repeated Slack triage, Jira field updates, status forwarding, and calendar negotiation. Most of that work clears small coordination issues and updates the shared record. A new hire can take on the bulk of it within the first week.
None of that is bad on its own. The problem is that shallow work is greedy: it expands to fill every gap in your day unless you actively stop it.
How much time does this actually eat? ICs spend 1.96 hours per day on unproductive task work (cycling through email, checking Slack, scrolling task lists without acting on them). That's nearly 10 hours a week of looking busy without producing anything.
What are the key differences between deep work and shallow work?
Deep work might ask a lot of you, and what you ship is hard to fake with a template. Shallow work is what survives in scraps between meetings. Most of it could sit with a colleague after a quick briefing.
Neither type is inherently good or bad. You need both. The question is proportion.
For ambiguous tasks, Newport has a quick test: "Could a recent college graduate be trained to do this relatively quickly?" If so, then that task probably falls under shallow work. If many years or some expertise is necessary, alongside some uninterrupted execution, then you're dealing with deep work.
Your brain pays a steeper price on genuinely complex work, so staying on one task pays off there. Simple, repetitive routines can still handle light switching without much penalty.
Nevertheless, if you don't block time for deep work first, meetings and messages will fill every open gap on your calendar.
What does deep work vs shallow work look like by role?
The line between deep and shallow work moves depending on what you do for a living. The cards below show sample tasks for four common roles.
How much of your day is deep work vs shallow work?
So, how much deep work do you actually get in a normal week? Most people think they get more than they really do. What they remember often runs ahead of what the calendar shows. About 61% of the average knowledge worker's day goes to shallow tasks. People average 2.9 deep work sessions a week but say they need 4.2 to feel on track.
- On average, people get 2.9 deep work sessions a week but say they need 4.2 to feel productive.
- 16.4% of workers get zero deep work sessions in a normal week.
- More than half (53.1%) get two sessions or fewer each week.
That pattern wears people down. 78.7% said they felt stress every week from too many tasks and not enough time. People in maker roles spend 12.1% of the work week catching up after priorities change. Only 53.5% of planned tasks get done each week, while the rest slides to the next week and the pile grows.
Few people plan to spend 61% of their week on coordination. Calls and chats fill the open space before anyone protects time for deep work. At that pace, a whole week may only leave a few hours for specs, analysis, or design work that needed quiet focus.
How do you rebalance deep work and shallow work in your schedule?
Shallow work cannot be eliminated, and attempting zero coordination is obviously counterproductive. The goal is to keep it from eating your best hours. Luckily, four simple scheduling habits can shift the mix.
1. Audit your current split
Before you try to change anything, just watch yourself for a week. Label each hour as deep work or shallow work and be honest! Our memory tends to flatter us. That is, we remember the focused stretches and blur over the coordination, the admin, the inbox. When you actually write it down, the picture usually shifts.
You're not alone if the numbers surprise you. There's a real gap between how productive people thought they were and what the data showed.
2. Schedule deep work first
Newport's "rhythmic" idea means you pick the same two or three-hour deep block every day. Treat that slot as fixed time for your hardest work during your most productive hours, before calls and chats take over. "I'll do it later" rarely works, so guard that block like a meeting you cannot move.
Newport says to cap hard focus at about 3 to 4 hours a day, which is usually the window when you can sustain something close to maximum cognitive function. After that, quality and energy tend to drop.
3. Batch shallow work into windows
When email and chat bleed through the day, focus keeps breaking. Instead, pick two or three short windows for inbox, Slack, and admin (for example after morning deep work and again before you sign off). People still hear from you on time, but your long blocks stay whole.
4. Defend your deep work blocks
Putting the block on your calendar is the easy part. The harder part is actually protecting it once it's there.
A few habits make a real difference. When the block starts, put your phone on Do Not Disturb, kill desktop notifications, and set a Slack status that tells people when you'll be back. Maybe something like "Heads-down until 11, will reply then." That last one matters more than it sounds. It's not about going dark. It's about giving people a clear expectation so they don't assume you're ignoring them. A two-hour window with a visible return time feels very different to a teammate than just... silence.
It also helps to put the block on a shared calendar. If it's invisible, it'll get booked over. If it's there and labeled, most people will work around it, especially if you've been consistent about showing up when you say you will.
Ultimately, you want to create a window that's genuinely protected without making yourself a liability to the people around you. Short, reliable, and visible beats long and unpredictable every time.
Protect your deep work hours 🔒
Deep work isn't something you set up once. Projects shift, meetings creep back in, and the calendar you protected last month quietly fills up again. It's just how it goes. The habit is running the loop: check the split, reclaim the blocks, batch the noise back into windows. Do that consistently, and the hours that matter stay yours.
