Deep Work for People Who Write All Day: The Rules, a Daily Setup, and Where Stray Thoughts Go

Most advice about deep work assumes your job is one big project and a few annoying emails. For a lot of people it is the other way round. Your day is replies, updates, tickets and threads, and somewhere in there is one document that actually matters and never gets written.

This guide explains deep work in plain terms, then turns it into a setup for writing-heavy days: the rules, a scheduling style, a sample week, a place for stray thoughts, and a shutdown ritual that ends the day cleanly.

What is deep work?

Deep work is focused, distraction-free time spent on cognitively demanding work, such as writing a proposal, designing a system or solving a hard problem. Computer science professor Cal Newport popularized the term in his 2016 book Deep Work. Its opposite, shallow work, is logistical work like email and chat. The method protects blocks of deep work and batches the shallow rest.

In Newport's framing, deep work is the kind of effort that pushes your thinking to its limit. It improves your skills, creates something new and is hard for someone else to copy. The deep work meaning, in one line: the hard, valuable part of your job, done without interruptions.

The deep work definition has two parts that people tend to forget. The first is the work itself, which must be demanding. The second is the setting, which must be free of distraction. A hard task done with chat open in the next window does not count, and an easy task done in silence does not count either.

What deep work is not

Deep work is not the same as flow. Flow is a state of mind that you might fall into. Deep work is a practice you schedule, whether or not the session feels effortless.

It is also not working longer hours. Ten hours of bouncing between tabs is still shallow. The goal is a smaller number of protected hours that produce more.

Here is what deep work looks like in a job that is mostly writing:

• Drafting a strategy doc or a quarterly plan from a blank page.
• Writing a careful reply to a hard customer escalation, where tone and facts both matter.
• Preparing a design review or a decision memo that weighs real trade-offs.
• Rewriting a messy process document so a new hire can follow it.

Deep work vs shallow work

Shallow work is logistical. You can do it while a little distracted, and someone new could learn to do it quickly. Inbox triage, status pings, scheduling and routine ticket replies all land here.

Shallow work is not bad. It keeps teams moving, and much of it is part of the job. The point of deep work vs shallow work is not to delete the shallow side. It is to cap it, batch it and keep it out of the hours you set aside for the hard stuff.

Newport offers a simple test for sorting a task. Ask yourself how long it would take to train a smart new graduate, with no special training in your field, to do it. If the answer is days, it is probably shallow. If it is months or years, it is probably deep.

Why does this matter so much for writing-heavy roles? Because the shallow side never runs out. Microsoft's Work Trend Index report on the infinite workday says its telemetry shows Microsoft 365 users are interrupted every 2 minutes, on average, by a meeting, email or notification. Without a plan, the replies fill every gap.

The four rules of deep work, in practical terms

Newport's deep work rules are short enough to fit on a sticky note:

1. Work deeply.
2. Embrace boredom.
3. Quit social media.
4. Drain the shallows.

Each one sounds abstract until you translate it into a normal workday. Here is what each rule means for someone who writes all day, plus one action to try.

Rule 1: Work deeply

Willpower runs out, so Newport says to build routines that make focus the default. Decide where you work, when you start, how long the block lasts and what you will produce. The fewer choices you face at the start, the easier it is to begin.

Try this: name tomorrow's block after its output, such as "Draft the onboarding guide, sections 1 to 3." A named output is easier to start than a vague "focus time."

Rule 2: Embrace boredom

If you reach for your phone every time you wait in line, your brain learns that any dull moment deserves a new input. Then, in the middle of a hard paragraph, it asks for the same thing. Newport's advice is to train your attention by being bored on purpose.

Try this: when a block hits a hard spot, do not open a new tab. Park the stray thought in your capture place (more on that below), and stay with the document for two more minutes. The urge usually passes.

Rule 3: Quit social media (or rather, choose tools on purpose)

Newport's third rule is famous for its title, but its core idea is softer. Keep a tool only if its benefits to the things you care about clearly outweigh its costs. "It might be useful someday" is not enough.

Try this: list the apps open on your work computer right now. For each one, write down what it does for your main goals this quarter. Close or mute the ones you cannot justify, at least during your deep work block.

Rule 4: Drain the shallows

You cannot remove shallow work, but you can shrink it. Newport suggests planning your day in blocks and agreeing on a rough shallow work budget, the share of your hours that should go to logistics. Once it has a budget, shallow work stops creeping into everything.

Try this: pick fixed shallow windows, such as three per day, and handle email, chat and tickets only inside them. The sample week below shows one way to place them.

Pick a deep work philosophy that fits your calendar

Knowing the rules is not the same as knowing when to do the work. Newport describes four scheduling philosophies. Each one fits a different kind of job, and picking the wrong one is a common reason people give up after a week.

Monastic. You remove almost all shallow work and spend most of your time on one deep goal. This suits writers, researchers and others whose value comes from one kind of output. For most people with a team and an inbox, it is not realistic.

Bimodal. You split your time into long deep stretches and normal stretches. The deep part might be two full days a week, or a few weeks each season. It suits people who can control whole days, such as consultants between client projects.

Rhythmic. You do deep work at the same time every day, such as 8:30 to 10:00 each morning. The habit carries you, so you do not have to decide each day. It suits most knowledge workers with meeting-heavy afternoons.

Journalistic. You drop into deep work whenever a gap opens up. Newport named it after journalists who are trained to switch into writing mode on deadline. It suits people with unpredictable days, but it takes practice to start cold.

For most people in reactive, writing-heavy jobs, rhythmic is the best default. Habit beats willpower, so a fixed time removes the daily debate about when to start. Colleagues also learn the pattern quickly. After a couple of weeks, people stop expecting a reply from you at 9:00 and start expecting it at 10:00.

How long should a deep work session be?

Newport's estimate is that a beginner can sustain about an hour of deep work a day. With practice, he suggests, people can reach around four hours, and rarely more. Treat those numbers as his estimate from experience, not as a research finding.

In practice, start with one block of 60 to 90 minutes. That range is a common recommendation, not a rule, but it is long enough to get past the slow start and short enough to protect on a busy calendar. Add a second block only once the first one happens reliably for a few weeks.

Some people use the 3-3-3 rule of thumb, which is usually credited to the writer Oliver Burkeman. You spend about three hours on your most important project, then do three shorter urgent tasks and three maintenance tasks. It pairs well with deep work: the three hours are the deep part, and the other six items are the shallow work you batch.

If three hours sounds impossible right now, that is normal. The point of the rule is the shape of the day, not the exact number. One protected hour plus a short list of small tasks is already a good day.

A deep work week for people who write all day

Here is a deep work schedule for a manager or PM who has a daily standup, recurring meetings and a steady stream of messages. It uses the rhythmic philosophy, one morning block and three shallow windows a day.

Between the shallow windows, chat and email stay closed. Meetings still happen where they are booked. The rule is simple: nothing shallow happens inside the deep block, and replies wait for the next window.

Protect the block on your calendar

Book the deep block as a real calendar event and name it after the output, such as "Draft Q1 plan." A named event is harder for others to book over than an empty slot, and it reminds you what you agreed to produce. Add the status line from the section below to the event description.

For the length of the block, turn on a Focus on Mac or Do Not Disturb in Windows so notifications stay quiet.

Batch shallow writing into fixed windows

In the sample week, the 10:00, 13:30 and 16:30 windows are where email, chat and ticket replies go. Each window is a short sprint: open the inbox, reply, close it. If a reply needs real thought, it is not shallow, so move it to tomorrow's deep block.

Because shallow work in these jobs is mostly writing, the windows can feel like a second job. One way to lighten them is to speak short replies instead of typing them. With VoiceSnap Pro you click into the reply, hold the dictation shortcut (Right Option on Mac, Right Alt on Windows), speak, release, and the punctuated text is typed at the cursor in any app. The dictate-in guides cover specific apps like email clients and chat tools.

Whether speaking is faster for you depends on how you type and how you think out loud. General research figures for typing and speaking speeds are collected in our guide to average typing speed; treat them as general figures, not product benchmarks.

Tell people when you are reachable

A deep block works best when colleagues know when you will answer. A short status line or a calendar note is enough, and it stops the "did you see my message?" follow-ups. Keep it friendly and specific.

Heads down on the Q1 plan from 8:30 to 10. I reply to messages at 10, 1:30 and 4:30. If something is truly urgent, call me.

Set the line once and reuse it every day. After a week or two, most people stop needing it.

Where stray thoughts go during a block

Here is the problem every deep work session runs into. Twenty minutes into the draft, you remember an email you owe, a bug you saw yesterday or an idea for a different project. If you open a new tab or the chat app to note it down, the block is broken. If you do not write it down, it keeps nagging.

That nagging has a name. Unfinished tasks tend to stay on your mind until you close them or make a plan for them, which is the core of the Zeigarnik effect. Switching away has a cost too: Sophie Leroy's research on attention residue found that part of your attention stays stuck on the previous task after you switch.

The fix is a capture inbox that exists only for the block. It follows four rules:

• One place. A single list, notepad or note, not three.
• One action. Write the thought in a few words and go back to the document.
• No organizing during the block. No tags, no due dates, no replies.
• Processed later. You empty the inbox in the next shallow window of the sample week, never during the block.

Paper on the desk works perfectly well. A notepad next to the keyboard never sends a notification. The only requirement is that writing a thought down takes a few seconds and does not open anything that pulls you in.

A voice note is another option. In VoiceSnap Pro you hold Right Command on Mac or Right Ctrl on Windows, say the thought and release, and it is saved as a note in your account to sort later. To record hands-free, press Control+Option+N on Mac or Ctrl+Alt+N on Windows instead; see how voice notes work.

Capturing a thought is not the same as remembering it. Handing memory to notes has real trade-offs, which our piece on cognitive offloading covers in detail. For a single deep block, though, the trade is almost always worth it: the note holds the thought for an hour so your head can hold the draft.

It also helps to empty your head before the block starts. A two-minute brain dump by talking clears the obvious worries so fewer of them show up at minute twenty.

The shutdown ritual: end the day with nothing open

Deep work is not only about the morning block. How you end the day decides how you start the next one. Newport describes a daily work shutdown ritual: he reviews his open tasks, checks his calendar and plan, and closes the day with a set phrase, "schedule shutdown, complete."

The phrase sounds silly, and he admits as much. Its job is to mark a clear line. Once you have said it, you know you checked everything, so a work thought in the evening does not need your attention until tomorrow.

Newport suggests a good shutdown ritual has three parts: a quick set of steps you can finish in about five minutes, a phrase that marks the end, and an agreement with yourself that the phrase means work is done. Here is a five-step version for a text-heavy job:

1. Clear the capture inbox. Go through every stray thought from the day. Turn each one into a task, a reply or nothing.
2. Flag replies for the first shallow window. Anything you owe someone goes on a short list for tomorrow's 10:00 window, so it is not floating in your head overnight.
3. Write the first sentence of tomorrow's deep work task. Open the document and leave one line to continue from. Starting from a sentence is much easier than starting from a blank page.
4. Check tomorrow's calendar block. Make sure the 8:30 block is still there and that nobody booked over it. Move it now if you must, not at 8:29 tomorrow.
5. Close everything and say the phrase. Close the inbox, chat and every tab. Then say your phrase, whether that is "shutdown complete" or anything else that works for you.

At first, the whole thing may take ten minutes. After a week, it usually takes five. If you want a record of the day, you can also say a short three-line log out loud before you close up, an idea borrowed from interstitial journaling.

The shutdown ritual is the step people skip most often, and it is the one that makes the rest stick. Without it, open loops travel home with you, and the next morning starts with the inbox instead of the block.

Common deep work mistakes

Most people who try deep work and drop it make one of a handful of mistakes. Each has a simple fix.

• Taking meetings into the block. You schedule the block, then accept an invite on top of it "just this once." Fix: treat the block like a meeting with someone important, and offer a different time.
• Treating email as deep work. A long inbox session feels hard, but it is still shallow. Fix: use the graduate test from earlier, and move real thinking out of the inbox into a document.
• No capture place, so you tab out. Every stray thought becomes a trip to another app. Fix: put one notepad or one note next to the document before the block starts.
• Blocks too long at the start. A three-hour block on day one usually ends early and feels like failure. Fix: start at 60 to 90 minutes and grow only when it holds.
• Skipping the shutdown. Work leaks into the evening, and the morning starts in the inbox. Fix: put a 15-minute shutdown event at the end of each day.
• Measuring hours instead of output. Sitting in a quiet room is not the goal. Fix: name each block after what it should produce, and check at the end whether it did.

If you only fix one of these, fix the meetings. A deep block that moves every day is really a journalistic schedule in disguise, and that is the hardest one to keep.

It also helps to remember what interruptions really cost. In a study of interrupted work, Gloria Mark and colleagues found that people made up for interruptions by working faster, but with more stress and frustration. Protecting the block is not about being precious. It is about doing the same work with less strain.

Frequently Asked Questions

What does deep work mean?

Deep work means focused time on demanding work with no distractions. Cal Newport, who popularized the term, describes it as effort that pushes your thinking to its limit and creates value that is hard to copy. Its opposite is shallow work, such as email and chat.

What are the four rules of deep work?

The four rules are work deeply, embrace boredom, quit social media and drain the shallows. In practice, that means building routines for focus, resisting the urge to fill every dull moment, keeping only tools that clearly earn their place, and capping shallow work with a budget and fixed windows.

How much time should you spend on deep work each day?

Start with one block of 60 to 90 minutes a day. Newport estimates that beginners can manage about an hour and experienced people around four hours, but those are his estimates rather than research results. Add a second block only once the first one is a steady habit.

Can you give me an example of deep work?

Writing the first draft of a quarterly plan with chat and email closed is a good example. So is working out the cause behind a hard support case, or writing a decision memo that weighs real trade-offs. Replying to routine messages, even many of them, is shallow work.

How do you go into deep work?

Pick a fixed time, close chat and email, and name the block after what you will produce. Keep one capture place next to the document for stray thoughts. If you start each block the same way, the routine does most of the work of getting you focused.

Start with one block tomorrow

You do not need a new system to begin. Book one deep block for tomorrow morning, put one capture place next to the document, and end the day with a short shutdown. That is the whole method, at the smallest size that still works.

Once that feels normal, add the shallow windows and the status line. Then, if your calendar allows, add a second block.

If you want a quick way to capture stray thoughts and speak short replies, VoiceSnap Pro is free to start, no card: Download free.