Maker’s schedule vs. manager’s schedule

Paul Graham distinguishes two incompatible scheduling types that create friction in organizations where both exist:

  • Manager’s schedule divides the day into hourly slots. Meetings are trivial interruptions, and context-switching is the norm.

  • Maker’s schedule requires long, uninterrupted blocks — ideally half-days or more — for substantive work like programming, writing, or design.

For makers, a single meeting doesn’t just consume the meeting time, it fragments the day and kills motivation for starting ambitious projects.

A meeting commonly blows at least half a day, by breaking up a morning or afternoon.

— Paul Graham

The asymmetry problem

Most powerful people in organizations operate on manager’s schedules. They don’t realize the asymmetric cost they impose on makers. A "speculative meeting" might be trivial for a manager—taking only their time—but devastates a maker’s entire afternoon.

The knowing of an interruption looms is as damaging as the interruption itself. If a maker knows a meeting is coming at 3pm, they can’t start any serious work in the morning.

Solutions

Graham advocates for time-blocking. This means scheduling all meetings at the end of the day (office hours) so they don’t fragment maker time. More broadly, he argues for organizational awareness of this distinction so both groups can work more harmoniously.

See also