thank you so much for your open-minded communication in this and other topics.
First: I agree to all four points you wrote about GTD workflow. And I’m glad you wrote this, because I get the chance to better explain my point. I just was talking about a little sub-topic of your “c)”. You wrote:
c) GTD has a concept of “Deferring” or “Scheduling” an action. This is basically a way to temporarily “hide” the action/project from the Next list.
Exactly, I want to hide a future task temporarily from my Next list by scheduling it. So far we’re on the same page. In my last post I contested the way HOW setting up a schedule works.
For example I want to start preparing my tax return somewhere in March, even though the deadline is at a much later date. So I set the start date to March 1st and the deadline to the actual deadline.
Your example fits exactly to my perspective: How you got your schedule date (“somewhere in March”)? In my opinion that’s not the natural way things work. What primary information do you have, when you think about the task “get tax return prepared”? You have a due date and you have a approx. time you need for that task. Why not enter this values in the GTD-software directly? Instead of that you first made a manual calculation for the schedule date (due date minus time to get task done minus spare time) in order to enter a calculated schedule date and a due date. The calculation is very easy, so you probably didn’t recognized you made it. But another contra for your way is, that the schedule date has no strong meaning, because it’s not a primary but a calculated value. So why pin that indirect value to any task in gui?
I can’t say I understand the concept of a repeating due date.
Let’s use your tax return example again. Why not make a repeating task out of that, so you wouldn’t forget to set a new tax return task next year? What are primary values for that?: Repeating due date (every year in july? I’m from germany, don’t know about your law.) and approx. time to finish that task (could be a reminder duration). Again: schedule date is calculated. (and could be a different date every year. Think about 29th february treatment for example). More pro’s for my perspective: Repeating due date is a primary value and could be pinned to task every year (in actual version there is no way to enter it, except of text description). And you would have same handling with not-repeating and repeating task, because in any case there is a due date and a reminder duration.
Sorry for my bad english. Hopefully you did understand my perspective.
Greetings from germany!