The meeting that cost four hours of work

Back in July 2009, Paul Graham wrote an essay that I only recently came across, and I genuinely cannot understand why it took me this long to find it. The piece is called "Maker's Schedule, Manager's Schedule," and from the very first paragraph I had the unsettling experience of reading something that articulated a frustration I had carried for years but never quite managed to put into words. If you work in a creative or technical role and have ever stared at your calendar with a creeping sense of dread, there is a good chance this concept will resonate with you just as sharply.

Graham's central observation is deceptively simple. There are two fundamentally different ways of experiencing time at work, and they belong to two different kinds of people. Managers operate on a schedule built around one-hour blocks. Their day is naturally segmented, and moving between tasks or meetings every hour is not a disruption to their work, it is the work. A meeting that goes well is a productive use of a block, and a meeting that falls flat is just one block lost before moving on to the next. The structure suits them perfectly.

Makers, on the other hand, including software engineers, writers, video editors, designers, and anyone else whose output depends on sustained creative or intellectual effort, experience time in a completely different way. For a maker, the meaningful unit of time is not an hour. It is half a day, a minimum of four uninterrupted hours during which deep, focused thinking can actually occur. Getting into that state of focus takes time. It requires the mind to warm up, to load the problem fully into working memory, and to begin making real progress. That process cannot be rushed, and it certainly cannot survive being interrupted halfway through.

This is where the collision between the two schedules becomes so costly, and where I think most workplaces are failing their makers without even realising it.

Consider a simple scenario. You are a maker. You arrive at work at eight in the morning ready to spend the day doing focused, difficult work. You check your calendar and see a meeting at ten. What happens? You do not simply work from eight until ten and then pop into the meeting as if nothing has changed. What actually happens is more insidious. You think about the meeting. You wonder whether you need to prepare anything. You decide that there is no point starting the task you really need to do because by the time you get into it you will have to stop. So you do something lower value instead: you check emails, you tidy up your inbox, you do the kind of shallow work that feels productive but is not advancing your real deliverables. By the time ten o'clock arrives, you have not done two hours of useful work. You have done very little of it.

Now extend that meeting to include a second one at eleven, and suddenly the two hours between eight and ten and the one hour between the meetings are all essentially lost. You have had interruptions scattered throughout the morning, each one destroying the conditions necessary for real focus. A day that looked busy on paper was actually a day in which almost nothing of substance was produced.

Graham describes a meeting on the maker's schedule as being like throwing an exception in a piece of code. It does not merely switch your attention from one task to another. It changes the entire mode in which you are working. He notes, from his own experience, that even knowing a meeting is coming in the afternoon is enough to subtly reduce ambition in the morning. When you know the day will be broken up, you are less likely to begin something genuinely demanding. That psychological cost is real, and it compounds.

What makes this particularly frustrating is the feedback loop it creates. Managers, often under pressure to hit delivery timelines, respond to slow progress by scheduling more check-ins with their makers. But the reason progress is slow in the first place is frequently that previous meetings have eaten into the focused time needed to actually make progress. The more meetings you add, the slower things go, which triggers more meetings. It is a cycle that many teams are caught in without realising it.

The solution is not to eliminate meetings. Makers are part of teams, and collaboration and alignment are genuinely necessary. The point is that meetings need to be treated as an interruption to a maker's working block, and that interruption needs to be justified. Before booking a meeting with a maker, the honest question to ask is: is this meeting more valuable than four hours of focused work from that person? Sometimes the answer is yes. But often it is not, and the meeting is being held out of habit, anxiety, or convenience rather than genuine necessity.

The practical fix, which Graham himself uses with something he calls office hours, is to cluster meetings together so that they consume as few maker blocks as possible. If you consolidate eight thirty-minute meetings into a single afternoon, you have interrupted one maker block. If you spread those same eight meetings across the week, you have interrupted eight blocks, potentially eliminating thirty-two hours of possible focused work time. That is an extraordinary difference in output, achieved simply by being thoughtful about scheduling.

Teams can build this into their culture with surprisingly little effort. Designating certain days or certain half-days as focus time, during which meetings are not booked, gives makers the predictability they need to plan ambitious work. It allows them to look at a Monday morning and know, with confidence, that they will not be pulled out of their flow at ten o'clock. That confidence alone changes the quality of the work produced.

Makers can help by communicating these needs clearly and without apology. Declining a meeting during a protected focus block and proposing an alternative time during a designated collaboration window is not being difficult. It is being responsible about how working time is spent. Managers who understand the maker's schedule will appreciate the transparency rather than take offense.

For those of us who spend most of our working lives in maker mode, this framework is not a luxury or a personal preference. It is the basic condition under which good work gets done. The organisations that understand this, that protect their makers' time as seriously as they protect their budgets, are the ones that will consistently produce the best output.

If you have not read Graham's original essay, I would strongly encourage you to do so. It is short, clear, and in the sixteen years since it was published, it has not dated at all. If anything, with the rise of open calendars, instant messaging, and the expectation of constant availability, the problem has only grown worse. The conversation it asks us to have within our teams is well overdue.