Maker's Schedule vs. Manager's Schedule: How to Protect Deep Work

Quick answer

There are two incompatible ways to run a calendar. The manager's schedule is cut into one-hour slots and works fine with frequent switching — that's how most people run their day by default. The maker's schedule needs blocks of half a day or more, because deep, creative work like writing or coding can't be entered and exited in an hour. Paul Graham named this split in 2009. The fix hasn't changed since: batch or push back the meetings that fragment a maker's day, instead of scattering them through it.

How it actually works

The two schedules, defined

A manager's schedule assumes you can pick up any task in the next hour, because the day is already divided that way. Slotting in a meeting costs almost nothing — you were about to switch tasks anyway. Makers don't get that luxury. Real progress on hard work needs half a day at minimum, because getting into a difficult problem takes time, and getting back into it after an interruption takes almost as long again.

Why one meeting can wreck an afternoon

The damage isn't the meeting's length — it's what the meeting does to the time around it. Drop a single one-hour meeting into the middle of an afternoon, and it splits into two pieces, neither long enough to do anything hard in. Worse, just knowing the afternoon will be broken up can be enough to talk yourself out of starting something ambitious that morning, since there won't be time to get far into it before the interruption arrives.

This isn't a fringe complaint. Research cited by Harvard Business Review found that 70% of meetings keep employees from completing their actual work, and the trend has gotten worse, not better: during the pandemic, average meeting length dropped by roughly 20%, but the average number of meetings attended per employee rose about 13.5%. Meetings got shorter and more frequent at the same time — close to the worst possible combination for a maker's schedule, since every meeting still forces a full context switch no matter how short it is.

The batching fix

The most consistent fix across people who've solved this for themselves is batching. Instead of spacing three meetings at 10am, 1pm, and 4pm — three unusable fragments — pack them back-to-back, or push them to the end of the day, so the rest of the calendar stays one uninterrupted block. Graham did this himself, holding "office hours" late in the day for anything that had to be a meeting, and leaving mornings and early afternoons untouched. It's really just a stricter version of time blocking — instead of blocking time for tasks, you're blocking time against interruptions.

When to use it (and when to skip it)

Who needs a maker schedule

This matters most for anyone whose output depends on sustained focus rather than availability: freelance developers and designers, writers, indie hackers shipping their own product, and anyone doing engineering or research work where getting "into" the problem takes real setup time.

Designated maker days vs. full flexibility

You don't have to choose between total flexibility and refusing every meeting. Cal Newport suggests splitting the week — designating specific days (say, Monday, Wednesday, Friday) as meeting-free maker days, and leaving Tuesday and Thursday open for collaboration. For most people, that's a workable middle ground, short of the more extreme option of routing all contact through a gatekeeper.

Not every week allows for a full blocked day, though. On weeks where meetings can't be consolidated that cleanly, try thinking about working with your peak hours instead — protecting your sharpest 90 minutes rather than an entire day. A smaller, device-level habit that reinforces either approach: turning on a Focus mode for the length of the block, so notifications don't undo what the calendar is protecting.

When it's overkill

Not every role benefits from a rigid maker day. Managers and client-facing freelancers whose value comes from coordination and availability may find a strict no-meetings block actively gets in the way. The point isn't to apply one rule everywhere — it's matching the calendar to what the work actually requires.

How Pomlo fits in

Protecting a block on your calendar only works if you can tell, afterward, whether it actually held. Pomlo's focus sessions let you track a deep-work block as its own session instead of lumping it into generic "work" time, so a protected afternoon shows up distinctly from a fragmented one. Reports make the pattern visible over a week or a month — how many uninterrupted blocks you actually got, versus how many got split by a call that could've waited. And because Pomlo organizes time by projects and clients, freelancers can tag focused work to the project it served, which matters when part of what you're protecting is billable deep work, not just time in general.

Pomlo is free to try on the App Store and Google Play — start a focus session the next time you block off a maker afternoon, and see how much of it actually stayed intact.

Frequently Asked Questions

What is the maker's schedule vs the manager's schedule?

The manager's schedule is cut into one-hour slots built for frequent task-switching — it's how most calendars default to working. The maker's schedule needs half-day-plus blocks, because deep, creative work like coding or writing can't be entered and exited in an hour. Paul Graham coined the distinction in 2009; it's now standard language for describing why the same calendar can work great for one role and terribly for another.

Why does one meeting ruin an entire afternoon for makers?

A meeting dropped into the middle of a block doesn't just cost its own 30-60 minutes — it splits the surrounding time into two pieces, each too short to get into deep work. Knowing the afternoon will be interrupted also lowers the motivation to start something ambitious that morning, since there won't be time to get far into it before the break arrives.

How do I protect deep work time if I can't refuse every meeting?

Batch meetings instead of spacing them out — cluster them at the end of the day or onto specific days of the week, so the rest of your calendar stays in uninterrupted multi-hour blocks. Treat a scheduled deep-work block the same way you'd treat an important meeting: don't let it get pulled apart for a call that could wait.

Are speculative or casual meetings really that costly?

For someone on a manager's schedule, a quick coffee chat or intro call is nearly free — it just fills one of many hourly slots. For someone on a maker's schedule, that same 30-minute call can cost an entire half-day block, since the two remaining fragments on either side aren't long enough for real work. Being selective about agenda-less meetings protects far more time than the meeting's length suggests.