Maker vs Manager Schedule
Paul Graham's influential 2009 essay describing two fundamentally different types of work schedules - makers who need long uninterrupted blocks for deep work and managers who operate in one-hour meeting increments, creating inherent scheduling conflicts in organizations.
Last updated: 2026-03-20 11:27
Overview
In his 2009 essay, Paul Graham (Y Combinator founder) identified a fundamental source of workplace friction: the incompatibility between "maker's schedule" and "manager's schedule." This concept has become foundational to understanding modern knowledge work time management.
The Two Schedules
Maker's Schedule
Characteristics:
- Long, uninterrupted blocks (minimum 3-4 hours)
- Deep focus on creative or technical work
- Single meeting can destroy an entire afternoon
- Needs flow state to be productive
- Context switching is extremely costly
Who Uses It:
- Programmers and developers
- Writers and content creators
- Designers and artists
- Researchers and scientists
- Anyone doing complex creative or technical work
Ideal Day:
- Morning: 4-hour deep work block
- Lunch: Break and recharge
- Afternoon: 3-hour deep work block or meetings clustered
- Minimal interruptions
- Protected focus time
Manager's Schedule
Characteristics:
- Divided into one-hour (or half-hour) intervals
- Meetings scheduled throughout the day
- Constantly switching contexts
- Coordinating people and resources
- Reactive to others' needs
Who Uses It:
- Executives and senior leaders
- Project managers
- Sales professionals
- Customer success teams
- HR and operations roles
Typical Day:
- Back-to-back meetings
- 30-60 minute blocks
- Email/Slack between meetings
- Few extended focus periods
- Constant availability expected
The Core Conflict
Why It Matters
A single one-hour meeting can break a maker's schedule into two pieces, each too small for serious work:
- Morning: 2 hours before meeting (not enough)
- Afternoon: 2-3 hours after meeting (context switching cost)
Result: An entire day rendered unproductive by one meeting
Graham's Insight
"Each type of schedule works fine by itself. 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. But the smarter ones restrain themselves, if they know that some of the people working for them need long chunks of time to work in."
Implications for Organizations
For Individual Contributors (Makers)
Strategies:
- Block "no meeting" days or half-days
- Cluster meetings on specific days
- Communicate needs to managers
- Use calendar blocking to protect focus time
- Decline meetings that could be emails
- Negotiate "office hours" for ad-hoc questions
Tactics:
- "I have Tuesdays/Thursdays for meetings only"
- "Can we batch this with other discussions?"
- "Let me respond async rather than jump on a call"
- Set calendar to show as "busy" during focus blocks
- Decline default 30/60 minute slots
For Managers
Best Practices:
- Understand which reports are makers
- Schedule maker meetings at day boundaries (end of day, right after lunch)
- Batch meetings to preserve maker time
- Use async communication when possible
- Protect team maker time as a leader
- Schedule "office hours" rather than ad-hoc interruptions
Red Flags to Avoid:
- 11am meetings (breaks morning focus block)
- 2-3pm meetings (breaks afternoon block)
- Scattered meetings throughout the day
- "Quick 15-minute call" culture
- Default to meetings instead of docs/email
For Hybrid Roles
Many people need both:
- Tech leads: Coding + coordination
- Design managers: Creating + managing
- Product managers: Building + aligning
Solutions:
- Designate maker days and manager days
- Morning maker time, afternoon manager time
- Ruthlessly protect maker blocks when needed
- Communicate which mode you're in
- Use different notification settings for each
2026 Adaptations
Remote/Hybrid Work
New Opportunities:
- Flex hours enable maker schedule optimization
- Async-first reduces meeting pressure
- Home office = fewer interruptions
- Calendar sharing makes conflicts visible
New Challenges:
- Always-on culture expectations
- Time zone coordination complexity
- Zoom fatigue affects both schedules
- Harder to protect boundaries
Modern Tools
Helpful:
- Reclaim.ai: Protects focus time automatically
- Clockwise: Optimizes team schedules
- Calendar color coding: Visual maker/manager time
- Slack status: "In focus mode until 3pm"
- Motion: AI scheduling around focus needs
Problematic:
- Calendar tools default to manager schedule
- Meeting culture enabled by Zoom/Teams
- Notification overload fragments maker time
- "Quick sync" creep
Organizational Solutions
No-Meeting Policies
Examples:
- No-Meeting Wednesday (Asana)
- No External Meetings Friday (GitLab)
- Meeting-free mornings (various companies)
- Focus Fridays (Atlassian)
Benefits:
- Predictable maker time
- Better for planning deep work
- Cultural signal that focus matters
- Productivity boost measured in studies
Meeting Guidelines
Best Practices from High-Performing Companies:
- Default meeting length: 25 or 50 minutes (buffer time)
- No meetings before 10am or after 4pm
- Meetings only on Tuesday/Thursday
- Required agenda or meeting is declined
- Max 2 hours of meetings per maker per day
- Recurring meetings audited quarterly
Role Design
Consider:
- Can roles be split into maker-only and manager-only?
- Do leads need to spend 50%+ time making?
- Is "player-coach" model sustainable?
- Should coordination be a dedicated role?
Criticisms and Limitations
Valid Critiques
- Oversimplifies: Many roles need both
- Privileged perspective: Junior employees can't dictate schedules
- Collaboration necessity: Some work requires real-time discussion
- Over-optimization: Can lead to meeting avoidance when meetings would help
- Power dynamics: Makers can't always set boundaries
When to Ignore
- True collaboration requiring sync work
- Crisis situations needing immediate coordination
- Client-facing roles with availability requirements
- Onboarding periods requiring high touch
- Small startups where everyone wears many hats
Measuring Impact
For Makers
- Deep work hours per week
- Context switches per day
- Meeting-free blocks achieved
- Self-reported productivity
- Output quality metrics
For Organizations
- Developer productivity (DORA metrics)
- Feature delivery speed
- Employee satisfaction scores
- Retention of maker roles
- Innovation metrics
Related Concepts
- Deep Work (Cal Newport): Similar emphasis on uninterrupted focus
- Flow State (Mihaly Csikszentmihalyi): Psychological basis for maker time
- Context Switching Cost: Research supporting maker schedule
- Async-First Communication: Alternative to meeting culture
- Time Blocking: Tactical implementation of schedule types
Resources
- Original essay: paulgraham.com/makersschedule.html
- Cal Newport's "Deep Work"
- Basecamp's "It Doesn't Have to Be Crazy at Work"
- Harvard Business Review articles on meeting culture
- Academic research on interruption costs
Related Items
90-Minute Biological Work Cycles
Work scheduling approach based on ultradian rhythms where individuals work in focused 90-minute blocks aligned with natural energy cycles, followed by 20-30 minute recovery breaks. Research shows this rhythm-based approach can boost productivity by 40% and reduce mental fatigue by 50% compared to random work intervals.
Attention Residue
Cognitive phenomenon where attention remains partially focused on previous task after switching, reducing performance on new task. Understanding this explains productivity costs of multitasking and context switching.
Attention Residue Phenomenon
The cognitive effect where switching tasks leaves residual attention from the original task, reducing performance on the new task for a non-trivial amount of time. Critical concept for understanding context-switching costs.
Bermuda Triangle of Productivity
Daniel Pink's term for the 2-4 PM afternoon window when cognitive performance dramatically declines, errors increase, and productivity nosedives due to circadian rhythms.