[timedoctor]

All of the "problems" that he listed of to do lists are solved by using the "Getting things done" method from David Allen.

I personally hate the method of blocking off tasks in a calendar because it is: a) Not agile (can't adjust your priorities quickly). So you get sick one day then you have to adjust your entire calendar for the next month? b) Very cumbersome and totally not suited to the concept of lists of things to do.

To do lists are perfect for storing information about what you might do in the future. You can create various lists to hold information, so that you don't have to constantly try and remember it. Then each day you prioritize and figure out which tasks you are actually going to work on. The point of the to do list is not to create a list of tasks that you are absolutely going to work on necessarily. Instead it's a way to store information and then jog your memory when you decide what you are going to prioritize and actually work on.

So overall I think the idea of forcing yourself to plan ahead of time exactly what you are going to do several days in advance is a horrible idea and very ineffective. What if something more important comes up on the day? You get a call from Techcrunch that they would like to feature your app. Sorry Techcrunch you're not on my calendar.

[PeterisP]

If you do lose one day, and everything is full, then you do have to adjust stuff anyway, and it forces you to do that.

You don't put things on calendar that you might do - you put things that you will or must do then; and it is important that if something (like that sickness) means that you won't be able to do all X things, then you can know early and choose appropriately which one you won't do in the expected time.

Also, in your Techcrunch example - it makes you informed about the consequences; if you get an option to do a large thing then you'll see what other important things you will be displacing and is it really worth it compared to those other tasks.

[ams6110]

Tangent, but that's a great observation on the agility implied in "agile." So many managers and executives think it means "building software faster" because "agile" == "quick" and you get to skip the requirements and design steps and can just start writing code. What it really means is "accommodating change more easily."

[zokiboy]

No, it that case you will check your calendar and decide based on your priorities in life do you want to reschedule a task you have planned with the new task. With calendar-based systems you usually only plan the current day and for other days you have rough outline how time will be spent.