Site icon Asian Efficiency

Agile Results Series Part 3: Mods

Agile Skyrim

Part 3! In this and the next segment of our Agile Results series, we’re going to show you how to take Agile Results – which is a pretty awesome system – and modify it to work alongside GTD, and other productivity principles.

Part 3 is an overview of all the different pieces and technology that you can use to make this modified system work. It will also outline how to set up and use the system the first and subsequent times through (i.e., the core of Agile Results). Part 4 is about implementing the non-core components of Agile, using devices from GTD or other productivity systems.

The work and process of how this works comes from my own implementation of Agile. In the Agile Results book, Meier states that you should use what you’re comfortable with – whether it’s pen and paper, a spreadsheet or custom software – to implement Agile. I’m going to show you how to do it with tools and apps that you’re already familiar with.

It’s important to make the point that while Agile is a phenomenal system, you need to change it to suit your personality and working style. There’s no need to completely throw out your existing system – just add in Agile components and make them work together. Agile is all about making tweaks, iterating and evolving you and how you work.

The implementation that we’ve come up with at Asian Efficiency is about lining up your goals from the daily through to the annual and beyond level, while creating accountability through support structures. It all goes to this core idea:

Productivity = the amount of time you spend directed toward your goals.

Let’s start by looking at the different component pieces of our modified Agile system.

Component Pieces

Here’s a mindmap of the different components of our modified system:

Areas of Life. These are Agile’s Hot Spots. Essentially, they line up with our breakdown of the different areas of your life (health, wealth, relationships, play, projects, mind, passions). We’ll be implementing these using Stories.

Journals. This is one half of the Rule of 3. It’s the written component, where all the nitty-gritty detail goes. Journals work at the daily, weekly, monthly and annual level. You’ll also be creating journals for Areas of Life, alongside Stories.

Roadmaps. This is the other half of the Rule of 3. It’s the “overview look” of all your outcomes and progress. You’ll only have 2 roadmaps – an annual one, combining annual, monthly and weekly outcomes, and a weekly roadmap, containing weekly and daily outcomes. In case you’re wondering why we recommend 2, it’s come out of extensive experimentation and tracking.

Daily Reminders. This is your list of affirmations, important questions and other reminders you want to see on a daily basis.

Lists. Every productivity system needs lists. In our implementation of Agile, lists are 3-fold: 1) action lists sorted by area, for sprints, single actions, projects, reviews, future lists and life management lists, 2) a how-to-work list that implements a lot of Agile’s inner game concepts, and 3) systems, processes and scripts for life that you use on a regular basis.

Stickies. Confession time: I have a minor post-it notes obsession. I’ve found that posting daily outcomes on a post-it note (digital or otherwise) is useful as a quick reference throughout the day to help with focus. The roadmaps you’ll create can also serve this purpose.

Triage. Like GTD, items still get dumped into an Inbox, and then triaged accordingly.

The Apps

You’ll need a few applications to set up our modified Agile Results system. You can use ANY applications really, but we recommend:

System Setup and First Run Through

Let’s look at each part of this setup.

The Journals

The journals you will keep are where it all begins. Load up your journal application of choice (I suggest Evernote if you don’t have one), and create the following notebooks/folders:

Life Stories

The first thing you want to write down are your life stories. The reason for this, is that clearly writing out statements about each area of your life, clears out and ties together a lot of the inner game and core concepts of Agile Results.

Aside: The concept of stories comes from The Power of Story, by Jim Loehr.

This does not have to be complicated. It’s pretty much a statement of “this is what I’m here to do with each area of my life.” Take your time with this, and realize that it could take up to a day to come up with all the different stories you have going on the first time you do this.

Here are the areas we recommend covering:

The structure of how to craft these stories (modified from The Power of Story), is this:

  1. How each story relates to your mission.
  2. The truth. Make sure you call yourself on any BS.
  3. The old story, including: faulty thinking, faulty logic, content and voice and faulty assumptions. Make sure you dig deep.
  4. The new story, which must: 1) align with your mission, 2) reflect the truth, 3) inspire you to take action. Be sure to include the truth, what would happen if the old story were to continue, show connections between your past and present circumstances, and a rough plan for action.
  5. Read your new story, and ask: 1) Does it take me where I want to go?, 2) Is it grounded in reality?, 3) Does in inspire genuine hope and make me want to take action?

Journal Templates

Here’s the structure of each journal template. You’ll want to create these within your journal software.

For each outcome, you want to use this format:

You can read more about the above format in goal setting and having a why.

Annual Journal

Monthly Journal

Weekly Journal

Daily Journal

First Run

Now that we know what each component entails, let’s walk through setting it up.

We want to do this by timeframe. This means, that the first time through, you’ll have to complete all timeframes. But then each subsequent month, week, or day, you’ll work with those timeframes to keep the system going.

Annually

  1. Create a copy of your annual journal entry template into your annual journal notebook.
  2. Fill it out. This should be straightforward. When selecting outcomes, remember the key Agile question: “If this were next year, what are 3 great results I would want?”
  3. Do an evergreen check or an Agile projection check. See if your selected outcomes are evergreen, in the sense that they benefit you forever, or run your outcomes against different timeframes – 1 year, 5 years, 10 years.
  4. Create an Annual Roadmap. Start a mindmap, and create months January through December. Put in your Annual Outcomes as branches when they’re due. If they’re due at the end of the year, put them in December. Bold and Highlight your outcomes to make them bigger.
  5. For each month in your Annual Roadmap, create a branch for sprints, a branch for that month’s outcomes, and a branch for major events occurring that month (anything that has a significant impact on your time, like a vacation or house renovations).

Here’s an example of an Annual Roadmap:

Annual Roadmap Example (click to enlarge).

We create roadmaps like this in MindManager.

Monthly

  1. Create a copy of your monthly journal entry template into your monthly journal.
  2. Fill it out. Remember that your monthly outcomes should flow directly into your annual outcomes. When mapping out your month week-by-week, remember that it’s a rough plan that can be changed as the weeks happen.
  3. Take the monthly outcomes, and put them into your Annual Roadmap under outcomes for the current month.

Here’s the updated Annual Roadmap, with monthly outcomes:

Annual Roadmap with Monthly Outcomes (click to enlarge).

Weekly

  1. Create a copy of your weekly journal entry template into your weekly journal.
  2. Fill it out, remembering that weekly outcomes should be related to monthly outcomes.
  3. Create a Weekly Roadmap. Start a mindmap, and then create branches corresponding to each area of life: health, wealth, relationships, mind, play, passion projects, personal projects.
  4. Put your weekly outcomes into the Roadmap, and bold/highlight them.
  5. Put your weekly outcomes into your Annual Roadmap too, under the monthly outcome that they correspond to.

Here’s what that looks like:

Annual Roadmap with Weekly Outcomes (click to enlarge).
Weekly Roadmap (click to enlarge).

Daily

  1. Create a copy of your daily journal entry template into your daily journal.
  2. Fill it out. Set your outcomes so they line up with weekly outcomes. Leave journal questions until the end of the day.
  3. Put your daily outcomes into your Weekly Roadmap.

Here’s a fleshed-out Weekly Roadmap:

Daily Roadmap (click to enlarge).

Congratulations! You’ve just done your first run through using Agile Results, and your system is now rocking and ready to go. Now let’s see how it works on a day-to-day basis.

Using Agile Results Daily

Using Agile Results (or any other productivity system for that matter) is basically about remembering to follow the system, and to keep it updated. This may take some willpower in the beginning, but with something like Agile it becomes second nature within a couple of weeks.

Annually

Monthly

Weekly

Daily

What To Do Next

You now have the nitty-gritty details of how to setup and use a modified Agile Results productivity system. You can start right away – grab the tools you’ll need (our preferences – Evernote, MindManager, DevonThink, OmniFocus) draw up your journal entries and roadmaps, and start planning.

In the next (and final) introductory article on Agile Results, we’ll be looking at how to implement some of the more abstract concepts of Agile Results, using some neat processes, tools and systems.

Next Actions

Do you want to see more examples of our personal systems and workflows? We reveal them all on our 3 Lifehacks seminar. It’s completely free and you’ll get to see the exact step-by-step systems and workflows that we personally use to be insanely productive. Register for the next available seminar here.

Photo modified from: imgur

Exit mobile version