How-Tos Productivity Downloads About

Protect Deep Work Time

Your calendar is full, you answered forty messages, and the important work never started. Shallow work expands to fill every unprotected minute — the only fix is protection: scheduled, defended blocks where deep work happens. This is the practice that makes batching shallow tasks and cutting context switches actually stick.

A person working deeply on a real laptop in a quiet room, phone face-down and notifications silenced, a calendar on screen showing a blocked focus session, the person's.

TL;DR / Quick Fix

Quick fix: block two 90-minute deep-work sessions on your calendar like meetings — non-negotiable, notifications off, one task only. Shallow work expands to fill unprotected time, so protection is the strategy. Tell your team the hours; most interruptions can wait ninety minutes.

Follow these steps

  1. Define your deep work. Name the 2–3 tasks that actually move the needle — writing, designing, coding, thinking. If everything is “deep work,” nothing is.
  2. Block it like a meeting. Put two 90-minute blocks on the calendar, labeled and non-negotiable. A block that moves for every request is decoration.
  3. Kill notifications dead. Phone on Do Not Disturb, chat status set, email closed. Every ping is a context switch wearing a notification costume.
  4. Work on exactly one task. One block, one task, no tab-hopping. Single-tasking feels slow for ten minutes, then the depth kicks in.
  5. Communicate the boundary. Tell your team the hours and the escalation path for true emergencies. Boundaries people know about get respected; secret ones get trampled.
  6. Review and defend weekly. Each week, count how many blocks survived. Fewer than half means the system — not your willpower — needs adjusting.
A person performing step 1: Define your deep work. Name the 2–3 tasks that actually move the needle — writing, designing, coding, thinking.
Step 1 in action: Define your deep work. Name the 2–3 tasks that actually move the needle — writing, designing, coding, thinking. If everything is “deep work,

What NOT to do

  • Do not schedule deep work in your energy dip. Protect the hours, but put them where your brain actually works — audit with an energy audit.
  • Do not let “quick questions” in. A five-minute interruption costs far more than five minutes of focus.
  • Do not multitask inside the block. Music is fine; monitoring chat “just in case” is not deep work.
  • Do not skip the shutdown after. End each block by noting where to resume — tomorrow-you restarts in seconds.

Frequently asked questions

How long should a deep block be?

90 minutes is the sweet spot for most — long enough for depth, short enough to sustain. Beginners: start with 50.

What if my job is all interruptions?

Then protect one block, not five. Even a single daily deep hour compounds enormously over a month.

Is this just time blocking?

Time blocking is the calendar technique; deep work is what you protect with it. Related, not identical.

What to read next

About the author

By Juan Ibarra · Google IT Support Certified (Verified on Credly). See the About page for full author details.

Share this guide