A meeting that costs a manager 30 minutes can cost an engineer the whole afternoon. That asymmetry is the single most useful idea for anyone scheduling other people's time, and most calendars ignore it completely. The bill shows up as lost engineering, and it's bigger than founders think.
Key Takeaways
- Makers and managers run on different schedules; a midday meeting can split a maker's day into two useless halves (Paul Graham).
- Employees lose roughly 24 hours a month to meetings they call unproductive, and a 5,000-person company can burn up to $100M a year on them (CBS News).
- Real engineering work needs blocks of half a day, not one-hour slots.
- Protect focus by clustering meetings and defaulting to async.
The Maker's Schedule
Paul Graham's essay "Maker's Schedule, Manager's Schedule" named the problem better than anyone. Managers slice the day into one-hour appointments, because that's how management works. Makers, engineers and writers, need long uninterrupted blocks, because you can't do deep technical work in the fragments between meetings. A single meeting dropped into the middle of a maker's day, Graham notes, can cost the whole afternoon by breaking it into two pieces too small to build in.
The trouble is that managers set the calendar, so the manager's schedule wins by default, and the makers quietly pay for it.
The Money Behind the Metaphor
The framework is nice, but the bigger point is that this gets expensive fast. Broad studies of meeting time keep landing on eye-watering numbers: employees lose around 24 hours a month to meetings they themselves call unproductive, and a single company of 5,000 people can waste up to $100 million a year on inefficient meetings (CBS News). Roughly 70% of senior managers say their own meetings are unproductive. That's not a scheduling annoyance. It's a line item.
For engineers the number actually understates the damage, because it counts the meeting minutes but not the ruined focus blocks on either side. As Cal Newport has written, deep work needs protected, uninterrupted stretches, and a fragmented calendar destroys exactly those.
| Cost of a midday meeting | Manager | Maker |
|---|---|---|
| Direct time | 30 min | 30 min |
| Realistic total cost | 30 min | Half a day |
A Concrete Version
Give a senior engineer a 2pm standup and a 4pm sync. On paper you've booked one hour of their day. In reality: the morning is fine, but after lunch they have 90 minutes before the first meeting (not enough to get deep into a hard problem), then 90 minutes between the two (also not enough), then it's 4:30 and they're cooked. You spent one hour of calendar and bought roughly zero hours of deep work that afternoon. Do that a few days a week and your most expensive engineer is producing at a fraction of their capacity, and every meeting felt "necessary" at the time.
The Honest Counterpoint
Some meetings are the best thirty minutes of the week: a real design debate, unblocking a stuck decision, a hard conversation email would butcher. The goal isn't zero meetings, and a team that swings to "no meetings ever" just moves the dysfunction into 200-comment threads. The point is narrower: meetings are expensive for makers, so they should clear a real bar and sit where they don't shred focus, instead of getting scattered across the day out of habit.
How to Protect Maker Time
The fixes are cheap. Cluster meetings at the edges of the day so the middle stays open for real work. Default to async for anything that isn't a genuine discussion, which is the heart of the async-first approach. And use timezone overlap deliberately: schedule the few meetings that truly need to be live, and leave the rest of the shared window for building. That's the argument for spending timezone overlap on collaboration that counts, not status theater. See available engineers.
Frequently Asked Questions
Why do meetings cost engineers more than managers?
Engineers need long uninterrupted blocks to do deep work. A meeting in the middle of the day splits it into fragments too small to build in, so the real cost is the ruined blocks, not the meeting itself.
How expensive are unproductive meetings?
Studies estimate employees lose about 24 hours a month to meetings they consider unproductive, and a 5,000-person company can waste up to $100 million a year. For engineers the true cost is higher because it includes the wrecked focus blocks around each meeting.
How many meetings is too many for an engineer?
Any pattern that prevents half-day focus blocks. Scattered short meetings are worse than the same total time clustered together.
What's the fix?
Cluster meetings at the start or end of the day, default to async for non-discussions, and reserve live time for collaboration that genuinely needs it.
The Bottom Line
Meetings are priced in manager minutes and paid in maker afternoons, and the studies show the bill runs into real money. Protect your engineers' focus by clustering meetings and defaulting to async, and you reclaim the most expensive hours on your team.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers in 72 hours. See available engineers.
