Maker vs Manager Schedule

Overview

The Maker vs Manager Schedule is a time management framework introduced by Paul Graham of Y Combinator in a 2009 essay. It distinguishes between two fundamentally different approaches to organizing time based on the type of work being performed.

The Two Schedules

Maker's Schedule

The Maker Schedule is designed for individuals whose primary work revolves around creative output and deep work:

• Time Units: Half-day blocks minimum
• Who: Software developers, designers, writers, artists, engineers, researchers
• Work Style: Requires prolonged concentration, problem-solving, and deep focus
• Meeting Impact: A single meeting can destroy an entire afternoon by breaking it into fragments too small for meaningful work
• Philosophy: You can't write or program well in units of an hour; that's barely enough time to get started

Manager's Schedule

• Time Units: One-hour slots or smaller
• Who: Executives, managers, coordinators
• Work Style: Gathering information, making decisions, coordinating people
• Meeting Impact: Meetings are the primary work product
• Philosophy: Days are sliced into predetermined slots, each with a specific purpose

The Core Conflict

When operating on the maker's schedule, meetings are disastrous. Research by Gloria Mark revealed that it takes an average of 23 minutes and 15 seconds to refocus on a task after an interruption. For makers, this means:

• Morning meetings destroy the entire morning
• Afternoon meetings fragment the day into unusable pieces
• Even short meetings create switching costs that eliminate deep work

Practical Solutions

Office Hours

Paul Graham recommends that makers implement "office hours"—designated blocks when they're available for meetings, while protecting the rest of their time for deep work. This allows:

• Managers to get needed face time
• Makers to maintain long stretches of uninterrupted focus
• Clear expectations about availability

Batching Meetings

• Schedule all meetings on specific days (e.g., Tuesdays and Thursdays)
• Keep other days completely meeting-free
• Group meetings consecutively rather than spreading throughout the day

Communication Boundaries

• Set expectations about response times
• Use asynchronous communication for non-urgent matters
• Implement "Do Not Disturb" modes during maker time

For Organizations

Respecting Both Schedules

• Recognize that different roles require different time structures
• Don't force makers onto manager schedules
• Create policies protecting maker time
• Schedule meetings at natural boundaries (start/end of day)

Hybrid Roles

Many people need both schedules:

• Designate specific days for each mode
• Use mornings for maker work, afternoons for manager work
• Explicitly transition between modes

Benefits of Implementation

• Increased productivity for creative workers
• Better work quality and innovation
• Reduced context-switching costs
• Lower stress and burnout
• Improved meeting effectiveness

Common Mistakes

• Assuming everyone can work in one-hour blocks
• Scheduling "quick" meetings without considering fragmentation cost
• Failing to protect maker time organizationally
• Not communicating schedule needs clearly

Use Cases

• Software development teams
• Research and development organizations
• Creative agencies and studios
• Any knowledge work requiring deep focus
• Hybrid roles balancing creation and coordination