Consolidate meetings into 1-2 designated days — meeting distribution destroys more capacity than meeting duration

Why This Is a Rule

Paul Graham's "Maker's Schedule, Manager's Schedule" essay identified the key insight: meetings don't just consume the time they occupy — they fragment the blocks around them. A single 1-hour meeting in the middle of a 4-hour block doesn't leave you with 3 hours of productive time. It leaves you with two 1.5-hour blocks, each too short for deep work, each requiring context-loading, and each psychologically compressed by the approaching or just-completed meeting. The meeting consumed 1 hour directly and destroyed 2+ hours indirectly through fragmentation.

Distribution is the killer, not duration. Five hours of meetings on one day costs you one day of maker time. The same five hours scattered as one meeting per day costs you five days of maker time, because each day's deep work blocks are fragmented by the meeting. Consolidation preserves entire meeting-free days for uninterrupted deep work — days where you can enter a maker-schedule mindset without watching the clock for the next meeting.

This is a batching strategy identical in principle to batching errands (one trip, many stops) or batching email (one session, many messages). The fixed overhead (context switching into "meeting mode," post-meeting recovery) is paid once per batch rather than once per meeting.

When This Fires

• When designing your weekly time-block structure
• When meetings are scattered across every day and deep work never exceeds 90-minute stretches
• When total meeting hours seem manageable but productive output feels disproportionately low
• Complements Never apply the two-minute rule during maker time — a 2-minute interruption costs 25+ minutes in context recovery during deep work (protect maker time) with the structural strategy for creating meeting-free blocks

Common Failure Mode

Accepting meetings whenever the calendar has an open slot. The "first available slot" scheduling algorithm guarantees maximum distribution — meetings land on every day because there are always gaps. The maker-schedule days are never protected because they're never designated.

The Protocol

(1) Designate 1-2 days per week as meeting days (e.g., Tuesday and Thursday). (2) When scheduling meetings, offer only meeting-day slots. "I'm available Tuesday afternoon or Thursday morning." (3) Protect non-meeting days absolutely: no "just this one quick call." Each exception fragments the protected day. (4) Batch back-to-back: on meeting days, stack meetings consecutively rather than spacing them. Three back-to-back meetings destroy one 3-hour block. Three spaced meetings destroy three separate blocks. (5) Accept that meeting days will be low-output for deep work — they serve a different function. The protected days carry the deep-work load, and they work because the meetings aren't there.