Paul Graham’s recent post Maker’s Schedule, Manager’s Schedule, is probably the best I’ve read on the subject and best describes why I detest most meetings.
Paul’s concept centers around two schedule types (he focuses on programmers, but I think it applies to most business roles):
- Manager’s Schedule: dominated by one hour block scheduling – the traditional appointment book.
- Maker’s Schedule: are dominated by half day blocks (at the very least) to accomplish most tasks. (The more challenging the task, the bigger the block, obviously.)
He then takes a look at scheduling meetings for both schedule types:
When you use time that way [note: Manager's Schedule], it’s merely a practical problem to meet with someone. Find an open slot in your schedule, book them, and you’re done.
Or rearrange blocks. It can get complicated, but it’s a fairly simple problem to solve.
But, take a look at scheduling using a Maker’s Schedule:
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.
Breaking the day up pretty much ruins any chance of getting anything productive done. I know I’ve found this to be true. And that is just considering going to the meeting, not preparation (which on some occasions I’ve found folks don’t do, which make the meetings even more of a waste) or (gasp!) meetings to talk about meetings. (Yes, you read that right.)
I love