Time-Blocking 101: How to Plan a Focused Workday

I used to write to-do lists with fourteen items and finish three. Time-blocking turned that around — but only after I stopped doing it the way most articles tell you to. Here's the version that actually works for me, plus the mistakes I made first.

What time-blocking actually is

Time-blocking is the practice of putting specific outcomes onto your calendar at specific times — not just meetings, but the work itself. Instead of a calendar with three meetings and a vague to-do list with twelve items, you have a calendar with three meetings and three named blocks like "9:00–10:30 Draft Q3 customer-success report" or "14:00–14:30 Process inbox to zero". The list answers what; the calendar answers when; time-blocking is the bridge.

The promise sounds productivity-influencer-y, but the underlying mechanism is real: when an outcome has a specific start time, the cost of postponing it is visible. You can see the conflict. You can decide whether to defend the block or move it. Without a block, "draft the report" silently slips from Tuesday to Thursday to next week, and you never quite notice.

The first mistake I made: blocking the entire day

My first attempt at time-blocking, around 2021, was beautiful on paper. I divided every hour from 8:30am to 6:00pm into a labeled block. By 9:45am the schedule was dead — a client request had shifted, a meeting ran long, and now every block downstream was wrong. I spent more time rebuilding the calendar than doing the work. After two weeks I gave up and went back to a chaotic list.

The version I use now blocks only the work that needs protected hours. Three blocks a day, max. Everything else lives on a regular to-do list and floats into the unblocked time. The calendar isn't a script for the day; it's a contract for the parts that matter most.

The three rules I actually follow

Rule 1: Block your peak hours, not your busy hours. Mine are 9–11am — that's when the hardest writing or analysis happens. I defend that 90-minute window like a meeting, including against meeting requests. If someone has to talk to me at 10am, I ask if 2pm works first. About 80% of the time, it does.

Rule 2: Name the outcome, not the activity. "Work on Q3 plan" is a hope. "Draft the executive summary section of the Q3 plan" is a block. The named outcome makes the start frictionless because there's no "what should I do first" question. It also makes the end clear: when the summary is drafted, the block is done, even if there are 20 minutes left on the clock.

Rule 3: Leave 40% of your day unblocked. This is the rule that changed everything for me. Reality has overruns, ad hoc requests, and small fires that need handling. If your calendar is 100% blocked, every interruption breaks the system. If 60% is blocked and 40% is open, interruptions just consume the open time and the blocks survive.

A workday that actually works

Here's roughly what a Tuesday looks like for me:

That's three named blocks (4½ hours of protected work) and three open windows (3½ hours for everything else). The structure is simple enough that I don't need a tool to maintain it; the calendar just shows the three blocks and meetings, and a daily to-do list handles the rest.

How time-blocking pairs with a daily list

The mistake I see in most time-blocking advice is the assumption that the calendar replaces the list. It doesn't. The list is where you capture and prioritize what; the calendar is where you commit to when. They answer different questions and need to coexist.

My workflow uses Today's Tasks for capture and prioritization (three lanes: High Priority, Due Today, General) and Google Calendar for the three blocks. At the start of each day I look at the High Priority lane and ask: "Which of these need protected hours?" Those become the blocks. The rest float in the open windows.

If you take one thing from this article: don't try to time-block your whole day. Block the two or three outcomes that need protected hours and let the rest float.

Common mistakes (besides over-blocking)

Blocking back-to-back without buffers. Every block needs a 10–15 minute decompression window after it, especially after a focused 90-minute push. Without buffers, by 3pm you're cooked.

Not protecting the block. Treat blocks like meetings: decline the calendar request that conflicts with one, just like you'd decline a meeting that conflicts with a client call. If you cave the first time someone tries to schedule over your block, the system collapses within a week.

Optimizing the schedule instead of doing the work. The calendar is a tool, not the goal. If you find yourself spending 20 minutes every morning rearranging blocks, you've drifted into procrastination dressed as planning. Two minutes is enough.

Confusing "deep work" with "all work". Not every task deserves a block. Most don't. Email, small admin tasks, quick decisions — these belong in open windows. Reserve blocks for the work where context-switching genuinely costs you 20+ minutes of recovery.

Getting started this week

If you've never time-blocked before, the smallest viable version is this:

1. Tomorrow morning, before opening your inbox, identify one outcome you want to make real progress on.
2. Put a 90-minute block for that outcome on your calendar at your peak focus time. Name the outcome specifically.
3. When the block starts, close email and chat. Work on the named outcome.
4. When it ends, take a 10-minute break. Then go check your inbox.

Run that for a week. If it works, add a second block. If it doesn't, change the time of the block (peak focus shifts) or the specificity of the outcome (vague names = unfinished blocks). Don't add more blocks until the first one is reliable.

FAQ

How long should each block be?

For deep work I use 90 minutes. Some people prefer 50 minutes (one Pomodoro pair) or 60 minutes (a standard meeting slot). 90 works for me because it's long enough to get past the warm-up phase and short enough that I don't burn out. Test with what fits your work — but don't go above 2 hours; nobody sustains real focus for that long.

What if my schedule changes constantly?

This is the case I most hear from managers and parents. Two adaptations work: (a) block two alternative times for each priority and pick whichever survives the chaos by mid-morning, or (b) shrink to one block per day and accept that's it. One block consistently held is far better than three blocks that constantly collapse.

Should I time-block evenings and weekends too?

Generally no. Time-blocking is a tool for protecting the work that matters at work. Applying it to personal time tends to make rest feel like more work. If you have a personal project you want to make progress on, one weekend block is fine; daily evening blocks usually aren't.

How does time-blocking interact with the weekly review?

The weekly review is when you decide which outcomes deserve blocks next week. The daily review (a two-minute end-of-day scan) decides which outcomes deserve blocks tomorrow. Both happen at the list level — the calendar just executes what the list decides.

Open Today's Tasks →