How to Do Deep Work: Plan, Protect and Track Your Deep Work Sessions

Most of what makes you valuable, whether you're a student, a developer, a writer or a researcher, comes from a small number of hours of hard, focused thinking. Cal Newport called this deep work in his 2016 book of the same name: focused, distraction-free work on cognitively demanding tasks.

The trouble is that deep work doesn't happen by accident. It needs to be planned, protected and practised. Here's how.

Deep work vs shallow work

Shallow work isn't bad; it's necessary. The problem is that it expands to fill your day unless deep work has protected time of its own.

Step 1: Decide what deserves deep work

List the two or three tasks that would make the biggest difference this week. These get your deep sessions. Everything else is shallow work to batch into lower-energy times.

Step 2: Schedule sessions in advance

Put deep work on your calendar as if it were a meeting with your most important client. Common approaches:

• Daily rhythm: the same block every day, for example 9:00 to 11:00. The easiest to sustain.
• Bimodal: whole days (or half-days) dedicated to deep work, others for shallow work.
• Opportunistic: grabbing deep sessions whenever time opens up. Hardest for beginners.

For most people, the daily rhythm wins. Put it at your best time of day; if you don't know when that is, track your sessions for two weeks and look.

Step 3: Choose your session length

Some deep tasks don't fit fixed blocks. A count-up timer lets you keep going while you're in the zone and take a proportional break when you stop. See Flowtime vs Pomodoro and how to choose your session length.

Step 4: Build a start ritual

Rituals reduce the friction of starting. Make yours the same every time:

1. Same place. A desk, a library seat, a particular café.
2. Clear goal. Write what “done” looks like for this session.
3. Phone away, notifications off, email and chat closed.
4. Everything ready: water, notes, files open.
5. Same cue: start the timer, put on the same focus sound.

Step 5: Protect the session

• Turn on Do Not Disturb for the whole block.
• Tell people when you're unavailable, and when you'll be back.
• Keep a “later” list for anything that pops into your head.
• Don't switch, even for “quick” checks. Every switch leaves attention residue.

Step 6: Batch your shallow work

Deep work gets easier when shallow work has a home too. Schedule two or three short blocks a day for email, messages and admin. Use the classic 25-minute Pomodoro for these: it keeps them contained.

Step 7: Shut down properly

At the end of the day, write down where you stopped and what's next. Newport recommends a shutdown ritual: review open tasks, plan tomorrow, and then genuinely stop. Rest is what makes tomorrow's deep work possible.

Step 8: Measure your deep hours

The simplest deep work metric is hours of deep work per week. Track it, set a target and try to grow it slowly. Around 3 to 4 hours a day is a strong level that most people can't exceed for long. If you're starting from 30 minutes a day, getting to two hours is a big win.

Tag your sessions by project or category so you can see whether your deep time is going to the work that matters most.

Common deep work mistakes

1. Starting too long. Jumping straight to 2-hour blocks usually fails. Build up.
2. No clear goal. “Deep work on the project” drifts. Define the outcome.
3. Leaving a door open. One open chat window is enough to break the session.
4. Skipping recovery. Breaks, sleep and downtime are part of the system.

Developers have their own particular challenges with deep work. Read the Pomodoro Technique for programmers. And if your attention needs rebuilding first, start with how to improve your focus.