Folke said:
Why would time-based things (things with an explicit date?) necessarily be more important than something that does not have a hard fixed date (such as a leaking oil well, where every second counts but the work could take weeks and you have no idea how long it will actually take)? (I have lots of those; not exactly oils wells, but still...)
Well, when one follows GTD, if it's on the calendar, it's a top priority, must be done at or by that time or bust. So, there shouldn't be anything
not important on the calendar
And it's not so much that they're more important - just that they're so important or date-sensitive that they should be considered before changing one's plans. So, if my oil well broke but I had a meeting with my director on my calendar, I consider whether or not that meeting is more important than fixing the oil well.
Folke said:
Why would you even begin to use dates to indicate importance, and then be forced to continue to use dates for other things, too (just to prevent them from dropping under the horizon of all the stuff that you have put dates on)?
I don't use dates to signify importance - I use my calendar to manage my time. I never schedule tasks for certain days unless they must be done specifically on that date or by that date. But I do schedule my practice sessions because they are a meeting between me and my instrument that, if not met, will have consequences. It's not like skipping one practice session means I can just do it tomorrow. Tomorrow's practice session will be harder and longer to make up for missing today's.
Folke said:
Why would you necessarily call the unscheduled time "free"? You are probably very busy doing your unscheduled important things, aren't you, or doing unscheduled things that make excellent use of your current context? Time is still precious.
I call any time not booked on my calendar "free." I'm pretty sure most people do, too. It's free from obligation time. Free from meeting time. Free to do tasks time. I'm not exactly sure why this is relevant to the conversation...
Folke said:
I totally accept that many (the majority, probably, especially outside of the GTD camp) embrace the use of dates. I also totally acknowledge the fact that GTD has provided no effective and consistent solution for making time-critical date-less things more visible - other than pushing the least interesting things into Someday to lessen the clutter. And I totally accept that we all do what the heck we want to make it work for us, whether it is XYZ or GTD (some will always insist on the latter). So I definitely support your intentions.
It's not just my intentions - it's what I've been saying.
Folke said:
I can even imagine that perhaps music practice for an imminent recital requires x repetitions in y days to make it stick, and that you need at least z hours between each rehearsal, such that in fact you land on a quite precise time schedule that you could legitimately classify as "indirectly hard". Wouldn't surprise me at all. If that is what you are saying then I would agree with you completely. I even had such cases myself that I handled in precisely that way. Nature is also a "hard" factor (memory retention, time to stabilize, and many such things).
This is exactly the point I'm trying to make. Music is a bad example for GTD and productivity philosophy because it doesn't follow the same rules many other situations do. Trying to turn this thread into a discussion on time-based task management philosophies isn't really the place to do it, because this is an odd case. Prepping for a recital is like prepping for a complex presentation. You can work on it each day, make progress each day, and still not be ready by the deadline. You must accomplish certain tasks in a certain order by a certain timeframe in order to effectively complete the project. Thus you are managing your time. I'm not a huge fan of putting "8-9pm practice instrument" on my calendar; I put "Master etude 21 at 145bpm" as an all-day event. It's a task that must be accomplished today to keep my ability to complete all other project tasks on track. If I don't complete this today, then the etude for tomorrow is thrown off, and on down it goes until you're 5 days before the recital and must practice 9 hours a day to get everything finished
I'm about to launch a side project for myself, where I have a defined amount of time to get a defined number of things finished. I want to space them out over the course of the project (it's a year long), as I'll be blogging the process. The only effective way I can think of doing this is by setting mini-deadlines for myself to keep the project on track. Sure, they're not "hard" deadlines, but I just don't understand why it's bad to put them on the calendar. I want to space this project out because it'll flow better, it's meant to take a year to complete, it lets me accurately gauge what time I have available for other projects, and keeps me on track to complete it in a reasonable and comfortable pace. I do not want to finish it halfway through the year. I do not want to be doing 3/4 of my items in the last 1/4 of the year. I'm curious how the date-adverse would handle this project, since the only real "hard" deadline is 1 year from the project's start date.