MENTAL MODEL · M13130

Maker's vs Manager's Schedule

SystemsHigh supportTime Management

Included

Updated 2026-08-17

Loading revision record…

INTRODUCTION

English translation pending.

CORE DEFINITION

A model of working time introduced by Paul Graham in a 2009 essay. The maker's schedule belongs to people whose work requires sustained concentration, such as programmers and writers: time is organised in half-day blocks, and a single meeting can fragment a whole block and destroy the value of the rest. The manager's schedule belongs to those who coordinate, and it is organised in hours, with meetings filling the day and switching costs being small. The two are structurally incompatible, and the model's central warning is that a maker forced onto a manager's schedule loses productive capacity without anyone intending it.

SCAFFOLDING EFFECT

psychology

Reduce cognitive load

- Calendar design: Block half-day units for maker work and cluster meetings into a separate part of the week. - Meeting cost accounting: Count a meeting as the whole block it breaks, not just the hour it occupies. - Team negotiation: Agree explicit no-meeting windows so coordination does not silently consume deep work.

anchor

Anchor fast decisions

Deep work requires loading a large amount of context into mind, and that context decays quickly once attention is diverted. The cost of an interruption is therefore not its duration but the reload time it forces, which can exceed the meeting itself by an order of magnitude. Because managers experience switching as cheap, their scheduling behaviour optimises locally and imposes a cost they cannot observe, so the mismatch persists unless it is made explicit and bounded by an agreed rule.

MINIMUM ACTION

In progress 0/1

Practice this model in one real situation:

Classify your work into maker tasks needing long blocks and manager tasks needing coordination. 2. Reserve two or three half-day blocks per week and mark them unavailable. 3. Cluster meetings into one or two designated days or into the end of the day. 4. When accepting a meeting, ask which block it fragments and whether the content could be handled asynchronously. 5. Review monthly whether the protected blocks actually survived.

Check to track your progress (stored locally)

Learning progress0%

account_treeGenealogyexpand_more

menu_bookReferencesexpand_more

Source support: Explicit

link
analogypkm.comhttps://analogypkm.com/experience/mental-models/zh/164_制造者与管理者时间表.htmlZH · Explicit
verified

RELATED MODELS