My Weird Issue With GTD

[theilluminated]

Hi, I recommend watching this video first before reading the rest of this post:

http://www.ted.com/talks/derek_sivers_keep_your_goals_to_yourself#t-94132

I use GTD. I use it to keep track of really important things, things that really needs to get done. But I have one issue, and I have had it since I started GTD. I write things down and then have a tendency to lose complete interest in it. Like the video said, if you tell your goals to someone, you ruin your lust for doing that goal. The same happens to me when I write things down and flesh it out.

I have overcome this to a degree due to improved habits, but it's still true to a large extent. The problem is that I can put so much into OmniFocus and then just lose all joy and lust for doing it, thus I only put the really important stuff there. Everything else that is just non-essential is in "whenever I want mode". If I put the non-essential-this-won't-destroy-my-life projects into I can't relate to it at all, because I subconsciously know that I don't care about it.

I know that this might only ring true to me, but I wanted to hear if others have experienced the same thing?

 

[tawaters]

Good video clip. Yes, I understand where you're coming from. When updating or creating new software, the most interesting part for me is the designing - laying it out from a big-picture perspective, figuring out the interactions with other modules, working through various scenarios, etc. Once that's done, I'd like to leave the minor details as "an exercise for the student" and move on to the next project. (In reality, there is always much more to be done than just a few coding details.)

I'd recommend not only tracking your projects & next actions, but be sure to include the 'Successful Outcome' - What do you 'see' when you picture this project (or even NA) completed? Having the details penciled out is good, but it will be clear that's it's not done/complete if it doesn't match the Successful Outcome.

Also, motivation often comes from knowing 'Why' - why it needs to get done; why it's important to us. I've found that documenting that helps too.

Tom