What is deep work?
Deep work is work done with full focus and no interruptions on a task that is hard for your mind. Cal Newport defines it as “the act of focusing without distraction on a cognitively demanding task.” Email, chat and routine admin are shallow work by comparison.
Three things make a block deep: the task needs real thinking, nothing is allowed to interrupt it, and you know in advance what finished looks like. Take any one away and you have ordinary work. A study session with the phone on the desk is a study session. It is not a deep block.
The idea is useful because it gives you a word for something you can protect. It is not a method with guaranteed results, and the sections below keep those two things apart.
Deep work vs shallow work
The line is drawn by the task and the conditions, not by how busy you feel. Shallow work is still work, and most jobs need a lot of it.
| Deep work | Shallow work | |
|---|---|---|
| The task | Needs real thinking: a proof, a draft, a design, a hard bug | Logistics: replies, scheduling, forms, routine updates |
| Interruptions | Kept out until the block ends | Expected, often welcome |
| Finish line | Written down before you start | Usually “until the queue is empty” |
| Where it goes wrong | Booked as time, but filled with small tasks | Expands to take the whole day |
Where the idea comes from: Newport’s book
The term comes from Cal Newport. On the book’s page on his site, he states the thesis as the Deep Work Hypothesis: “Deep work is becoming increasingly valuable at the same time that it’s becoming increasingly rare.” The page describes Part One as the case for deep work and Part Two as strategies for doing it.
That makes the book an argument with examples, not a trial. It tells you why to protect time and offers ways to do it. It does not measure whether people who follow it produce more.
Four deep work techniques: how to schedule it
Summaries of the book (book notes at grahammann.net and SuperSummary) describe four approaches. We have not checked the wording against the book, so read this as the usual summary, not a quotation.
| Approach | The pattern | Fits when |
|---|---|---|
| Monastic | Remove or sharply cut shallow obligations | Your role allows it. The summaries call it impractical for most people |
| Bimodal | Defined stretches for deep work, the rest left open | You can set aside whole days or blocks |
| Rhythmic | A regular habit, so you do not decide each time | Your schedule is fairly steady |
| Journalistic | Switch into deep work whenever free time appears | You already switch fast. The summaries say it is not for beginners |
Newport’s own page links to separate posts on time blocking, fixed-schedule productivity and depth rituals, so treat the four above as a menu, not a fixed list.
What the research supports, and what it does not
The strongest support is for something narrower than the book’s promise: interruptions cost something.
Interruptions are not free
In a laboratory study, Gloria Mark, Daniela Gudith and Ulrich Klocke (2008) asked 48 people to answer work emails in blocks of 12 under three conditions: no interruptions, interruptions on the same topic, and interruptions on a different topic. Interrupted people finished sooner, with no difference in quality. They also reported more stress, frustration, time pressure and effort. The authors read this as people speeding up to make up for the interruptions, at a price. The topic of the interruption made no difference.
The same paper found that two personality measures, openness to experience and need for personal structure, predicted how costly interruptions were for a given person. So the size of the cost is not the same for everyone, which is a reason to test it on yourself.
Attention can stay behind
Sophie Leroy (2009) gave this effect a name: attention residue, where part of your attention stays on the task you just left. Later summaries of her experiments report weaker performance on the next task when the first was left unfinished. That fits the advice to end a block with a note on where to pick up. We cite the paper for the idea and its direction, not for how large the effect is.
What the evidence does not show
- That a certain number of deep hours a day improves your output. Neither study tests it.
- That the email task in a university lab carries over to long, hard thinking.
- That any particular block length is best. The lengths people use are habits, not findings.
Deep blocks for students, developers and professionals
The idea is the same. What counts as a hard task and what interrupts it differs by role.
Students
The hard task is usually something you cannot do half-attended: working a problem set, writing an argument, or learning material that is new to you. The interruptions are the phone and the group chat. A good finish line is concrete: “Solve problems 4 to 9, each with a worked answer or a marked question for office hours.” NEDIO’s student set offers Read, Write, Solve, Revise, Plan. See the study timer for students.
Developers
The hard task is a bug you cannot yet explain, a design that does not fit, or a change that touches several parts. The interruptions are chat, review requests and notifications. A good finish line is something you could show: “A failing test that reproduces the nightly import skipping rows.” NEDIO’s developer set offers Code, Debug, Plan, Review, AI Agent. The deep work guide for developers goes further, with a calendar calculator and a block planner.
Professionals
The hard task is a plan, a report, an analysis or a piece of writing that needs one long line of thought. The interruptions are meetings that land in the middle, messages and email. A good finish line is a draft you can react to: “A one-page draft exists and the open questions are listed.” NEDIO’s professional set is the one with a mode called Deep Work, next to Write, Review, Plan, Admin. The student and developer sets use other names, and a deep block there is simply a sprint with a hard goal.
Start with one block
Do not rebuild your week. Run one block and see whether it reached its finish line.
- Pick one task that needs thinking. If it takes no thought, it belongs in a shallow slot.
- Write the finish line. Something you could show another person when the block ends.
- Choose a length. NEDIO’s presets are 15, 25, 45, 60, 90 minutes. Nothing in the research above says which is best, so treat the length as a guess about your own work.
- Close the exits. Phone out of reach, chat muted, one window open.
- Stop when the timer ends and leave a note. Write what exists, what is unclear and the next action.
Block: 60 minutes
Goal: the one thing this block is for
Done when: something you could show another person
First action: the very first thing you will open or write
Exits closed: phone away, chat muted, one window
Before I stop, write:
Done: what exists now
Unclear: what I still do not know
Next action: the first step for the next blockCopy the card into any notes app. If you would rather use a timer, this link opens a 60-minute professional block with a goal and finish line filled in, which you can edit before you start:
How to tell whether it is working
Keep one count: blocks started, and how many reached their finish line. Write it with both numbers, such as “3 of 5”, not “most of them”. A number without its denominator is not evidence.
One week is too little to judge. With five blocks a week and a true rate near 60 percent, the 95 percent interval around a week’s result is about ±43 percentage points (1.96 × √(0.6 × 0.4 ÷ 5)). That is NEDIO’s own arithmetic, not a published study. In practice, “3 of 5” one week and “4 of 5” the next tell you nothing about whether a change worked.
So change one thing at a time, keep the count for several weeks, and compare with the weeks before. If the count rises after a change, that is a lead to keep testing, not proof. NEDIO’s close-out lets you mark the outcome of each block as completed, partial or not completed; that is your own mark, and NEDIO does not verify it.
What we do not know
- Whether protected blocks raise measured output for students, developers or anyone else.
- How large attention residue is outside the laboratory, and for long, hard tasks.
- Which block length works best for you. That is an experiment, not a finding.
- What the book says line by line. This page relies on Newport’s own description of it and on published summaries, not a full reading.
One disclosure: NEDIO sells a sprint timer, so we have an interest in you using one. The card above works without it, and the advice here does not depend on any product.
Conclusion
Deep work is a useful name for a hard task, no interruptions and a written finish line. The book argues for it; the studies support the narrower point that interruptions cost something and that the cost differs from person to person. Whether deep work improves your output is a question you can only answer with your own counts.
Next step: run one block this week and write down “reached its finish line” or “did not”. If you are a developer, continue with the developer guide. If you study, see the student timer.
Primary sources and references
These papers are linked through their DOI records. They support the points about interruptions and attention on this page; neither tests deep work itself. Newport’s book page and the two book summaries are linked in the text.
- Mark, G., Gudith, D., & Klocke, U. (2008). “The cost of interrupted work: More speed and stress.” Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, 107–110.
DOI: 10.1145/1357054.1357072
A laboratory experiment with 48 people answering work emails. Interrupted people finished sooner with no difference in quality, and reported more stress, frustration, time pressure and effort. It tests interruptions in an email task, not deep work itself.
- Leroy, S. (2009). “Why is it so hard to do my work? The challenge of attention residue when switching between work tasks.” Organizational Behavior and Human Decision Processes, 109(2), 168–181.
DOI: 10.1016/j.obhdp.2009.04.002
The paper that introduced the term attention residue. Later summaries of its experiments report weaker performance on a second task after leaving a first one unfinished. This page cites it for the term and that direction, not for effect sizes.
Frequently asked questions
What is deep work?
Deep work is work done with full focus and no interruptions on a task that is hard for your mind. Cal Newport, who coined the term, defines it as “the act of focusing without distraction on a cognitively demanding task.” Email, chat and routine admin are shallow work by comparison.
What is the meaning of deep work?
The phrase names a way of working, not a mood. It points to demanding tasks done in protected time, set against shallow work that needs little concentration. Newport’s argument is that deep work is becoming more valuable and more rare. That is his claim, not a measured result.
Is deep work the same as flow?
No. Deep work describes how you set up the work: a hard task, no interruptions, a fixed window. Flow usually refers to an experience of full absorption. You can do a deep block and not feel absorbed, and this page does not claim that a deep block produces flow.
How many hours of deep work can you do in a day?
We have no figure we can source, and Newport’s own book page gives none. Numbers quoted elsewhere trace back to summaries. Start with one block you can finish, count how many reach their finish line over a few weeks, and adjust one thing at a time.
Is deep work the same as focus?
Focus is the wider word: attention on anything. Deep work is narrower. It means attention on a cognitively demanding task, with interruptions kept out for the whole block. You can focus on an easy task for hours and still not be doing deep work.