Maker’s Schedule, Manager’s Schedule
Central idea
A meeting that looks like one hour on a manager’s calendar can destroy half a day of a maker’s productive work.
Summary
Managers commonly organize work in one-hour blocks, switching subjects between meetings. Makers—programmers, writers, and designers—usually need long, uninterrupted blocks because difficult creation depends on loading a large problem into working memory. A single meeting can split the day into fragments too small for ambitious work, while the manager scheduling it may see only an available slot. Neither schedule is inherently superior; the failure is treating them as interchangeable. Teams can reduce the collision by clustering meetings, using office hours, protecting meeting-free blocks, and recognizing the real cost of an interruption before placing it on someone else's calendar.
Key ideas
Calendar time is not equal
The same one-hour meeting has different costs depending on whether surrounding work is modular or requires deep context.
Context is expensive to reload
Complex creation needs a continuous mental model; fragmentation consumes time before and after the visible interruption.
Design schedules intentionally
Batch communication and create predictable collaboration windows instead of scattering interruptions throughout every day.
Protect both modes
Identify which work requires long focus blocks.
Cluster recurring meetings into bounded windows.
Keep meaningful meeting-free periods.
Evaluate interruption cost, not only calendar availability.
Why it matters now
AI can shorten individual implementation steps, but complex problem framing, architecture, verification, and debugging still require sustained attention. Faster tools do not make fragmented thinking free.
Continue with the original
This short version preserves the main argument. Follow the source for the complete talk, article, or book.