How to Actually Do Deep Work: Run a One-Week Audit in 6 Steps

Most knowledge workers don't have a motivation problem. They have a calendar problem.

That's Cal Newport's argument in Deep Work: the work that creates the most value — the hard problem, the important draft, the design that has to be right — requires long stretches of distraction-free concentration, and modern schedules are built to prevent exactly that. What's left is shallow work: email, chat, status meetings, and the feeling of a full day with nothing finished to show for it.

Reading that argument takes a weekend. Running it against your actual week is the part nobody does. Here's the audit, step by step, using the six commands in the Deep Work skill for Claude Code (and other AI assistants). Budget about 80 minutes, and use last week's real calendar — not the week you wish you had.

Step 1: Audit where the hours actually went (/deep-work-audit)

Start with the honest baseline: a time audit with a deep/shallow split. Go through last week block by block and classify each one. Anything that could be done while distracted — inbox, chat, routine updates — is shallow. Anything that demanded your full, unbroken attention is deep.

Most people who run this discover the same ratio: deep work is a small minority of the week, and it arrives in fragments — 25 minutes here, 40 there — too short to reach the depth the valuable work needs. Write the ratio down. It's the number the rest of the audit exists to change.

Step 2: Find the leaks (/distraction-audit)

Next, a distraction elimination plan. List every interruption source that broke a work block last week: the chat channel you check reflexively, the phone on the desk, the drive-by question, the meeting that could have been a message.

The point isn't willpower — Newport is explicit that environment beats discipline. For each leak, the output is a structural fix: where the phone lives during a block, which notifications exist at all, and what your team or family can actually expect from you while you're in one.

Step 3: Build the week before it builds itself (/schedule-builder)

Now build the weekly deep work schedule: named blocks, at named times, for named work — placed before the shallow work gets a chance to claim the calendar. Newport's core scheduling insight is that deep work has to be decided in advance, by philosophy and by time block, or it loses every day to whatever shouts loudest.

Keep the first week modest. Two or three protected blocks you actually keep beat a heroic schedule you abandon by Wednesday. The audit in Step 1 tells you where the blocks can realistically come from — usually, out of the shallow hours you just counted.

Step 4: Design the on-ramp (/ritual-design)

Deep work sessions fail at the start, not in the middle. The pre-session ritual checklist removes the negotiation: same place, same starting routine, same rules for what happens when you get stuck, and a clear definition of what "done" looks like for this session.

A good ritual answers three questions before you sit down — where will I work, how will I work, and how will I support the work (coffee, materials, phone in another room)? Decide them once, in the checklist, instead of re-deciding them at the start of every block.

Step 5: Keep score on what you control (/scoreboard)

Build the tracking system with lead measures. The lag measure — "finished the big project" — arrives too late to change anything. The lead measure is the one you control daily: hours of true deep work completed this week, counted honestly against the schedule from Step 3.

Newport borrows this from execution research for a reason: people play differently when they're keeping score. A visible scoreboard turns deep work from an intention into a streak you don't want to break — and it makes the Step 1 audit repeatable, so next month's ratio is a measurement, not a guess.

Step 6: Shut down completely (/shutdown-ritual)

End the day with the shutdown checklist: capture every open loop, check the places tasks hide, decide what tomorrow's first block is, and then actually stop. Newport calls the endpoint "shutdown complete" — a phrase that sounds like a gimmick until you've felt the difference between an evening your brain spends rehearsing unfinished work and one it spends recovering.

The shutdown is also what makes Step 3 sustainable. Deep work blocks expand to fill a rested mind; they collapse under a tired one. A week of audits and rituals that leaves you checking email at 11pm has missed the point of the book.

The sequence matters

Run them in order: audit → distractions → schedule → ritual → scoreboard → shutdown. Scheduling before the audit produces a fantasy calendar; skipping the scoreboard produces a good week that never repeats. Each step uses the output of the one before it, and together they take about 80 minutes — roughly one of the deep work blocks you're about to start protecting.

Run it on your week

The Deep Work skill runs this full audit as six guided commands in your AI assistant, using your answers as the input — it's $7 one-time in the BookSkills library, and checkout no longer asks for an account first: you buy, download from the success page, and claim it into an account whenever you're ready. New to book skills? Start with the free Atomic Habits skill to see the format first. And if you end up running audits like this on a shelf of books, Annual Access unlocks all 43 skills for $79.99/year — it pays for itself at 12 single skills ($84 bought one at a time), so it's the right call only if you'll actually use a dozen or more.