Folke said:
Seems like David nowadays expresses a view which is somewhat closer to the mainstream view. I am sure that will go down well in most camps.
This whole calendar thing has been sloshing around in my head, along with various other issues about time management.
And suddenly today I conclude that there's a way--a way that looks obvious to me once I see it, though I didn't see it five minutes ago--to see the suggestion of blocking off personal time as BEING counter-culture.
Specifically, it's counter to the multitasking, interruption-embracing, extrovert-embracing culture that seems to dominate business more and more. If I were going to sit down and write a long essay about this, I would take lots of quotes from DeMarco's PeopleWare and Cain's Quiet.
These days, a whole lot of people are sitting in cubes, often in cubes with half-height walls, or shared cubes. And they're often expected to respond promptly to company chat messages, and phone calls, and people dropping by their office, and emails, and pings from problem report systems, and birthday cake gatherings, and, look, Mary and her husband brought the new baby in to visit!
One of DeMarco's books had a sequence of log entries from a programmer who was asked to log her work time, for a study of interruptions. I remember it as looking rather like:
9:15-9:18: Coding
9:18-9:22: Question from manager
9:22-9:30: Coding
9:30-9:35: Question from coworker
9:35-9:37: Coding
9:37-9:45: Support call from customer
And this sort of constant interruption is what we're SUPPOSED to thrive on, in our multitasking-embracing, extrovert-celebrating culture. In many companies, if you seek any relief from the interruptions, you're the bad guy, because your coworkers and customers are the reason for your work, blah blah blah. The fact that you can't DO that work for them if they keep interrupting you every five minutes (sometimes literally) is not necessarily accepted.
And on the other side, the "maker's schedule" argues that certain work, such as programming (among many many other types), really requires uninterrupted blocks of FOUR HOURS or more. And the idea that getting into "flow" for a task requires twelve, or fifteen, or some similar number of minutes, and that every interruption restarts that process, means that the programmer above will essentially never be able to really program.
So time-blocking so that you can work without social interaction every few minutes is, to a substantial degree, indeed counter to the current culture.
Now, that all sounds a little bit like I'm saying that swimming with the culture is bad and swimming against it is good. I'm not saying that. But I am saying that this shift in the GTD method--and I too perceive it as a shift--suddenly doesn't look to me as if it's been made to make the GTD method more palatable to those who are used to the other more traditional methods, but instead to acknowledge an increasingly common reality of many workplaces.
Unscheduled time might be better for a large percentage of people IF they had unscheduled time that they had control over. We could argue the best strategy in that ideal situation, forever. But many people don't have that control, and have to take conscious action--perhaps like scheduling long meetings with themselves--to get any control at all.
I have, in fact, heard of groups of programmers commandeering a conference room for a few hours--or a few days, if a deadline is coming up--just so that they could work there in uninterrupted silence. Our extrovert culture respects what looks like a "meeting", and it may take it a good long while for it to notice that that "meeting" is four people typing frantically on their laptops with their headphones on.