Maker Time, Manager Time

In July 2009, Paul Graham — programmer, essayist, and a co-founder of the startup accelerator Y Combinator — published a short essay with a long shadow: “ Maker’s Schedule, Manager’s Schedule.” It names a friction everyone who works alongside both kinds of people has felt but few could explain. There are, Graham argued, two fundamentally different ways of using time, and they are quietly hostile to each other. Most scheduling conflict inside a company is not rudeness or disorganization. It is two clocks, each reasonable on its own terms, billing each other for costs the other cannot see.

The hour and the half-day

The manager’s schedule is the traditional appointment book: the day cut into one-hour intervals, each hour a fresh default, changing what you do every hour as a matter of course. For someone on it, a meeting is a practical problem — find an open slot, book it, done — and it costs roughly the hour it occupies. The maker’s schedule belongs to people who make things: programmers, writers, designers, anyone whose work is one large object held whole in the head. Makers, Graham writes, “generally prefer to use time in units of half a day at least. You can’t write or program well in units of an hour. That’s barely enough time to get started.” For a maker, then, a meeting is not an hour. It is an exception thrown into the middle of the work: it splits the afternoon into two pieces, each too small to do anything hard in. And the damage starts before the meeting does. Knowing the afternoon will be broken, a maker is less likely to start anything ambitious in the morning — so the booking costs the hour, the shape of the day, and sometimes the nerve the hard work was depending on.

Defenses that respect both schedules

Graham’s own compromise was office hours: he put himself onto the manager’s schedule for a defined window — his sat at the end of the day — so interruptions arrived in a batch he had chosen instead of detonating through the middle of maker time. The pattern generalizes well beyond startups. Cluster meetings against each other and against the edges of the day, so the middle survives whole. Publish office hours if your role attracts drop-ins, and let the window absorb what used to ambush the week. Protect mornings for the work that needs a running start. And if you manage makers, learn to see what your single booking actually creates: a 2 p.m. meeting does not take an hour from a maker’s day — it takes the afternoon, and it mortgages the morning.

There is a subtler cost Graham points at, and anyone who has done deep work will recognize it. A maker with a meeting at two o’clock does not merely lose the hours around it; the whole day is quietly downgraded in advance. Ambitious work — the kind that sits near the edge of what you can do — needs the belief that there will be time to finish the thought. A day known to be broken rarely gets that belief, so the hard problem is never started at all, and nothing on any calendar records the loss. This is why makers guard empty days out of all proportion to their length: an unbroken day is not eight hours of capacity. It is the only container some work fits in.

Most professionals now live on both schedules inside the same week — managing in the morning, making in the afternoon. The distinction Graham drew teaches a diagnostic skill: before you defend a block or accept a booking, know which schedule the work in question runs on. Spend manager time without guilt and protect maker time without apology. Confusing the two is how a calendar fills completely while the real work waits for an evening that never quite arrives.

← All Insights

© 2026 Cognosco Learning. All rights reserved.