Manager-Maker Schedule Clash

A simple explanation

Paul Graham's distinction is one of the clearest framings of why modern knowledge work is structurally broken at the calendar level. The manager's day runs in 30-minute units, and a single meeting in the middle of it costs only 30 minutes. The maker's day runs in three-to-four-hour blocks, and a single meeting in the middle of it costs the entire block.

When the same calendar tries to run both schedules — which most workplaces do — the maker loses. The meeting is the same meeting from the manager's side; from the maker's side, it is the destruction of the only block in which substantive work could have happened.

An everyday example

You are an engineer. Wednesday afternoon, you have three free hours from 1pm to 4pm — the only block this week long enough for the architectural work you have been trying to start. At 11am a manager schedules a 30-minute sync at 2:30pm.

From the manager's view, this is normal — they had a gap, you had a gap, the gap aligned. From your view, the calendar now reads: 90 minutes of pre-meeting where you cannot start anything substantive because you will be interrupted; 30 minutes of meeting; 60 minutes of post-meeting where you have to re-load context and the resumption lag eats most of it. The afternoon's substantive output goes from three hours to perhaps thirty minutes of actual depth.

The meeting cost the manager 30 minutes. It cost you the week's only deep block.

Why one calendar can't run both

Three structural reasons.

First, the unit sizes are incompatible. The manager's natural unit is 30 minutes; the maker's natural unit is 3-4 hours. A single 30-minute intrusion does not subtract 30 minutes from a 4-hour block — it shatters the block into two unusable pieces.

Second, the cost models are asymmetric. Scheduling a meeting costs the manager almost nothing (it is the substrate of their work). It costs the maker the resumption lag, the pre-meeting anticipation, the post-meeting re-entry, and the lost depth-deposit. The maker bears all the cost; the manager bears almost none.

Third, the visibility is asymmetric. The manager sees their own calendar fill productively. The maker's loss — the substantive work that did not happen — is invisible until evaluation time, when the deliverables are missing and the cause is no longer traceable to the schedule.

Graham's framing is essentially that running both schedules on one calendar is a quiet subsidy from makers to managers. The maker pays the structural cost; the manager rarely sees it.

The behavioral loop

The shape that runs through a clashed week:

1. The maker's calendar shows a deep block — 3-4 hours free.
2. A manager spots the gap — schedules a meeting in the middle.
3. The block becomes two fragments — neither long enough for depth.
4. The maker arrives at the first fragment — knows the meeting is coming.
5. The pre-meeting anticipation prevents depth — no point starting something the meeting will interrupt.
6. The meeting happens — 30 minutes for the manager.
7. The maker returns to the second fragment — has to re-load context.
8. The resumption lag eats the front of the fragment — 15-20 minutes lost.
9. Depth never enters — the afternoon's substantive output is near-zero.

The defining feature is that the loss is structural and invisible. No one did anything wrong by any local rule.

Emotional drivers

Three feelings, layered:

• A faint resentment at the meeting — that meeting cost me my afternoon — that the maker often suppresses because the resentment seems unreasonable in proportion to a 30-minute meeting.
• A diffuse self-distrust at end of week — why am I not producing what I should be? — that the loop-runner often metabolises as personal failure rather than structural cost.
• A reluctant complicity in the system — accepting the meetings because refusing them carries social cost, while paying the depth cost silently.

What your nervous system does

The maker who anticipates an interrupting meeting cannot fully drop into the focused-attention state required for depth. The body monitors the clock, the calendar reminder, the approaching interruption. The monitoring is itself a form of vigilance, low-grade but continuous, that prevents the parasympathetic engagement that depth requires.

After the meeting, the body has to re-enter the state, which takes the resumption lag plus the additional cost of the residue the meeting itself produced. Over weeks, the maker's body learns that any calendar with intrusions is not safe for depth, and the body stops attempting depth in those calendars at all.

The DojoWell interpretation

Manager-maker schedule clash is a structural producer of effort_without_deposit for the maker — the density signature in which real working hours produce near-zero substantive deposit because the calendar's shape destroys the blocks depth would have required.

The Meaning System is asking for the protected block. The Threat System, scanning for unattended meetings and unanswered requests, allows the intrusions because they are immediate. The system answers the Threat System (the meeting is unmissable) and underpays the Meaning System (the depth never enters).

The substitute is calendar fragmentation — the appearance of a normal working day made of normal-looking pieces. Real effort runs. The deposit on substance is destroyed not by the work being absent but by the blocks being too short for the work to settle.

The equation reads sharply for the maker. Effort: present. Deposit on substance: collapsed, because every block is below the depth floor. Residue: the anticipation of the next intrusion. The numerator collapses. Density: low. The fix is structural and political — a team-level agreement about which days run on which schedule, or a manager who treats the maker's depth blocks as load-bearing rather than as available space.

How do I protect maker hours when my manager runs on manager hours?

Three moves, in increasing order of difficulty.

First, declare the shape of your calendar. Make Tuesday-Thursday mornings (or whatever block) visibly protected. Reject meeting requests in those slots by default. The decline is read as serious only if you stay consistent.

Second, explain the cost in the manager's vocabulary. Most managers do not know Graham's framing. A meeting in my deep block costs the whole block, not just the meeting is a sentence that translates the asymmetry into a cost the manager can hear.

Third, propose a team-level pattern. Mondays and Fridays for meetings; Tuesday-Thursday for depth. Once the pattern is at the team level, individual makers do not have to defend it daily.

Practical steps

1. Block your depth hours as recurring events. Visible on shared calendars. Deep work — do not schedule over in the title.
2. Decline meeting requests in those slots by default. Offer alternative times in your shallow blocks. The decline must be consistent or it stops being read as serious.
3. Track the cost of intrusions for one month. Note each meeting that landed in a deep block and what depth-work did not happen as a result. Bring the data to your manager.
4. Negotiate one full-depth day per week. Most managers can accept no meetings on Thursdays once the cost is visible. One day of guaranteed depth produces more output than four days of fragmentation.
5. Match your own meeting-scheduling to maker norms. When you schedule meetings for others who do maker work, put them at the edges of the day, not the middle. The norm shifts from inside.

Reflection questions

• How many depth blocks did your calendar have last week, and how many of them were intruded on?
• Does your manager understand the cost structure of meetings on a maker's schedule, and if not, what would it take to explain it?
• Which one day of your week, if guaranteed meeting-free, would change your output most?
• When you schedule meetings for others, do you place them at the edges or the middle of their days?

Frequently Asked Questions