The Two Schedules That Explain Why Meetings Kill Deep Work
In 2009, Paul Graham published a short essay that changed how many programmers, writers, and creative professionals think about their time. “There are two types of schedule,” he wrote. “The manager’s schedule and the maker’s schedule.” The insight was deceptively simple: these two schedules are fundamentally incompatible, and forcing makers to operate on a manager’s schedule is one of the most reliable ways to destroy their output.
The maker manager schedule distinction is not about seniority or job title. It is about what kind of work you do and what conditions that work requires. Understanding which schedule governs your best output, and building your day around it, is one of the highest-leverage changes a knowledge worker can make.
What the Manager’s Schedule Is
The manager’s schedule runs on one-hour increments. Each hour is a unit that can be assigned to a meeting, a call, a review, or a check-in. Meetings can be scheduled at 9am, 10am, 11am — the schedule accommodates all of them without much friction because each slot is independent. A meeting at 2pm doesn’t really affect the meeting at 3pm. The cost of adding another one-hour block is low.
This schedule works well for roles where the primary output is coordination: setting direction, reviewing others’ work, making decisions, gathering information, and aligning teams. For executives, project managers, and people in client-facing or operational roles, the manager’s schedule fits the actual work. Moving between contexts frequently is the job.
What the Maker’s Schedule Is
The maker’s schedule works in half-days or full days, not hours. Makers — programmers, writers, designers, researchers, analysts — produce work that requires long uninterrupted stretches of concentration. A programming session that takes two hours to reach full depth is cut off at the one-hour mark by a meeting. The context switch costs not just the meeting time but the ramp-back-up time on either side.
Paul Graham described this from his own experience as a programmer: “A single meeting can blow a whole afternoon, by breaking it into two pieces each too small to do anything hard in.” This is the core asymmetry. For a maker, a one-hour meeting in the middle of the afternoon is not a one-hour interruption. It is a four-hour interruption: the period before the meeting when focus is impossible because the meeting is coming, the meeting itself, and the period after when the context has been broken and rebuilding it takes time.
Why the Two Schedules Conflict
Most workplaces run primarily on the manager’s schedule. Calendars fill with one-hour slots. Meetings get booked wherever there is an opening. From the perspective of someone scheduling a 10am meeting, they see an available slot and fill it. They are not considering what that slot means to the person receiving the invite.
For a maker, that 10am meeting means the morning is gone. The two hours before the meeting are too short to get into deep work comfortably because the interruption is coming. The time after the meeting may be equally broken. What looked like a short meeting on the scheduler’s calendar eliminated the maker’s entire productive window for the day.
This is not a failure of individual discipline. It is a structural mismatch between how makers produce work and how organizations tend to schedule it. Graham’s insight was to name the mismatch clearly rather than treating it as a personal problem to be overcome through better focus techniques.
How to Apply the Maker/Manager Schedule Distinction
Identify which schedule governs your best output
Most people have days where they are primarily in maker mode and days or roles where they shift into manager mode. A senior developer who also runs a team may need maker time for coding and manager time for team coordination. The question is not which schedule you are permanently on, but which one governs the work that matters most right now.
If your most important output requires sustained concentration — writing, coding, designing, analyzing, building — you are in maker mode for that work. If your most important output is coordination and decision-making, you are in manager mode.
Protect your maker blocks at the calendar level
The practical application of the maker manager schedule is simple: block your maker time on your calendar before meetings can fill it. A four-hour morning block of focused work time, marked as busy, prevents the 10am meeting from appearing as an available slot. What is already blocked cannot be booked.
The specific mechanics: identify the time of day when your concentration is highest (for most people, morning), block it as a recurring protected window, and hold that boundary consistently. Meetings go in the afternoon, or in designated coordination slots outside the protected window.
Time blocking is the practical tool that makes the maker schedule work. The principle is Paul Graham’s; the implementation is a recurring calendar block that signals to yourself and others that this time is committed to deep output, not coordination.
Batch your manager tasks
The manager’s schedule components of your day — email, meetings, approvals, check-ins — should be consolidated rather than distributed throughout the day. If meetings must happen, an afternoon block from 1pm to 4pm is far less damaging to a maker’s output than individual meetings scattered through the day at 9am, 11am, 1pm, and 3pm.
Batching all coordination work into a defined window preserves the morning for maker work without requiring that meetings be eliminated. The maker and manager roles coexist; they just run in different parts of the day.
Communicate your schedule explicitly
One of Graham’s practical suggestions was simply to be explicit with the people who schedule meetings with you. Telling colleagues “I keep mornings for deep work and am available for meetings after 1pm” changes how your calendar gets used without requiring anyone to guess. Most people will accommodate a clear stated preference. What they cannot accommodate is an unstated one they do not know exists.
The Maker/Manager Schedule in Practice With Any.do
The task management side of the maker schedule is about knowing exactly what to work on during protected maker time, so that the block is used for focused output rather than planning.
A useful daily structure: each evening or morning, identify the two or three maker tasks you will work on during your protected window. Add them to your Any.do daily planner for that day. When the maker block starts, you open your task list and know immediately where to direct your attention. No decision overhead at the start of the block.
Deciding what goes into your maker time the day before means the protected window starts immediately rather than starting with ten minutes of figuring out where to begin. The calendar protects the time; the task list defines what happens in it.
Any.do’s daily planning view shows your calendar events and your tasks together, which makes it straightforward to plan around your protected maker blocks. You can see at a glance what meetings are already scheduled and assign the right tasks to the right remaining windows. The unified task and calendar view is built precisely for this kind of integrated daily planning.
When the Maker Schedule Is Not Available
Not every role or organization allows makers to protect long blocks. Some jobs require frequent context switching by design. For people in those roles, the maker/manager schedule distinction is still useful even if a full half-day block is not possible. Even a 90-minute protected window, consistently held, creates meaningfully more deep output than a fully fragmented day.
The goal is not a perfect maker schedule. It is moving incrementally toward one: identifying the most valuable focused work time, protecting it from the highest-priority interruptions, and expanding it as much as the role allows. Small consistent expansions of maker time compound over weeks and months into substantially more of your best work getting done.
Start Protecting Your Maker Time Today
The maker manager schedule is one of the clearest frameworks for understanding why certain kinds of work require different time structures. The application is direct: identify when your best output happens, block it before meetings can claim it, and batch your coordination work into the remaining windows.
If you want the task management side to match the calendar structure, Any.do is free to start and takes a few minutes to set up. The combination of a time-blocked calendar and a clear daily task list is what turns protected maker time into consistent, completed output.
