- Although I really <3 Julian's ideas around multi-layered calendars, I don't know that I can completely buy into scheduled tasks. [[Bradley, August]] introduced me to the idea of "Do Dates" -- dates on which you plan to complete a task, but not an actual deadline. - This builds on [[Allen, David. 'Getting Things Done', 2001.]], and the idea that the calendar is _only_ for "must-do"s -- what or where you need to do / be or face negative consequences. - "Do Dates" gave me the flexibility of scheduling my tasks to better manage my workload _without_ assigning arbitrary deadlines to myself. - But a [[{6a} layered calendars|layered calendar]] presents a whole new possibility that doesn't fit into either ideology... Julian proposes that tasks _should_ be on your calendar. And it makes sense; tasks _do_ need _some kind_ of constraint. Adding them to a calendar requires you to estimate the amount of time a task will take; it requires you to make time for it; it requires you to [[treating to-dos as calendar events is like playing tetris with time|play tetris with your time]]. - On the one hand, I feel resistant to this kind of scheduling with how many random tasks, etc. pop up throughout the day. On the other hand, it feels exciting. It feels more final. It feels like a _real plan_ instead of a mostly-empty canvas. - [[how can gtd be updated with new linked thinking]]