Give the work a place in your week
A list says what; a calendar says when. Learn to block time for important work, estimate honestly despite the planning fallacy, and re-plan when the day breaks.
Time blocking
Giving specific tasks specific stretches of time in your calendar, and treating those blocks like appointments. It's the if-then plan from the last lesson with a clock as the cue: "At 9:30 on Tuesday, I draft the method section."
Not "work on thesis this week", but Tuesday 9:30–11:00 "draft method section, part 1" and Thursday 9:30–11:00 "draft method section, part 2".
Same tasks, two plans
List only
Twelve items, no times. Every hour you decide again what to do, and a message or a request usually wins. The report waits for a quiet moment that doesn't come.
Blocked day
9:30–11 draft the report. 12:15–12:45 email and messages. 2–3 admin in the afternoon dip. The rest open. The choices were made in advance, when you were calm.
Check yourself
Maryam blocks 9 to 11 every morning for her report. But whenever a colleague asks for a meeting in that slot, she says yes, and most weeks the report gets almost nothing. What should she change?
- Give up on blocking, since meetings will always win
- Treat it as a real appointment; offer another time
- Keep the block, and work on the report during the meetings
- Block even more hours so that a few of them survive
Show the answer
Treat it as a real appointment; offer another time
Yes. She'd never cancel a doctor's appointment because someone asked for a chat. "I'm busy then, how about 11:30?" works for most requests and keeps the block alive.
WHY BLOCKS OVERFLOW
The planning fallacy
We tend to underestimate how long our own tasks will take, even when we know similar tasks ran over before. Psychologists Daniel Kahneman and Amos Tversky named this the planning fallacy. We picture the task going smoothly and forget the interruptions, the dead ends and the parts we didn't think of.
In a classic study, students predicted when they would finish their thesis. On average it took them weeks longer than they'd guessed, only a minority finished by their predicted date, and even their "if everything goes wrong" estimates were too hopeful on average.
Estimate like someone who's been burned before
- Look back, not ahead
How long did a similar task actually take last time? That number beats your feeling about this time.
- List the parts
Write the steps out. Research suggests that spelling out the parts of a task tends to make estimates more realistic, because forgotten pieces show up.
- Add a margin
Give the task more time than your best guess, and more again if it's a kind of work you haven't done before.
- Check afterwards
Note how long it really took. Next time you'll have a real number to start from.
Check yourself
Ali's last three monthly reports each took about four hours. For this one he blocks two hours, because "this time I'll really focus". His block is probably too short.
Show the answer
True
True. "This time will be different" is the planning fallacy talking. His own track record, about four hours, is the best estimate he has. If he blocks four and finishes early, he gets time back; if he blocks two, the report spills into everything after it.
THE SHAPE OF A WEEK
Three kinds of blocks, and some empty space
Deep blocks for your chosen important tasks, in your peak hours, long enough to get past the warm-up; many people start with about an hour. Batch blocks for email, messages and admin, at set times. Buffer blocks: empty time for overruns and surprises. And leave part of each day unplanned, because something always comes up.
Name each deep block with a next action from the last lesson: "draft results, part 1", not "thesis". When the block starts, you already know what your hands will do.
Check yourself
Is each block ready to use, or does it need fixing?
- Tue 9:30–11: draft intro paragraphs 1 to 3
- Wednesday: thesis
- Daily 12:30–1: answer email and messages
- Every hour from 8 to 6 booked, no gaps
- Thu 4–4:30: buffer for anything that ran over
- Mon 2pm, in your usual slump: the hardest problem set
Show the answer
Ready to use: Tue 9:30–11: draft intro paragraphs 1 to 3, Daily 12:30–1: answer email and messages, Thu 4–4:30: buffer for anything that ran over
Needs fixing: Wednesday: thesis, Every hour from 8 to 6 booked, no gaps, Mon 2pm, in your usual slump: the hardest problem set
Check yourself
Match each problem to its fix
Show the answer
- Your blocks keep running over → Estimate from how long it took last time
- Small requests eat into your deep block → Batch them into a set block later
- You sit down to a block called "Project X" and stall → Name the block with a next action
- A long meeting wiped out your morning block → Move the block to a new slot, don't drop it
Tuesday · Priya · sharpest 9–12
09:00 Choose today's few (10 min)
09:15 DEEP draft results section, part 1
10:30 Short break
10:45 DEEP make figures 1 and 2
12:00 BATCH email and messages
13:00 Lunch
14:00 BATCH forms and bookings (afternoon dip)
15:00 BUFFER
15:30 Open2 deep blocks in her peak hours · 2 batch blocks · 1 buffer · the late afternoon left openNot every day looks like this. One protected deep block on a busy day still counts.
Check yourself
Kaveh plans tomorrow in the evening. He fills every slot from 8am to 6pm with tasks, puts his hardest task at 3pm after a long lunch meeting, and leaves no gaps. He's sharpest in the morning. What's the most useful change?
- Add a few more small tasks so no time is wasted
- Drop the blocks and just see how the day goes
- Start at 6am instead, so that everything on the list fits
- Move the hard task to the morning; add a buffer
Show the answer
Move the hard task to the morning; add a buffer
Yes. His hardest work belongs in his best hours, and a plan with no slack breaks at the first surprise. A buffer makes the rest of the plan survivable.
Lesson recap
- Time blocking gives your chosen tasks a when, not just a what, and you defend blocks like appointments.
- The planning fallacy makes us underestimate our own tasks; estimate from past reality and add a margin.
- Use deep blocks in peak hours, batch blocks for small tasks, buffers, and some open time.
- When the plan breaks, re-block the important work instead of dropping the day.