How to schedule deep work when your calendar is full of meetings

Deep work is the kind of work that actually moves projects forward — writing, design, hard engineering, strategic thinking. It needs 60+ minutes of uninterrupted time. Most knowledge-worker calendars have none. This is how to fix that, structurally.

The four-part playbook

1. Find your one anchor

You don't get to schedule three deep-work blocks per day. You're lucky to get one. Pick the day's highest-leverage block — the one where missing it actually matters — and treat that as your anchor.

Anchor characteristics:

• 90 minutes minimum, 120 ideal. Less than 90 and you're context-switching back to email before you've actually started. More than 120 and your brain runs out of fresh capacity.
• Same time every day if possible. Decision fatigue compounds — if you have to decide when the anchor is each morning, you'll skip it. Same slot daily removes the decision.
• Peak-energy window. For most people, mornings — but be honest about your own peak. If you're sharper at 10 p.m., that's your slot.

2. Defend it like a meeting

The single biggest reason deep-work blocks die: people accept meeting requests that overlap with them, telling themselves "I can do the deep work later."

Don't do this. Treat the anchor block as a meeting. If asked, "I have something else booked then" is a complete sentence — same answer you'd give about a 1:1.

If your team's culture pushes back on this, it's worth showing your manager which deep work the anchor produces. Most managers will trade a 30-minute sync for finishing a project a week earlier.

3. Batch everything else

The shallow work — email, Slack, code review, expense reports, status updates — expands to fill any unstructured time. Don't give it any.

Pick two windows per day for shallow work (e.g. 11:00–11:30 and 16:00–16:30). Outside those windows, the inbox is closed. Slack notifications off. Phone in another room.

This is the move that separates people who feel productive from people who are productive. The first three days are uncomfortable; by week two, your real output goes up sharply.

4. Plan to reflow

The plan will break. A meeting gets added; the kid is sick; an urgent customer issue lands. You can't prevent disruption — you can plan to reflow when it happens.

Three rules when the day breaks:

• Move the anchor first. If the anchor block is gone, find tomorrow's slot before triaging anything else.
• Compress the shallow work. Today's email batch can be 15 minutes instead of 30.
• Cut, don't reschedule. If the week is too packed, push the lowest-priority block to next week. Rescheduling a deep-work block to "later this week" is just lying to yourself.

This is where auto-scheduling tools shine. TimeFlow reflows your blocks automatically when meetings move — your anchor finds tomorrow's slot before you've opened the calendar to triage.

A worked example

Tuesday morning. My calendar starts:

• Standup 9:30–9:45
• 1:1 with Alex 10:00–10:30
• Customer call 14:00–14:30
• Eng review 15:30–16:30

Total meetings: ~3 hours. Open windows: 8:00–9:30, 10:30–14:00, 14:30–15:30, 16:30–17:30.

Anchor placement: 10:30–12:30, two hours of writing the design doc. Highest-leverage block of the day; longest open window; my morning energy is good.

Shallow batches: 13:00–13:30 (email + Slack catch-up before the customer call) and 17:00–17:30 (end-of-day cleanup). Outside those, Slack is muted.

Buffer: 8:00–9:30 is intentionally not booked. If the anchor runs over (it usually does), I have somewhere to recover. If it doesn't, that's reading time.

That's the whole day. The decisions are: anchor at 10:30, batch at 13:00 and 17:00. Everything else is reactive.

The two failures to avoid

Failure 1: Booking three "deep work" blocks in one day

You can't sustain three real deep-work blocks per day. Two is hard. One is realistic. People who schedule three end up doing zero — the calendar gives them permission to delay each one to the next slot, and the day evaporates.

Pick one. Make it count.

Failure 2: Scheduling deep work right after a 1:1

Context-switching cost from a 1:1 to deep work is brutal — 15–30 minutes of mental drift before you're actually focused. If you must sequence them, put 30 minutes of buffer between, even if it means moving the deep block.

This is the kind of thing auto-scheduling handles well. TimeFlow protects context buffer between high-context-cost transitions automatically.

The honest summary

Deep work isn't a productivity hack. It's a structural decision about which 90 minutes of your day matter most. Once you've decided, the rest of the system (batching, defending, reflowing) is just enforcement.

Most people fail at deep work not because they don't believe in it but because they don't enforce the anchor. Pick the slot, defend it, and accept that one great deep-work block per day is a productive week.

Try it

If you'd rather have the calendar place and reflow your deep-work blocks automatically, TimeFlow does exactly that — you tell it the work and the priority, it picks the slots, and it reshuffles when meetings move. Free during beta.