A reflection on “Maker’s Schedule, Manager’s Schedule” by Paul Graham, nearly twenty years later
We are living in the era of the greatest technological productivity in history. We have tools that generate in seconds what once took days, artificial intelligence assistants available around the clock, and instant access to virtually any information. And yet many people, myself included, report that it is becoming increasingly difficult to find time to think. Not free time, but time to truly think, in depth, and to reflect without interruptions. The paradox is that the more tools we have to be productive, the less time remains for the kind of work that creates the most value for our companies. Paul Graham, co-founder of Y Combinator, the accelerator that launched companies such as Airbnb, Dropbox, and Reddit, described this problem with surgical precision in one of his essays in 2009. What he wrote then is just as relevant, if not more so, in 2026 as it was when it was first published. I discovered it one night while I was reading well past midnight, which is when I usually find time to read the articles that have been sitting in my browser bookmarks for years.
“The mere consciousness of an engagement will sometime worry a whole day.” Charles Dickens wrote that in the nineteenth century, and Graham used it as the epigraph to his essay because he understood that it captured something human beings have felt for centuries — a feeling modern work environments have turned into an epidemic. The essay is titled “Maker’s Schedule, Manager’s Schedule,” and its central argument is a distinction that seems obvious once you read it, yet fundamentally reshapes how we understand productivity: there are two types of people, defined by how they use their time. The manager works in one-hour blocks; a meeting is simply another slot on the calendar. The maker needs uninterrupted half-day stretches; a meeting at the wrong time doesn’t just interrupt the afternoon, it eliminates it altogether. What Graham diagnosed nearly two decades ago in the Silicon Valley context has now become the central challenge of any organization that relies on critical thinking to generate value.
The distinction he identified entails a consequence that his essay mentions only in passing, yet deserves closer examination: when both types of schedules coexist within the same person, they do not balance each other out. Instead, one consumes the other. And this dynamic has perhaps intensified this consequence more than any other in recent years, as our productive capacity has expanded through generative artificial intelligence tools. This transformation has increased our output and enabled us to assume additional roles, almost overnight. It has also produced a parallel consequence: the cannibalization of our capacity for sustained concentration. What is most revealing is that this cannibalization does not manifest as meetings or visible interruptions, but rather as a new category of cognitive demand that Graham could not have anticipated when he wrote his essay.
What Graham could not have foreseen in 2009 was that by 2026 there would be a third type of demand for our attention, distinct from both the manager’s schedule and the maker’s schedule. Generative artificial intelligence tools do not request meetings or create interruptions in the conventional sense, yet they demand something just as costly: constant evaluation. Each week brings new tools that promise to transform a given process, replace our jobs, or at the very least reshape the way we work. Every new capability unlocked by a model raises an immediate question: should you integrate it into your and your team’s workflows? For a manager, this represents neither shallow work nor deep work, but rather a permanent state of technological vigilance that consumes cognitive energy without producing any concrete deliverables. It is the modern equivalent of what Graham described as the cascading effect of a mid-morning meeting: you don’t just lose the time spent in the meeting itself, but rather the anticipation of having to evaluate something new keeps you constantly second-guessing about how you work. An abundance of possibilities thus becomes a sophisticated form of technological paralysis, which can quietly erode our productive capacity even as we immerse ourselves in promises of infinite productivity.
The answer to this paralysis is not to ignore these tools, nor to adopt all of them without discernment. The answer is to develop a capacity that neither the maker’s framework nor the manager’s framework take into account: the ability to take a step back from the business and look it as a whole rather than simply reacting to its demands. Graham named two figures because those were the ones organizations were capable of recognizing. But there has always been a third that was never given a name of its own: the thinker. In small companies, that role falls almost invariably to the founder or director, who carries it out in fragmented ways, at the margins of the day, squeezed between tasks. And yet it is the role most needed in a world where new tools come out every week and one wrong decision about technological adoption can cost months of work. Paradoxically, it is also the role to which the least time is dedicated in the conventional workday, precisely because it doesn’t produce tangible deliverables, meeting minutes, or appear in any productivity report. The task of deciding what to automate, what to delegate to a tool, and what to preserve as irreplaceable human judgment cannot be completed between notifications. The thinker’s schedule has no fixed structure; it requires exactly the kind of space that the conventional workday never sets aside for it, neither the eight hours of a day replete with meeting, nor the maker’s uninterrupted half-day stretches. It is the time that each leader must deliberately carve out outside their operational agenda: a weekly block free of meetings, a morning without notifications, the late-night hours that many small business owners are already using without having given them a name yet.
For years, I have done a significant portion of my most meaningful work during late-night hours. Not out of discipline, but because that’s when the conditions that the conventional workday systematically eliminates finally exist. The house is quiet: no notifications awaiting response, no phone calls, and no dogs barking at the delivery driver. While you aren’t forced to constantly switch contexts to address the multiple demands a manager juggles throughout the day, you maintain all of the pieces required to keep the engine running very much at the forefront of your mind. What neuroscience refers to as a flow state requires only two conditions: at least fifteen to twenty uninterrupted minutes to get started, and the absence of interruptions during the work block. And, for me at least, some nuts to snack on. At night, those conditions arise naturally. There might not be a report thatresults from these nocturnal hours, but there will be a decision: this tool is worth testing, this one might be able to change the way we work, and this one, despite being all the rage, isn’t a good match for who we are.
So, the relevant question in 2026 is not whether we should be working at night, but rather why our workdays are structured so that those conditions exist only outside working hours. The challenges we face, as well as those that will shape the fate of entire industries in the coming years, will not be determined by our ability to resolve urgent administrative issues, respond to Slack messages at maximum speed, or keep our inbox at zero from nine to five. They will be determined by our capacity to reflect on the artificial intelligence tools now at our disposal, and on how to integrate these new providers that deliver in seconds what once took weeks to receive, all without allowing our processes and working relationships to fall apart. This, in turn, requires precisely what most companies still fail to protect: uninterrupted time for deep thinking, devoted not to producing more, but to deciding better. It’s a form of time we might call the thinker’s schedule, and it’s the only one of the three that almost no organization has learned how to defend yet. Graham wrote his essay in 2009 to explain why he didn’t want to meet someone for coffee. Seventeen years later, his argument explains something far more consequential: the companies that survive the next decade will not necessarily be those with access to the best tools, but rather those that have learned to create the silence their leaders need in order to think clearly.
In an economy obsessed with output, thinking has become the most radical and necessary act of all.
You can read the original essay at: https://paulgraham.com/makersschedule.html
