Maker's Schedule, Manager's Schedule

Overview

Paul Graham identifies two types of schedule: the manager's schedule and the maker's schedule. Understanding these different approaches to time is crucial for productivity and avoiding conflicts.

Manager's Schedule

The manager's schedule is for bosses and is embodied in the traditional appointment book, with each day cut into one hour intervals.

Characteristics:

• Time Units: One-hour blocks
• Flexibility: Easy to slot in meetings
• Approach: Time as fungible resource
• Primary Activities: Meetings, calls, reviews, decisions
• Context Switching: Frequent and expected

How It Works:

When you use time that way, it's merely a practical problem to meet with someone - find an open slot in your schedule, book them, and you're done.

Who Uses It:

• Managers and executives
• Sales professionals
• Customer-facing roles
• Coordinators
• People whose job is connecting others

Maker's Schedule

There's another way of using time that's common among people who make things, like programmers and writers, who generally prefer to use time in units of half a day at least.

Characteristics:

• Time Units: Half-day (4+ hours) minimum
• Need: Extended, uninterrupted blocks
• Approach: Time as scarce, precious resource
• Primary Activities: Writing, coding, designing, creating
• Context Switching: Disruptive and costly

Why Makers Need Long Blocks:

"You can't write or program well in units of an hour - that's barely enough time to get started."

Who Uses It:

• Programmers and developers
• Writers and authors
• Designers
• Researchers
• Artists
• Deep thinkers
• Anyone doing complex creative work

The Conflict

When you're operating on the maker's schedule, meetings are a disaster - a single meeting can blow a whole afternoon, by breaking it into two pieces each too small to do anything hard in.

Why One Meeting Ruins a Day:

Example: Meeting at 2 PM

• Morning (9 AM - 12 PM): 3 hours

  • Too short to start major work
  • Anticipating the meeting creates mental drag
  • Can't fully engage knowing interruption is coming

• Meeting (2 PM - 3 PM): 1 hour lost

• Afternoon (3 PM - 5 PM): 2 hours

  • Too short to restart deep work
  • Mental fatigue from context switch
  • Day feels fragmented

The Power Dynamic:

Each type of schedule works fine by itself, but problems arise when they meet. Since most powerful people operate on the manager's schedule, they're in a position to make everyone resonate at their frequency if they want to.

Paul Graham's Solution: Office Hours

Graham manages to advise many startups on the maker's schedule by using office hours.

How It Works:

• Set aside chunks of time at the end of working day
• Meet founders during these specific windows
• Use signup program to cluster all appointments
• Protects maker time earlier in day

Benefits:

• Preserves morning/afternoon blocks for deep work
• Batches all meetings together
• Creates predictable, protected time
• Maintains maker schedule while still being accessible

Strategies for Makers

1. Batch All Meetings

Cluster meetings on specific days or times.

Examples:

• "Meeting Mondays" - all meetings one day
• "Office Hours" - 2-4 PM daily for meetings
• "Tuesday/Thursday only" - no meetings other days

2. Protect Morning Blocks

For most people, mornings are peak creative time. Never schedule meetings before noon if possible.

3. Set Clear Boundaries

Communicate your maker schedule needs:

• "I'm available for meetings Tue/Thu 2-5 PM"
• "I don't take meetings before 1 PM"
• Block calendar to show unavailability

4. Create "No Meeting" Days

Dedicate entire days to maker work with zero meetings.

5. Use Async Communication

Prefer email, Slack, or other async methods over synchronous meetings when possible.

Strategies for Managers

1. Recognize Maker Needs

Understand that makers need different time blocks than you do.

2. Batch Your Meetings with Makers

Schedule multiple maker meetings consecutively rather than spreading throughout their day.

3. Respect No-Meeting Blocks

Don't book over protected maker time unless truly urgent.

4. Default to End of Day

When possible, schedule maker meetings late in their day.

5. Question Meeting Necessity

Ask if a sync meeting is really needed or if async communication would suffice.

For Mixed Roles

Many people need both types of schedules.

Strategies:

Theme Days:

• Maker days (Mon, Wed, Fri)
• Manager days (Tue, Thu)

Split Days:

• Morning: Maker mode (8 AM - 12 PM)
• Afternoon: Manager mode (1 PM - 5 PM)

Seasonal Approach:

• Maker months (deep project work)
• Manager months (meetings, reviews, planning)

Cultural Implications

For Companies:

Maker-Friendly Policies:

• No-meeting Wednesdays
• No meetings before 10 AM
• Default 25/50-minute meetings (not 30/60)
• Async-first communication
• Respect for blocked calendar time

Signs of Manager-Schedule Culture:

• Meetings any time, any day
• Expectation of instant availability
• Open office layouts
• Frequent interruptions normalized

Real-World Applications

Tech Companies:

Many successful tech companies implement:

• No-meeting days (GitHub, Asana, etc.)
• Maker time protection policies
• Async-first communication
• Flexible work hours

Individual Level:

Successful makers:

• Block calendar aggressively
• Batch meetings strategically
• Communicate boundaries clearly
• Protect mornings religiously

Common Challenges

Challenge 1: "But I Need to Be Available"

Solution: Set specific availability windows. Being available 2-4 PM is different from being available always.

Challenge 2: "Meetings Get Scheduled Anyway"

Solution: Block calendar, decline proactively, suggest alternative times.

Challenge 3: "I Have Both Responsibilities"

Solution: Theme days or split days to accommodate both needs.

Measuring Impact

For Makers:

• Hours of uninterrupted work per week
• Quality of output during maker blocks
• Project completion rates
• Stress levels
• Job satisfaction

For Organizations:

• Developer/maker productivity
• Time to ship features
• Code quality metrics
• Employee retention
• Innovation output

Integration with Other Methods

Maker's Schedule concept aligns with:

• Deep Work: Requires maker-schedule blocks
• Time Blocking: Tool for protecting maker time
• No-Meeting Days: Implementation of maker schedule
• Context Switching Costs: Explains why meeting breaks hurt
• Flow State: Requires maker-schedule conditions

Who Benefits Most

Understanding this framework benefits:

• Programmers and developers
• Writers and content creators
• Designers
• Researchers
• Managers of creative teams
• Anyone doing complex cognitive work
• Organizations wanting to optimize productivity

Related Concepts

• Deep Work: Requires maker-schedule time
• Flow State: Enabled by maker blocks
• Context Switching: Why manager interruptions hurt makers
• Time Blocking: Method for protecting maker time
• Async Communication: Alternative to manager-schedule meetings