Direct Answer

I block two hours of deep work on my calendar every day and treat that block exactly like an external meeting I can't move. If it's not on the calendar, it doesn't happen: the day fills in around it and eats the time instead. Blocking it, titling it, and declining anything that conflicts is what actually protects the work that matters.

If I left it off my calendar, my day got eaten. Every single time. Nobody was sabotaging my focus. An open calendar reads as available, and available time goes to whoever asks first. A meeting request, a "quick" call, an email that could have waited an afternoon: all of it filled the space I'd meant to use for the work that moves things forward.

So now I block deep work like a meeting I can't move. Two hours a day, and I defend them.

An empty calendar isn't free time

The reframe that changed it for me: an empty calendar is unprotected time. Every open block reads as an invitation, and the people around you will fill it faster than you can claim it. Nobody is doing anything wrong by booking a slot that looks free.

Guarding a vague sense of "focus time" doesn't work. Put the deep work where everyone checks before they book you. A block with a title and a fixed time is a fact about your day. "I'll find time later" is not.

2 hrs the deep work block I defend daily, treated as unmovable
One decision to protect before deciding anything else that day
Hack 12 of the 30 Hacks From Dahlia series

How to choose which two hours

The block only works if it matches your actual energy. Pick the two hours nobody else wants and you'll protect the calendar but lose the thinking, because you'll be staring at a blank document at your lowest-energy hour. For a lot of people the best focus is the first stretch of the morning, before the inbox sets the agenda. For others it's later, after the first wave of meetings clears.

Watch yourself for a few days before you commit. Where does your thinking feel sharpest? Where do you keep getting pulled away? Put the block where the first answer is yes and the second is no.

Block it like you mean it

A block only holds if you treat it like a meeting someone else booked.

Blocking it for real

✓
Title it like a real commitment. Not "focus time," but a specific label: what you're working on. A named block is harder to talk yourself out of.
✓
Decline conflicting invites. When something lands on top of the block, decline it like any other conflict. You don't owe an explanation of the work behind it.
✓
Tell your team it's not open. Say it plainly, once: that window is not available for meetings. People respect a boundary they've been told about more than one they're expected to infer from a calendar color.

An empty calendar isn't free time. It's unprotected time.

What counts as deep work, and what only looks like it

Deep work is the task that needs your full attention and produces something that didn't exist before you sat down: a plan, a piece of writing, a strategy, a decision only you can make. It falls apart if you're interrupted halfway through.

What sneaks in is shallower than it feels. Email feels productive because the count goes down. A "quick" call feels productive because you're talking about the work instead of doing it. Status updates, light admin, anything you could do while half listening to something else: none of it needs a locked door.

Saying no to a meeting

Setting the block is easy. Holding it the first few times someone books over it is hard. There's a real pull to say yes, especially when the request feels urgent or comes from someone you don't want to disappoint. That guilt isn't a sign you're doing something wrong. It's what a boundary feels like when it's working.

🔒
Treat the guilt as information

If declining a meeting during your block never felt uncomfortable, the block wasn't protecting anything. Don't reopen the calendar because you feel guilty.

A short reply is enough: you have a standing commitment during that window and you're glad to find another time. No lengthy justification, no apology. Anyone who pushes back on a block they'd never question if it were a client call is telling you something about the relationship, not your calendar.

When something actually is urgent

Real emergencies exist, and the block isn't meant to survive one. But most things that feel urgent only feel that way because they just landed in your notifications. A real emergency is rare and obvious: it can't wait two hours, and someone is actively affected by the delay.

When one does, handle it, then move the block to later that afternoon instead of dropping it. Breaking the block should be a decision you name, not where the day drifts.

Key takeaways

Frequently Asked Questions

Match the block to your actual energy, not to whatever slot happens to be empty. Notice the window where your thinking is sharpest, whether that is early morning before the inbox opens or a stretch later in the day, and claim it first. Blocking the two hours nobody wants anyway protects the calendar, not the thinking.

Decline it the same way you would decline a conflict with any other meeting already on your calendar, because that is what the block is. You do not need to explain the work behind it in the reply. A short note that you have a standing commitment during that window and can offer another time is enough, and it is the same courtesy you would extend to anyone whose meeting you tried to book over.

Deep work is the task that needs your full, undivided attention and produces something that did not exist before you started: a plan, a piece of writing, a system, a decision. It sneaks into disguise as a quick email reply, a status update, or a call that feels productive because it is social. If you can do it while half listening to something else, it is not the work the block was built to protect.

Handle the emergency, then move the block instead of dropping it for the day. A real emergency is rare and obvious: it cannot wait two hours and someone is actively affected by the delay. Most things that feel urgent in the moment are not that. Reschedule the block to later the same day rather than letting one interruption become the reason the work never happens.

Dahlia Imanbay, AI Strategist and Fractional CMO

Dahlia Imanbay

AI Strategist, Fractional CMO, and Full-Stack Developer with 16+ years of experience building AI systems for healthcare, SaaS, and mission-driven brands. Writes from production experience, not theory.

More from the series

Browse all 30 hacks

One small, real system at a time, from calendars to inboxes to the tools that quietly run the day. Watch the full "30 Hacks From Dahlia" series and read the companion post for each one.