In one sentence
Managers can treat time as interchangeable hourly units; makers cannot. Because creative work requires sustained immersion, organizations should design communication and meetings around the maker’s schedule rather than imposing managerial fragmentation on everyone.
Overview
Graham observes that programmers and writers often work best in half-day or longer blocks, while managers naturally organize time into one-hour appointments. A meeting is therefore a minor transition for a manager but a major interruption for a maker: it breaks an afternoon, creates task-switching costs, and may discourage starting ambitious work at all.
The central organizational problem occurs when people on the two schedules interact. Managers—especially those with authority—can impose their rhythm on makers, even when they understand neither the cognitive cost nor the morale effect. Graham’s solution is not to eliminate meetings, but to contain them: cluster them into office hours or place them at the edges of the workday. He describes using separate parts of his day for managerial and maker tasks.
The essay also explains why speculative meetings, such as “grabbing coffee,” are cheap for managers but expensive for makers. The broader principle is that coordination systems should account for the opportunity cost of interruption, not merely the meeting’s duration.
Core ideas
Two fundamentally different time models
The manager’s schedule divides the day into appointments and treats open slots as available capacity. The maker’s schedule treats uninterrupted blocks—often half a day or more—as the basic unit of productive work.
A meeting costs more than its duration
For a maker, a one-hour meeting can destroy the surrounding block, force a change of mental mode, and make difficult work feel impractical. The real cost may be an afternoon or an entire day, not one hour.
Interruption changes what gets attempted
Knowing that the day will be broken up can prevent someone from beginning an ambitious task in the first place. Schedule design therefore affects not only output, but also which projects people are willing to undertake.
Authority creates schedule asymmetry
People with organizational power often operate on the manager’s schedule and can unintentionally force everyone else into it. The essay argues that effective leaders restrain this power when they know their colleagues need long creative blocks.
Cluster coordination instead of scattered interruption
Office hours are Graham’s practical device: group meetings into a predictable block, preferably at the end of the maker’s day. This preserves a contiguous work period while retaining access and responsiveness.
Speculative meetings have unequal costs
An exploratory meeting may be nearly free for a manager with spare calendar capacity, but costly for a maker. “Just coffee” should therefore not be treated as universally low-cost or socially neutral.
People can maintain dual schedules
Graham describes separating maker and manager work into different periods—programming at night and handling business during the day. The idea generalizes to protecting certain hours for creation and reserving others for coordination.
Practical takeaways
- Identify whether each task requires managerial responsiveness or maker-level concentration.
- Protect several uninterrupted half-days each week for writing, coding, design, analysis, or other deep work.
- Batch meetings into office hours or a narrow daily window instead of scattering them across the calendar.
- Schedule meetings at the end of a work block when possible, so they do not split productive time.
- Before accepting a meeting, ask whether the expected value justifies losing the surrounding work block—not merely the meeting’s stated duration.
- Make the cost of interruptions explicit to managers, clients, and collaborators; this is a coordination issue, not a personal preference.
- Use asynchronous updates, written questions, and well-defined agendas when a live meeting is unnecessary.
- If you must serve both roles, separate maker and manager periods rather than switching repeatedly throughout the day.
Caveats and counterpoints
- The essay presents a useful distinction, not a complete taxonomy. Many roles mix creation, collaboration, support, and decision-making, so a person may need to switch schedules deliberately.
- Some creative work is collaborative and benefits from frequent interaction; minimizing meetings can also reduce feedback, alignment, and learning.
- The office-hours solution works best when requests can be queued. Emergencies, customer support, and tightly coupled teams may require faster response systems.
- Graham’s examples come largely from programming, writing, startups, and venture advising. The costs and feasible scheduling patterns may differ in healthcare, operations, education, or other interruption-heavy work.
- The argument emphasizes the maker’s lost concentration but gives less attention to the coordination costs managers bear when access is restricted. A good system must balance both.
Questions worth revisiting
- Which parts of my week are genuinely maker work, and which are manager or coordination work?
- How much productive time does each meeting actually consume, including setup, recovery, and abandoned work?
- Could recurring meetings be batched, shortened, moved asynchronous, or placed at the edge of the day?
- Do I unintentionally impose my schedule on people whose work requires longer uninterrupted blocks?
- What ambitious work am I postponing because my calendar never contains a sufficiently large open block?
- When is an interruption truly urgent, and what escalation rule should distinguish it from ordinary availability?
Return to this when…
Return to this essay when redesigning a calendar, introducing a meeting policy, managing creative or technical staff, or deciding whether an apparently small meeting is worth the larger block of concentration it may destroy.