If you have read anything that I have written on Lifehack.org, you probably already know that I am a complete Getting Things Done junky. But, like any good lover of productivity pr0n, I tend to look online for the “next best thing” when it comes to productivity systems and implementations.

Recently I listened to Scott Hanselman’s software development podcast, Hanselminutes, on his own personal productivity system. This guy is a telecommuting, programming animal, so I was intrigued to see what he had to say.

Besides the normal use of GTD, Steven Covey’s 7 Habits, and the infamous Pomodoro Technique, Mr. Hanselman mentioned a book by another programmer, J.D. Meier, called Getting Results the Agile Way. This system takes some cues from the Agile software development methodology (more here at Wikipedia) and is a system based on producing results rather than activities, having boundaries and set tasks and goals you want to accomplish, and making time your best friend.

This system seems pretty interesting and effective once you read into it. Let’s take a look at the key points of the Agile Way productivity system.

What’s so different about this system?

If you are a GTDer you may sometimes feel that you are bogged down in the minutiae of everyday task management, blindly checking off tasks as you finish them. If you are a 7 Habits kind of person then you may get caught up in the question, “What’s my life purpose?”.

The Agile Way offers a slightly different approach . It concentrates on the outcomes of your actions rather than the activities of checking things off your list. This approach has more of a directive off the bat, whereas GTD says that you need to clear the runway level before you get to defining what you want to do with your life.

The Agile way also is all about reflection and making sure that you are producing some sort of results in your days, weeks, months, and years. The system takes the idea that projects and tasks are always changing, and because of that it is important to make sure that your plans of action are still valid and still producing results.

Something else that Meier’s stresses is the power of “3″, and the first he lays out is the idea of using your Time, Energy, and Technique to continuously produce results. He says that if you manage your energy effectively by living with passion regarding your work, you can use your time, energy and passion, to produce better and more quality results.

The system explained

You are probably thinking, “OK, enough with the na-na-nu-nu, energy equals results stuff. How do I use this system?”

Meier’s has a really great “getting started” guide on the book’s site. Basically the system revolves around the power of “3″. Here are the basic steps:

  • Define 3 outcomes for your day
  • Define 3 outcomes for your week
  • Define 3 outcomes for your month
  • and define 3 outcomes for your year

Basically, you want to identify the 3 things you want to accomplish for your day, week, month, and year and then at the end of each respective period review your results, find where you can grow and improve your technique, and plan again.

The Monday Vision, Daily Outcomes, and Friday Reflection pattern is a simple habit for daily and weekly results. source: http://gettingresults.com/wiki/Getting_Started_with_Agile_Results

Another nice idea is the “Weekly Results” paradigm where you first identify your “Monday Vision”, review your “Daily Outcomes, and then follow up the week with your “Friday Reflection”. This reminds me of the GTD weekly review, but allows you to be even more active with reviewing your actions and results.

There are a ton of extra subtleties to the system, like creating time boundaries for certain portions of your life (Meier calls them “hotspots”) like, work, family, fun, creativity, spirituality, etc. By setting minimum and maximum times for these areas of your life, you are creating some sort work/life balance.

First impressions

Overall, I am extremely impressed with Meier’s system. So, impressed that I couldn’t believe that I haven’t heard of it before. What I like about it most is that it gives you some sort of direction for your days, weeks, months, and years. GTD is awesome at helping you identify and organize what needs to get done, but sometimes falls short in the actual “doing” part of the process. I could totally see a hybrid approach with GTD and the Agile Way to take stock of your current workload and then define what needs done during your weeks.

Another nice thing about the Agile Way is that it is instantly implementable. You can sit down with a pen and paper (or a spreadsheet, Evernote, OneNote, text file, etc. for you geeky types) and start to define your day and week. This allows you to start concentrating immediately and isn’t filled with the initial overhead of GTD.

So, I highly suggest that you take a look at Getting Results the Agile Way. You can pick up the dead tree edition at Amazon or read the entire book at the book’s site.

Love this article? Share it with your friends on Facebook