What It Is

Maker Time refers to uninterrupted blocks of time (4+ hours) needed for creative, cognitively demanding work. The concept comes from Paul Graham’s influential 2009 essay “Maker’s Schedule, Manager’s Schedule,” which distinguished between two fundamentally different types of workdays.

The #MakerTime hashtag represents the struggle to protect deep focus time in a meeting-driven workplace.

Paul Graham’s Essay

Y Combinator founder Paul Graham wrote in July 2009:

Manager’s Schedule – Day divided into 30-60 minute slots (meetings, calls, emails). Switching every hour is normal.

Maker’s Schedule – Day divided into half-day or full-day blocks. Makers (programmers, writers, designers) need long stretches to enter flow state.

The conflict: One hour-long meeting can destroy a maker’s entire day because:

• It splits the day into two short blocks (before and after meeting)
• Anticipation of the meeting prevents deep focus beforehand
• Momentum is lost after the meeting

Graham’s insight: Managers don’t understand why makers hate meetings, because managers operate on a fundamentally different rhythm.

Why Makers Need Long Blocks

Flow state – Takes 15-30 minutes to enter deep focus (Mihaly Csikszentmihalyi)

Complex problem-solving – Holding entire systems in working memory (code architecture, plot structure, design patterns)

Momentum – Each interruption requires 10-25 minutes to rebuild context

Creative breakthroughs – Often come after sustained struggle (hours, not minutes)

Examples of maker work:

• Writing code or debugging complex systems
• Writing articles, essays, novels
• Designing user interfaces or graphics
• Composing music
• Mathematical proofs
• Strategic planning

Manager vs Maker Conflict

Manager perspective: “It’s just an hour. What’s the big deal?”

Maker perspective: “That hour splits my day in half. I effectively lost both halves.”

The asymmetry: Managers can schedule meetings around their own maker time, but individual contributors often can’t control their calendars.

Solutions

Office hours – Makers set specific times for meetings (e.g., 2-5pm); protect mornings

No Meeting Days – Company-wide policies (No Meeting Wednesdays, Focus Fridays)

Async-first – Default to Slack/email; meetings are rare exceptions

Batch meetings – Stack meetings on certain days; leave others meeting-free

Defend the calendar – Block maker time as “Busy” or “Focus Time”; decline non-essential meetings

Maker mornings – Reserve 9am-12pm for deep work; meetings in afternoon only

Workplace Adoption

Tech companies embraced maker time principles:

Atlassian – No Meeting Wednesdays since 2013

Facebook – “No Meeting Wednesdays” pilot (2012+)

Google – Maker Mondays (some teams)

Basecamp – Library Rules (no talking in main room during mornings)

GitLab – Async-first culture (meetings discouraged)

Remote Work Impact

Pandemic remote work (2020+) initially seemed to help maker time:

• No commute = More time
• No open office = Fewer interruptions
• Control over environment

But new problems emerged:

• Zoom fatigue – Back-to-back video calls worse than in-person
• Always-on culture – Harder to protect boundaries at home
• Calendar sprawl – Managers filled gaps with more meetings

Criticism

Not all “makers” need full days – Some creative work benefits from short sprints (e.g., 30-min writing sessions)

Collaboration suffers – Extreme protection of maker time can isolate people

Privilege – Individual contributors with autonomy can protect time; junior employees often can’t

Romanticizes isolation – Some breakthroughs come from conversations, not solitude

Manager work is valuable too – Coordination, communication, decision-making matter

Modern Relevance

The maker vs manager framework remains relevant because:

Hybrid work – Companies designing office policies need to respect both schedules

AI era – Deep, creative work becomes more valuable as AI automates shallow tasks

Meeting bloat – Average knowledge worker spends 30-40% of time in meetings (2023)

Graham’s essay gave language to frustration many makers felt but couldn’t articulate.

Sources

• Paul Graham, “Maker’s Schedule, Manager’s Schedule” (July 2009): http://www.paulgraham.com/makersschedule.html
• Mihaly Csikszentmihalyi, Flow: The Psychology of Optimal Experience (1990)
• Atlassian’s No Meeting Wednesday policy: https://www.atlassian.com/