I have been a productive worker wannabe for several years now. I have read a ton of books, prescribed GTD as much as I could, bought all the gear in the world that anyone recommended as being the best, and constantly failed at it. It wasn’t until I slowed down, settled with a set of tools and got back to the basics that I started to understand what being productive was.
Being productive isn’t using your gear or being knowing the Getting Things Done flow chart inside and out. David Allen reminds us what being productive is at its most basic level:
“You have to define what done means and what doing looks like.”
It’s really that simple. What I think is so amazing is that GTD is a very basic idea yet when we are thrown into the “rat race” of work and life, we easily forget to apply the basics. Either that or we have yet to master them. Let’s look closely at defining done and doing.
Define What Done Means
This was something that took a long time to “get”. I understood that defining a project was naming something that had more than one action to accomplish, but I still had trouble defining my outcomes with the project. Not so much with smaller things like, “schedule some time with a [insert friend name here] and catch up” but more along the lines of “development new web service testing suite for [insert web service here]”.
There are hard edges with some projects while others are like a big ball of stuff just sitting there and taking up space. We have to be able to get through the stuff, find the things that are important, and then define what complete looks like. Luckily there is an awesome way to do this; use Mr. Allen’s 5 Phases of Project Planning. Here they are in a nutshell:
- Define purpose and guiding principles. (Why is this being done?)
- What is the successful outcome? (What would it be like if this were totally successful?)
- Brainstorm (Get creative and write down and link anything that comes to mind about the project)
- Organizing (Create priorities and an order to the project)
- Identify next actions (keep reading for this)
Now, like I said before, some project are pretty self-evident in what needs to happen. But there are many that are large and nebulous that need a clear outcome and a structure to complete. Once you define what “done” is, then you can move onto deciding what doing looks like.
What Doing Looks like
Coming up with the next action of a project may seem like its easy, but in practice can be very difficult. The biggest problem is that we tend to “over-generalize” our projects and tasks and add things to our lists like:
- Plan birthday party for Amy
- Create brand new web app for ‘X’
- Lose your protruding gut
These are some great things to accomplish, but they are far from being next actions. What we need to do is granularize our projects and get down to the “dummy level” with our tasks. We have talked about this many times before at Lifehack, but it needs repeating as this is the heart of getting more accomplished and being less stressed while doing it.
I liken this to the idea of “cranking widgets” and checking off easy todo tasks off your list one at time. This will eventually lead you to completely large scale projects while keeping yourself way less stressed.
So, instead of “plan birthday party for Amy”, I’d better create a highly doable next action like, “draft a list of people to invite to Amy’s party.” Then I can get the ball rolling. In fact, all it takes to make a dead project move forward is identifying a single next action that you could do given the right context.
That’s what doing looks like.
It’s all about the basics
Like I said before, I know that if you are a GTD or productivity kind of guy or gal that this stuff is pretty basic. But the thing is that staying productive is all about mastering the basics. When life and work sets in and you are bombardo with the “real world” it’s important to know the basics well and use them immediately.