How does "Batch meetings into one or two days per week" work?

Even a single meeting on an otherwise clear day fragments two blocks (before and after) and imposes an anticipatory cost — the maker cannot fully commit to depth knowing an interruption is coming. Concentration-day batching eliminates this anticipatory overhead entirely and lets the maker enter blocks without a mental reservation.

How does "Communicate your schedule mode to collaborators" work?

Most schedule fragmentation is not malicious — it is the result of collaborators following meeting norms without knowing they conflict with maker work. Explicit, one-time communication about your structure shifts the frame from "unavailability" to "professional craft practice," reduces social friction, and prevents the repeated individual negotiation that is itself a concentration cost.

How does "Offer office hours to concentrate collaboration" work?

Office hours solve the social contract problem: protecting maker time feels selfish unless collaborators have a reliable window. By providing a concentrated, predictable access window, you give people a legitimate path without granting open access to the full day. This also batches low-priority requests that would otherwise arrive as interruptions throughout the day.

How does "Align maker blocks with your peak energy window" work?

Glucose, cortisol, and alerting neurotransmitter systems follow a circadian pattern that produces a peak alertness window for most people in the late morning. Cognitive demand during this window extracts more output per unit of time than the same demand during a trough. Scheduling meetings, email, and administrative tasks in the trough — not in the peak — is a structural energy allocation decision.

Maker vs Manager Schedule

Q: How does "Audit which schedule you’re actually running on" work?

Most knowledge workers drift into a de facto manager schedule by social default — meetings fill gaps without intentional placement. Naming which schedule your output actually requires makes the mismatch visible and converts a diffuse frustration into a concrete design problem you can solve.

Q: How does "Protect at least one half-day maker block per workday" work?

Research on expertise and creative output consistently shows that meaningful progress on difficult problems requires reaching a state of sustained engagement that takes 15–20 minutes to enter. A block shorter than ~90 minutes rarely reaches that depth. Protecting the block in the calendar is the structural move that makes all other tactics possible.

Q: How does "Use a start and end ritual to enter and close maker mode" work?

Habit cues reduce the activation energy required to enter a state. A consistent startup sequence — the same steps in the same order — becomes a conditioned signal that triggers the shift toward sustained concentration, bypassing the need to re-decide to start each time. A shutdown ritual creates a cognitive "off ramp" that reduces unfinished-task rumination after the block ends (the Zeigarnik effect: unclosed tasks stay active in working memory until intentionally closed).

What is the maker vs manager schedule and how do you use it?

Paul Graham’s framework distinguishes two fundamentally incompatible time structures: makers need long, uninterrupted blocks to produce creative or technical work, while managers run on hourly slots. Mixing meeting culture into a maker’s day destroys the sustained concentration that deep output requires.

Paul Graham’s 2009 essay articulated something practitioners had felt but rarely named: makers and managers don’t just have different jobs, they operate on incompatible time architectures. A meeting dropped into a maker’s morning doesn’t cost one hour — it costs the entire contiguous block that deep work requires. Understanding the distinction is the prerequisite for deliberately designing a day that matches how you actually produce value.

Practices

Audit which schedule you’re actually running on

Identify whether your work requires maker blocks, manager slots, or a hybrid — and how well your calendar reflects that.

Protect at least one half-day maker block per workday

Defend a contiguous 3–4 hour stretch of no-meetings time as a non-negotiable structural element of the week.

Batch meetings into one or two days per week

Cluster all coordination into designated meeting days so the remaining days stay structurally intact.

Communicate your schedule mode to collaborators

Tell your team when you are in maker mode and what that means for response times.

Use a start and end ritual to enter and close maker mode

A consistent pre-block ritual cues the brain to shift into depth; a shutdown ritual seals the block and prevents cognitive carry-over.

Offer office hours to concentrate collaboration

Designate one or two open windows per day when collaborators can reach you freely, then protect everything else.

Align maker blocks with your peak energy window

Schedule your hardest maker work when your cognitive resources are highest — usually within 2–4 hours of waking.

Practice this with IX Coach

Reading about a practice changes nothing on its own. IX Coach turns these into a guided, adaptive routine — discerning where you are in real time and walking the practice with you, session after session.

Practice this with IX Coach

IX Coach: 7 days free, then $40/month (about $1.30/day).

Maker vs Manager Schedule

Practices

Audit which schedule you’re actually running on

Protect at least one half-day maker block per workday

Batch meetings into one or two days per week

Communicate your schedule mode to collaborators

Use a start and end ritual to enter and close maker mode

Offer office hours to concentrate collaboration

Align maker blocks with your peak energy window

Practice this with IX Coach

Related