Skip to main content
PProfileMatch

Time Blocking and Deep Work: Plan a Focused Day

Soft SkillsLesson 2 of 45 min read

What you'll learn

  • Explain time blocking and what deep work means
  • Build a realistic time-blocked schedule with buffers
  • Protect focus time and batch shallow tasks like email and chat
  • Adjust the plan when the day goes wrong

On this page

  1. What time blocking and deep work are
  2. Plan a focused day, step by step
  3. Protecting your focus
  4. Worked example: when the plan breaks
  5. Common mistakes
  6. How this shows up in interviews and on the job
  7. How to practise

A to-do list tells you what you have to do. It does not tell you when. When the work has no time slot, it loses to whatever is loudest, and you reach 5 pm having answered 40 messages and written no code, analysis or report.

What time blocking and deep work are

Time blocking means assigning tasks to specific blocks in your calendar instead of working from an open list. Deep work is a term from author Cal Newport for focused, distraction-free work on cognitively demanding tasks. Writing code, analysing data, drafting a proposal and studying for an exam are typical examples. Shallow work is the logistical stuff: email, chat, scheduling, small admin.

Combining the two is simple: put your deep work in protected blocks, put shallow work in smaller batches around it, and leave space for the unexpected. This way you decide in advance when you will focus, rather than hoping a free hour appears.

Plan a focused day, step by step

  1. Choose your one to three outcomes for tomorrow, using the Eisenhower matrix if needed. Not 12 tasks; the things that make the day a success.
  2. Know your fixed points. Add meetings, standups and deadlines to the calendar first.
  3. Place deep work in your best hours. For many people that is the morning, but it varies; use the time you tend to think most clearly.
  4. Estimate generously and add buffer. Tasks usually take longer than expected. Leave 20 to 30 per cent of the day unplanned, or at least 15 minutes between blocks.
  5. Batch shallow work. Check email and chat at set times, for example 11:30 and 4:00, instead of continuously.
  6. Name each block with a specific output, such as "Draft the API section" instead of "Work on project".
  7. Review at the end of the day and move unfinished blocks. This takes five minutes and makes tomorrow's plan.
TimeBlockType
9:00-9:15Plan the day, check calendarPlanning
9:15-11:15Build the invoice export (write code + tests)Deep work
11:15-11:45Email, Slack, reply to QAShallow batch
11:45-12:30Code review for Sam's PRMedium focus
12:30-1:30Lunch, away from the screenBreak
1:30-2:30Team meeting and standup follow-upMeetings
2:30-4:00Buffer for bugs and unexpected requestsFlex
4:00-4:30Email, Slack, plan tomorrowShallow batch

Protecting your focus

A deep block only works if you remove the obvious interruptions. Close the email and chat apps, put your phone in another place, and mute notifications. Tell people when you will be back: a status like "Focus until 11:15, will reply after" is usually accepted by teammates. If your job is truly interrupt-driven, such as support or on-call, block smaller sessions of 25 to 45 minutes and protect those instead.

Scripts for protecting a block
Slack status:
"Focus mode until 11:15. Urgent? Call me."

To a teammate who walks up:
"I'm in the middle of something until 11:15. Can I come to you then?"

To a manager (when a new request arrives mid-block):
"I can look at it at 11:15 after my current task. If it needs to happen
right now, which task should I pause?"

Worked example: when the plan breaks

At 10:00 a production issue interrupts your 9:15 to 11:15 deep block. This is not a failure of time blocking; the buffer exists for this. Fix the issue, then re-plan on the spot: move the deep block to 2:30 to 4:00 (the flex block), shorten shallow batches, and tell your manager what has moved. The skill is re-planning calmly, not keeping the original schedule.

A student can use the same idea: block 90 minutes of study in the morning for the hardest subject, a lighter block for assignments after lunch, and fixed breaks. Put the phone in another room for the block, not just on silent.

Common mistakes

  • Over-planning. A schedule with no gaps breaks at the first interruption, and then you drop the whole system.
  • Vague blocks. "Work on project" does not tell you where to start. Name an output.
  • Underestimating tasks. If you always run over, multiply your estimates for a week and see how it fits.
  • Copying someone else's routine. The morning-only deep work advice does not suit everyone. Test your own energy for a week.
  • Expecting deep work in an open, interrupt-heavy role. In some jobs, being responsive is the job. Adapt the idea rather than forcing it.
  • Treating it as a rule instead of a tool. If a plan is not working, change the plan.

How this shows up in interviews and on the job

Interviewers ask, "How do you plan your day?" or "How do you handle competing deadlines?" A concrete answer, such as "I block the morning for focused work, batch email twice a day and keep a buffer for surprises", is more convincing than "I am very organised". Use STAR for the story behind it.

On the job, a visible calendar helps managers see your capacity. It also makes it easier to renegotiate: "My week is blocked for the release; I can pick this up Thursday." See saying no and managing workload.

How to practise

Tonight, plan tomorrow in 10 minutes: pick one outcome, schedule one 60 to 90 minute focus block, schedule two shallow batches, and leave a 30-minute buffer. Tomorrow, note where the plan broke. Use that to improve the next day's plan, not to judge yourself.

Try it yourself

Plan tomorrow in a calendar or on paper. Include one deep-work block of 60 to 90 minutes with a named output, two shallow batches for email and chat, and a 30-minute buffer. At the end of tomorrow, write down one thing that did not go to plan and how you would adjust it.

Show a hint

If your day is meeting-heavy, find the longest gap and protect that one. Even 45 minutes counts.

Key takeaways

  • Time blocking assigns tasks to calendar slots; deep work (Cal Newport's term) is focused work on demanding tasks.
  • Schedule fixed points first, protect one deep block, batch shallow work and leave buffer time.
  • Name each block with a concrete output so you know where to start.
  • Plans break; the skill is re-planning calmly and telling people what moved.

Test yourself

A trick from this lesson's ride: Deep work: brain fully on, door shut. Shallow work: logistics. Four more tricks like it wait along the route, each followed by a question.

Ride this lesson

Frequently asked questions

What is time blocking and how do I start?

Time blocking means putting tasks into specific slots in your calendar instead of leaving them on a list. Start by adding your meetings, then schedule one focus block for your most important task and a couple of short blocks for email and admin.

What does deep work mean?

Deep work is Cal Newport's term for focused work without distraction on cognitively demanding tasks, such as coding, analysis or writing. It contrasts with shallow work like email and quick chats.

How do I time block when my job has constant interruptions?

Use shorter blocks of 25 to 45 minutes, add buffer time, and let colleagues know when you are focusing. Where your role requires being responsive, block time for responding and protect smaller windows for your own work.