Paul Graham's 2009 essay "Maker's Schedule, Manager's Schedule" is the most-shared productivity essay in the YC universe for one reason: it names the single biggest cause of why senior engineers, designers, writers, and researchers feel like they're working flat out and shipping nothing. They are. They're on the wrong schedule for the work they're trying to do.
This free visualiser shows you exactly what that looks like. Pick a stance — Maker, Manager, or Hybrid — and see your day rendered as a timeline with deep-work blocks, meetings, buffers, and shallow work in proportion. The totals at the bottom tell you how many hours of real deep work the schedule actually contains, the longest unbroken block, and what kind of role each stance is realistically suited to.
The core idea, in one paragraph:
A maker's day works in 3–4 hour blocks. Anything that breaks those blocks (a single meeting at 11am) doesn't cost 30 minutes — it costs the entire morning, because the two leftover halves are too short to start anything substantial in. A manager's day works in 30-minute slots and meetings *are* the work. Both schedules are valid; mixing them is what kills output. The most common organisational failure is putting a maker on a manager's calendar and wondering why the code doesn't ship.
What each stance looks like in the visualiser:
- Maker — two genuine 3-4 hour deep blocks separated by lunch, with shallow work shoved to the end. Roughly 7 hours of deep work, zero scheduled meetings. The schedule of a senior IC who actually ships.
- Manager — 30-minute slots stacked 9-5, mostly 1:1s, syncs, and stakeholder calls. Roughly 7 hours of meetings, 30 min of deep work that won't survive the first interruption. The schedule of an EM, PM, or department head.
- Hybrid — one defended morning maker block (3.5h), all meetings stacked into a 2-hour midday window, async-only afternoon. The schedule of a player-coach, staff engineer, or founder who has to do both.
The math nobody runs:
A single 30-minute meeting at 11am on a Maker's schedule doesn't cost 0.5 hours. It costs: - 15 minutes of pre-meeting attention drift ("I have a thing in 15 min, no point starting anything deep") - 30 minutes of the meeting - 15-20 minutes of context-switch recovery on the other side - Plus the entire morning block being shredded into two 75-minute halves that won't fit any real task
That's why "just one quick meeting" can take a Maker's day from 7 hours of output to 2.
How to use this tool:
Pick the stance your current calendar most resembles, then pick the stance the work you're *supposed* to be doing requires, and compare the deep-work totals. The gap between the two is your real productivity problem — and almost always the real lever isn't time management, it's calendar design and meeting-decline politics. The verdict box at the bottom of each stance gives the honest version of what the schedule can and can't produce.
For the daily companion to whichever stance you pick, see the Morning Routine Checklist (which assumes a maker morning), the Meeting Cost Calculator (for proving meeting costs to skeptical managers), and the 90-Minute Focus Timer (which fits cleanly inside any maker block).