Here's my first impression: I think you've jumped ahead to _tools_,
and you need to stop and internalize the _habits_. The tools are a
distraction when you're starting.
OmniFocus, a tickler file, and a hipster PDA will serve well -- it's
the set of tools I use, and they encompass a quite successful GTD
implementation (he said, modestly ;)). But you might want to put them
all aside for a bit.
You need to get in the habit of keeping your commitments outside your
head: externalize.
And you need to get in the habit of looking externally _for_ those
commitments, rather than in your own head.
My off the cuff suggestion is to grab something cheap and dumb. Like a
shitty, three-subject notebook from the drugstore, if you can carry
that around. Or 8.5x11" printer paper and some cheap folders. You're
going to ditch it, and you don't want to get attached to it.
If you work in a single location and don't want to carry things
around, [index cards in piles][1] will work. That's how I internalized
the habits and patterns. But it's easy to get fetishistic with stuff,
and that's what you want to _avoid_. Pick something _not sexy_.
[1]: http://www.flickr.com/photos/jazzmasterson/sets/48077/
Do the simplest possible thing that can hold the shape your life will
take when it's outside your head. A lab notebook and a file folder
will do. Just make sure your tools are not interesting in and of
themselves, so you focus on your "stuff."
I hope this will help you figure out things like what a project means
in your personal life. The only way to determine that is to try, fail,
reflect on your system _weekly_ (and no matter what DA says, when
you're starting your reviews will take _as long as they take_), and
then scratch out the stuff that's not working and make it new.
This is a lot of work. A LOT.
The metawork involved in really internalizing GTD is a huge hidden
cost. But if it's worth it to you, it'll be worth it. (Yes, that was a
tautology. I'm on coffee prime, shut up.)
At its worst, reflecting and refactoring your externalized life is
make-work in the service of a fetishized "system" that serves
primarily to perpetuate itself.
At its best, reflecting and refactoring your externalized life is
reflection on your actual life, your priorities, and the ways in which
you're committed to implementing them in the real world. That's the
key word: implement. As in, action.
The last, best advice I can give is, when you find yourself noodling
with the system, STOP. Reboot. Take a breath, move to your action
list, pick something, and just _do_ some of the stuff on the list.
Keep doing, and keep implementing, and fix the friction as you go.
That's where the fancy tools come in.
Cheers.
--
"The universe tends toward maximum irony. Don't push it." -- [jwz][]
[jwz]: http://jwz.livejournal.com/801607.html
Don't worry about it. You need *a* method of tickling, and the tickler
file can be many different methods. If you use your iPhone all the time, it
might be a use for that software you own. I don't know if it would work, but
my point is that 43 Folders are just one way to accomplish the goal.
> -I carry a hipster-PDA and a Fisher Space Pen with me everywhere but
> probably don't use them for there intended purpose just because it has
> become more of a habit to throw them in my pocket and then forget
> about them.
That's a problem. You need baskets to collect items. It doesn't matter
what they are, but you need to collect in places to dump into your inbox to
process.
> -I get bursts of energy but I am a scatter brain when I do. Blame
> coffee or a personal problem I don't know.
GTD works with a scattered mind. In fact, it's a nice cure. When you
have a stack of next actions, you don't have to think... just do.
> -I have such an issue with identifying a project.
> Let's say I have to replace my garage window. I kind of think that
> that should be a Project with actions to follow that however if I were
> to write down Replace Garage Window somewhere??? I wouldn't have the
> slightest clue on how to go from there. Now I know that that consists
> of a few steps/actions to complete but to me I almost feel like by
> breaking it down I am complicating a simple task. I should figure a
Me? If I had all the items I needed, I'd just have it be Replace Garage
Window. It's a simple task and it falls under the "I have everything here to
do it and it can be done in one push of action". If you need to pick up
something from Home Depot, that's one more task... which leads to...
> -Contexts are also difficult for me to come up with.
> I mean the basics are okay but the basics are just that basic, and
> individuals have there own different contexts that they add. I have a
> context like...fixer mode, anywhere, dreams, writing, small
> stuff.....those I pulled right out of my Omnifocus.
Keep contexts location oriented. Not necessarily your location, but what
is in front of you (thus the @phone context). I use @home, @desk, @out, etc.
Your window would have an @out item to pick things up, then @home to fix it.
Thus:
Garage Window Repaired
@out Home Depot - Pick up glass (16"x16") and caulking
@home Fix garage window
At review, toss the project into your @out stack -- into your iPhone, bag,
pocket or HPA (in my case, I use 3x5 cards and have a carrying case from
Target). When it is done, it goes back into the inbox and shuffles back out
into your @home stack. When my work day is done, I hit my @home stack and
fix the window.
Keep in mind that the basic principles are sound and there are many many
mechanical ways to implement them... and then you can even dink with some of
the principles. You just need something that you'll use.
--
Evan "JabberWokky" Edwards
http://www.cheshirehall.org/
615.686.9538
Yup -- that's what I meant at the end of my reply, only Josh is more
succinct.
One thing that seems like a good idea is to try using GTD to manage one
corner of your life, not the whole thing. Collect, review and do for that
one aspect and nothing else. With fewer items you can get the hang of it
easier and you're not sitting with a huge stack that sucks the life out of
you (and you're not wasting your time making a stack rather than doing
things).
Although it doesn't apply to everybody, having a significant other who you
live with (or at least have a daily routine with) is a great benefit to
something like this. It doesn't even have to be a romantic relationship -- a
child who is old enough to have regular homework. My wife and I review
together -- and that's both the GTD kind and also the "so, what happened
today for you?" kind of review. I have a friend who has two children and
they have a Sunday date to review their school and social lives. They don't
do GTD, but they do review their notebooks and tests. At the core level GTD
is two things: a way to keep on top of everything and a way to have what to
do next ready when you're at that point. Doing a regular review is
absolutely essential to the first part.
Routine is good, and once the mindset is established it can occur
anywhere. We review at home, out, while travelling... it just kind of has a
mental "click" and we're both taking out our systems and chatting as we go
through everything we share. Meanwhile, she color codes her lab books and I
figure out how far behind I am in publishing. :)
> Hi Russel,
> Considering your situation, as some other people have already
> recommended, I also recomend trying very simplistic low-tech tools
> like a pocket note book.
[...]
I have a further thought, after all the replies to Russel.
I used to use an entirely paper-based system for GTD, which I no
longer do: I use OmniFocus on the mac and iPhone, and it works better
for me than paper _ever_ did.
That is because, once I understood the habits, and had a kind of
information architecture of my own life developed on paper, I simply
translated that onto the computer, and moved on.
Paper is a phenomenal input mechanism, and it is a quiet medium: it
gives you space to find the shape of your thoughts. But you have to do
all the mental work of tracking what relates to what. In my GTD
implementation, at least, that is quite a lot of work.
The computer is sometimes a good input mechanism (OF is quite good at
this), and takes on the extra work of tracking and locating what you
need. And having my GTD system on my iPhone, in the shape of OF for
iPhone, is invaluable.
(To get an idea of how valuable it is: before third party applications
worked on the iPhone, I was using a local Rails app on my OF mac,
which would parse my OF database with RubyApplescript, then display
the contact list through a browser, which I managed to get working
outside the house with a dynamic DNS and port forwarding. So, I had
slow, read-only access to OF as long as I had wifi or cellular signal.
That sucked, but it was better than nothing.)
So, by all means. Develop the habits without fancy tools. I think
that's the best way to learn it. But don't feel like you have to stay
there: the fancy tools exist for a reason.
One final thought:
OmniFocus can be stunningly complex. That is because its purpose is to
be shaped in the mold of your external brain, and configuration ==
complexity. When you have your GTD system implemented, and you want to
import into OF, I would suggest you create a single project in OF,
like: "Bend OmniFocus to my will."
Then make it work for you, by working within its system.
That's how I did it, and look at all I've accomplis--
Um.
*crickets*
Excuse me, I think I have some stuff to do.
Cheers,
Josh