Analysts run on “maker’s schedule”

Most of those versatile researchers of the data-driven world — the business analysts, creative analysts, or even cowboy analysts — probably run on a different schedule from their managers. Paul Graham’s latest essay compares “manager’s schedule” and “maker’s schedule.”

I’m no analyst, just a writer. But the more analysts I meet, the more I find that analysts and journalists share a surprising number of characteristics. One of them, I think, is the tendency to run on “maker’s schedule,” as explained by Graham:

When you’re operating on the maker’s schedule, meetings are a disaster. A single meeting can blow a whole afternoon, by breaking it into two pieces each too small to do anything hard in. Plus you have to remember to go to the meeting.

Meetings are interruptions. They mess up any breadcrumb trail of thoughts that has not yet been laid down in permanent memory. That’s why I’m writing this at 11:39 at night, when I can let a ghost of an idea hang unattended without fear of new email or a phone call dissolving it. Graham writes about once keeping a dinner-to-3 a.m. workday.

Now he wears a VC hat, and he can’t avoid meetings. So he schedules “office hours” at the end of the day.

He hopes that pointing out the two kinds of schedule will make it easier for the “makers.” Their schedule tends to offend managers.

I hope this insight spreads.

What do you think? Do analysts you know work this way? Post a comment.


  1. Andy says:

    I find that when I telecommute it is much easier to be on a “makers” schedule. The meetings are easier to get out of and less distracting. Plus, you get an extra hour of work at the beginning and end of each day since you don’t have to drive in.

  2. O Reilly says:

    That was a damn great article. It’s so true. Imagine this – go back 100 years – and imagine a bricklayer, carpenter, painter, writer, or soldier getting interrupted every hour for a meeting. Ridiculous. Stop the insanity, you moron managers.

Leave a Reply

Your email address will not be published. Required fields are marked *