Archives For GTD

Getting Things Done

People who know me well would perhaps call me slightly eccentric, when it comes to my enthusiasm for fountain pens, paper stationary and paper organizers. But those of you who like the feeling of writing with a nice pen in a Moleskine notebook, you should definetely read this article.

It's a great comparison of all the paper based planner systems on the blog How to be an Original.

I’ve been using technological solutions for my calendering and for managing my To Do’s (or Next Actions) for a long time now. The last paper planner I owned and used is pre-2000. My last solution was a PDA I used for planning, contacts and for my Getting Things Done system.But the PDA was stolen recently. Time for a brand new start, and I’m switching back to paper. I know, I couldn’t believe it myself either, but it’s true.

Paper planners are great for Getting Things Done, because of better speed when you want to capture stuff, and when you want to skim your next action lists.

I own a Levenger Circa i A5 size, that I carry around all the time. This was quite an investment at the time I bought. A great system.

But now after reading Lowdevijks reviews, I must admit I feel an urge to get this one: The X47 A6 Timer. It's sooo expensive! Perhaps a new goal in my Weekly Review Reward Programme.

  • Jens Poder

Handling todo's on actionlists is essential in any GTD-system, so it's something I have been striving to get fast and functional for quite some time.

Until I tried Tudumo, I used Microsoft Outlook's todo-lists, since this was on my computer already, and was open all the time. But Outlook was really slow. It boots slowly, and you have to use the mouse all the time navigating the user interface.

Tudumo is the exactly opposite.

  • It's fast booting, so you will get into the app in a split second, instead of waiting for a large app to get ready
  • It has brilliantly chosen keyboard shortcuts, that's intuitive and easy to remember in your workflow.
  • It offers several states each action can be in (next action, someday/maybe, on hold etc)
  • With fast filters and search, allowing you to effortlessly switch between viewing for example all your actions and things on your someday/maybe list.
  • Tags on actions (hit ctrl-t and add a tag)

All this ties together in a great workflow, that is far superior to anything else I've tried.

A quick overview of the app

CallsOnly

Here's a screendump of the app, with a couple of actions in it. The current view is of all the actions tagged with "@calls". The actions are listed in light blue under their respective headings (Anniversary & Attend...). In front of each action is different icons, a red circle for a "next action" and a blue for simply "action". In the bottom of the screen the list of tags are listed, allowing you to choose all the actions with for example "Derek". Clicking All will show the full list of actions.

In the top right corner you can see the find and filtering options. Tudumo lets you search real-time (it lists files as you type). And you can choose which type of actions you'd like to see (next actions, actions + next action, someday/maybe and more).

Handling Incoming Stuff in a GTD-workflow

As mentioned one of the great things about Tudumo is the speed, and how well it integrates with a GTD-workflow.

When something pops into my head, that I need to capture, I just hist WIN-T on the keyboard, and Tudumo launches immediately.

Tudumo starts in the heading used last. I use these headings for my standard GTD-contexts (@work, @home, @pc, @diy, @phone and @errand).

If I'm not positioned in the right heading I can navigate with the keyboard using CTRL-UP and -DOWN jumping to the next or previous heading.

To add something I hit CTRL-N and start typing an action - "brainstorm structure for Tudumo review" - and hit enter. The idea is now captured, and I can hit WIN-T and leave Tudumo again.

Making Frontend Decisions about Actions with Tudumo

So it's fast. But for a GTD-fiend it's essential to be able do to a little more. You want to be able to make and handle effective frontend decisions about your stuff.

The basic question is whether the thing on your mind is actionable or not. If it's actionable, you need to decide whether to:

  • Do it right away
  • Defer by putting it on a next actions list
  • Deferring it to a specific date by putting it in some sort of tickler file or calendar
  • Delegate it, an track it on a waiting for list
  • Handling it like a multistep project with a list of actions to be completed
  • Maybe do it sometime in the future if you feel like it (someday/maybe)

The great thing about Tudumo is, that if it's actionable, Tudumo will handle it!

Menu

Above is the list of "states" that Tudumo will let you choose for a selected action, and the respective key to choose that "state" (1-6).

Next Actions: Next actions are easy. If it's something you want done as soon as possible just hit 1. It's on your next action list!

To check out all your next actions you just hit CTRL-1 to see a list of all next actions.

Deferring to a specific date: If you want to defer something - say, returning the library books - to a specific date, you can put it "On Hold".

You can do this by hitting 3. But it's actually smarter instead to select a "start-date" for the action. Hitting CTRL-SHIFT-D will let you choose a specific date for the action reappear on your lists. On this date you'll get a popup-notifier reminding you about returning your library books, and the action is active again.

To check out a list of all actions "On hold" you can hit CTRL-5.

Tracking Delegated Actions: If you have delegated an action, then just hit 5. This put's it on the "Waiting For" list, where you can track them. You can add a due-date to these by hitting CTRL-D and selecting a time in future where you'll want to check up on it.

If you want to check up on all your delegations hit CTRL-6 and you'll only see actions in the state "Waiting for"

Handling Multistep Projects: When I want to handle a multistep project I use the tagging feature i Tudumo. I have a tag for each project. Hitting CTRL-T on a selected task lets you add a tag. This is done by typing a tag-word; several tags can be added separated by commas. So for a project, say "xmas presents" I just type this into the tag-field, and hit enter.

If you want to enter several tasks with the same tag, say you are brainstorming tasks in your "xmas presents" project, you can click the "xmas presents"-tag in the taglist in the bottom of the screen. This gives you a list of all the tasks tagged this. If you enter new tasks by hitting CTRL-N when in this list, new tasks will inherit the tag from the list. This lets you brainstorm multiple tasks on the same projects.

When finished you can select which projects belong to which contexts and choose the tasks that are next actions.

Someday/Maybe Lists: To add an action to your someday/maybe list you just change the state of the action to someday/maybe. To see all your someday/maybes hit CTRL-7.

Conclusion

So all in all Tudumo is brilliantly suited for those of you using GTD on your computer. It is the best match for my todo-needs I have found so far.

It's fast and flexible. The really nice thing is that the same task easily changes from one state to another.

Of course the best feeling is to hit 4 on a task to mark it "done". But it's very powerful to be able to move a task on a off someday/maybe lists with single keystroke.

So all in all it integrates wonderfully with the GTD-framework.

So if you're looking for something fast, and don't need an app that syncs with PDA's or websites, I really recommend this. It prints lists on paper, but that's it!

Me... I'm all for computerlists and printing pages to my organizer. But it's a little old school. I would be great to have an app with the same usability, that syncs via Google Gears to a website, and lets you sync with a mobile device. But perhaps this is in the pipes.

  • Jens Poder

Technorati Tags: , , ,

Yesterday I made a couple of handy tools for tracking my new Pull-based system for maintaining my GTD-system.

Having split up my 3 hour weekly review routine into bit and pieces, that I perform on demand, made me want to have something to assist my focus on the new system, and help me track my progress.

So I made a template for my Circa Levenger Notebook and a Wallpaper for my desktop.

Here's the template for my organizer:

review_tjekup

With this, I can tick off, every time I perform one of the new routines. This means I can keep up giving myself little rewards for completing weekly reviews.

Here's my new desktop wallpaper

review_baggrund

This is to help me remember each part of my new system. When I sit at the computer, and my mind is frying, then looking at the desktop will help me start clawing my way out of the darkness into "Mind Like Water."

Good Friends

The color scheme for these designs was found on the wonderful website colourlovers. Here you can find 5-part color palettes, that can inspire you when you create presentations and design.

  • Jens Poder

Technorati Tags: , , , ,

Lean GTD #6 – Perfection

14. september, 2007 — 17 Comments

So here we are, at the end of the Lean GTD series. It has been quite an experience for me. There has been two radical changes in my GTD system.

  • A better flow in the stream of efficiency, breaking down the batch & queue processing for about 50% of my stuff, allowing actions I have already commited myself to do, to zoom past the inbox and directly onto my actionslists, and thereby reducing handling time and waste.
  • A pull-based review system, based on a handfull of smaller routines. These routines gets performed on demand, when the corresponding emotions invade my thinking. This have allowed me to free up 3 hours of review-time every week. But more important, it allows me to apply the rigth amount maintenance to my GTD process, adding even more maintenance if things heat up and my mind gets pinned by incoming stuff.

I'm really happy with the result. A great deal of annoying fiddling with the system has been banished, and my ability to keep GTD up and running has been greatly improved.

One of the really nice benefits has been getting rid of great piles of unprocessed stuff and loads of unfinished reviews. Man, have these been haunting me, giving me a bad conscience, and even worse, making me feel like a GTD-looser. Now, these sources of dismay are no part of my life anymore. And right now... I don't miss them.

So now it's time to look ahead. I have been through a phase of radical change in my system. A phase of Kaikaku (I love these japanese words). Now it's time to move onto Kaizen, the phase of gradual step by step perfection.

Having mapped my system thoroughly through this proces, and having clarified the benefits and values the system provides, I will now go into cruise mode, slowly refining it bit by bit, confident that I have have a solid framework in place. I will collect ideas for refinements, and from time to time implement the ones that seems most promising.

I hope some of you have found the series interesting. Thanks for reading. Please share your comments, and... keep it lean!

  • Jens Poder
Technorati Tags: , , , , ,

image

This is part of a series on using LEAN to streamline your GTD system

I want to break down the task of completing my weekly review into smaller actionable routines, and then be able to sense when to apply each routine, instead of doing it routinely according to a schedule. So I'm going to describe each routine, and the emotions connected to it. Again this is at a pretty experimental stage for me.

My weekly review has grown into an elephant sized project, that I end up half-completing time and time again. It's deeply frustrating, and also boring. I don't want to slave every week trying to complete a weekly review. I don't want to block in 3 hours every friday afternoon. What I want to do, is to keep my GTD-system up and running without taking it down for a 3 hours weekly maintenance. I want to do it when I sense the need for maintenance, instead of routine maintenance. I need a PULL system.

Emotional Triggers and Reactions

By analyzing my current weekly review, I have sliced it into smaller separate routines.

These I have then linked to the emotional state of mind that these routines are supposed to prevent. So when I sense I'm entering one of these emotional states it is time do some maintenance.

The Talkbubbles represent the emotional states, and the relevant reaction is described underneath it.

I feel out of control. Days are packed with appointments and the time to do actual work and preparing is scarce

This Triggers: Calendar Review - Checking the past week, the next two weeks in my calendar and my tickler file. This includes converting stuff in the calendar into actions. Blocking in some time to do deep dive knowledge work undisturbed, and figuring out appropriate actions to prepare for scheduled meetings. Reclaim control over my time and Consider appointments that I want to defer to later or cancel.

I scan my Action list and my eyes skip about avoiding many items, that has been on the list for ages

This Triggers: Tidy Actionslists - This is going through my actions list and checking the content. This includes checking the doability of each item. Is it physical and concrete? Is it the NEXT action. Is it possible to do in 20 minutes or less? Do I still feel commited doing it? While ajusting and adding, I tidy up and retype, add new actions and then print a crisp new list ready to churn.

I'm busy but I'm npt making real progress. Days go by emptying mail and milestone tasks stay uncompleted

This Triggers: Project Refocus - This is to ensure I'm doing the right actions. The ones that is really important. This involves looking at my project lists and prioritizing them. This I do in excel by giving them a score from 1-100 and then sorting. I then check each project. Does it have a clear outcome? Is there a next action on the actions list. In the end i tidy up my list and print.

My head is full of stuff. I have the same idea several times but forget to write them down

This Triggers: Mind Dump - This is a thorough 10 minutes brainstorm aimed at emptying stuff from my head on to paper. This is done by mindmapping. I mindmap and brainstorm in the areas: LOVE, WORK, PLAY and GROWTH. After an initial free brainstorming phase, I use my project list as a checklist to trigger new ideas.

I miss projects I feel excited about. I'm stuck in a routine. I need something fresh

This Triggers: Someday Maybe Review - This is looking through my saved creative ideas about things to do, to find something new and exciting to engage in. I find it really wonderful to find an old idea that I suddenly have the energy to commit to.

I lack motivation. I feel I'm getting nowhere. My work/life balance is out of control

This Triggers: Personal Mission Statement Review - This is the big picture. How am I doing from the perspective of my life goals, my 5 year plan, and my 2 year goals. When these issues are reviewed projects are then reprioritized, and new relevant project are added.

Daily Focus and a Tracking Tool

So these are the individual parts that I used cover in a single review. As I'm typing this I really can't understand how I ever completed a single one of these reviews, it's just so much to cover, and so much mental energy to spend.

At the same time researching these emotional states really has giving me a whole new look, at the value of maintaining my GTD-system. Who wants to feel like this?

What I want to do now, is to able to sense when these emotional states are creeping in on me. This is the PULL thing. I have to be able to do the routines only when needed. I don't want to do them to often out of sheer routine. But even more important, I need to do them more often if once a week isn't enough in some periods.

For the next couple of months I am going to track my progress in making this PULL-based GTD maintenance system working.

I have a morning routine involving focusing on the "big rocks" of the day. This is done when my computer is booting, sipping the first cup of coffee. I call it my Daily Focus.

From now on I will include thinking about my emotional state of mind, searching for signs of these emotional states of mind to trigger either a

  • Personal Mission Statement Review 
  • Someday Maybe Review
  • Mind Dump
  • Project Refocus
  • Tidy Actionslists
  • Calendar Review

And then I'll put a little scoreboard in my organizer, to mark with an x, when I have done one these routines. Because I still want to get rewards for making weekly reviews :)

All in all I'm really happy with this new solution to my Weekly Review Blues.

Tomorrows Post: The final LEAN principle - Perfection!

  • Jens Poder

K.E.L.P. By LaertesCTB on Flickr

This is part of a series of articles on using LEAN to streamline your GTD system

So here we are at one of the tough hurdles in every LEAN implementation. The introduction of PULL in the production process, or in this case, into my GTD system. It's at a pretty experimental stage for me, but here's the basic idea.

The reason to do this is actually in the GTD book itself, in the "Mind like Water" concept. The water reacts to a pebble thrown into it with a totally appropriate reaction. It doesn't over react or underreact. Here's the Mind Like Water simile quoted:

In karate there is an image that’s used to define the position of perfect readiness: “mind like water.” Imagine throwing a pebble into a still pond. How does the water respond? The answer is, totally appropriate to the force and mass of the input; then it returns to calm. It doesn’t overreact or underreact. The power in a karate punch comes from speed, not muscle; it comes from a focused “pop” at the end of the whip. That’s why petite people can learn to break board and bricks with their hands: it doesn’t take calluses or brute strength, just the ability to generate a focused thrust with speed. But a tense muscle is a slow one. So the high levels of training in the martial arts teach and demand balance and relaxation as much as anything else. Clearing the mind and being flexible are key. Anything that causes you to overreact or underreact can control you, and often does. Responding inappropriately to your e-mail, your staff, your projects, your unread magazines your thoughts about what you need to do, your children, your boss will lead to less effective results than you’d like. Most people give either more or less attention to things than they deserve, simply because they don’t operate with a “mind like water." Source: http://wiki.jeffsandquist.com/default.aspx/GTD/MindLikeWater.html

Considering this quote, it's interesting, that so much in the GTD system revolves around implementing habits. The habit of weekly review for example. Doing something from habits isn't the same as doing something because it's an appropriate reaction. So my goal is to redefine my weekly review habit, to a set of appropriate reactions instead.

(Please note: I'm not claiming that habits aren't useful. It's only that some habits are harder to learn than others. And I have been struggling with my weekly reviews all my GTD-life. So this is why I'm trying out new techniques. If your weekly review habit is strong and efficient, I congratulate you!)

An Appropriate Reaction

PULL in LEAN is all about appropriate reactions. A traditional industrial system tries to produce a large quantity of something, by forecasting (guessing) the demand, producing it, then putting the stuff on storage, and selling it on demand.

The problem in the traditional approach is that forecasting is pretty damned difficult to do. So 99% of the time you either underestimate or overestimate demand. Overestimating demand is bad because you end op with a lot of stuff you can't sell at your target price, and then you loose money. Underestimating is just as bad, because reaction times in traditional industrial production are so slow, that you'll have difficulties supplying the demand for outsold extra popular versions of your product, thus loosing potential sales and loosing money!

LEAN does it the other way around. It tries to get rid of forecasting alltogether, by making a superfast production chain, that reacts on customer pull. Production methods with fast change-over times and smaller output are favoured over superfast industrial machines, with high change-over times and large output. This makes the production system more ready to respond to demand.

When the production system is ready to respond to demand PULL can be introduced. The principle in PULL is, that nothing is produced before the next link in the system-chain signals, that it needs the part. This can be done in variety of ways. A traditional approach is a visual system (KANBAN-system), that makes everyone aware of the flow in the whole production line.

A PULL system like this make Toyota Dealers i USA able to have smaller inventories of each spare part for repairs, but instead invest in a much wider variety of spare parts. This makes American auto-owners able to get special spare parts for quite old Toyatas overnight, where competitors are struggling to deliver comparable parts within weeks.

The system is in a state of perfect readiness. When there's a demand for something it triggers a chain reaction, that delivers the goods just in time. This is what I wan't my GTD-system to be like!

Weekly Review - From "Batch & Queue" to Pull

I think reviewing your GTD-system once a week is quite allright, if you're able to do it consistently. Unfortunately I'm not. I like the feeling of clarity I get from reviewing, but I think doing it is dull work, and I find it very difficult to use my scheduled review time as buffer time.

What I want is to build a system where I react on telltale signs that I need to do something in my system. When the telltale sign appears it'll trigger an appropriate reaction, and then I'll get back into churn mode.

I know that I have certain emotional reactions to my system getting out of hand. I think that it may be possible to link these emotions to appropriate reactions. Like eating when you're hungry.

This will enable me to break down the Elephant project of completing one weekly review into smaller actionable items, that I do when the need arises.

Take for instance reviewing the actions-list. I know the feeling when my actions-list needs unclutteríng. It is the feeling I get when my eyes are gliding all over the list, seeing plenty of things, but not really wanting to do any of them. This is a telltale sign, that I need to unclutter my action-list. This includes reviewing each item checking to see if they are:

  • Doable
  • A concrete physical action
  • The NEXT action in the given project
  • Less than 20 minutes of work

Then I retype the ones I don't like, and delete the old ones, type in new ones and print. This doesn't take long, and the peace of mind is restored, and it's back to churn mode.

So! My goal is to make a complete system of EmotionPULL-triggers, signs that something needs attention, and appropriate doable actions take when these signs emerge.

So next article: LEAN GTD #5: Triggers and Reactions - A Pull System for GTD Weekly Reviews.

  • Jens Poder

Technorati Tags: , , , ,

This is post 3 in a series of articles on using LEAN to streamline your GTD system.

To map a value stream is quite an experience. Doing it with something as personal as your GTD system is a real eye-opener.

In this case, I started with the benefits that I want to get from my GTD-system, described in yesterdays post.

  • Capture Ideas
  • Efficiency & Control
  • Connecting purpose and tasks
  • Uncluttering

My method was very simple, and not at all as sophisticated as the usual ways of mapping production systems in LEAN. But I figured this was okay for this experiment. I welcome suggestions from experienced LEAN people.

Just grab a bunch of memos and start mapping. Get all the things up there. Your project list. Your capture tools, get them up there. It took me about an hour, and the result was this:

My GTD Flow on a board

The text is in danish, and quite small, but you can check it out on Flickr, where I have added notes, describing the flow in detail. Just click the picture.

In a simplified way, the flow can be viewed like a connected stream that splits up into smaller streams, each representing a unique benefit. The components upstream at the start (like capturing) are beneficial for the whole system, but some of the components (like the tickler file) is closely connected to one stream (in this case the benefit of uncluttering).

This image describes the 4 streams of my GTD System:

gtd-flowboard_overlay-copy

There are four streams of benefit:

  • The stream of capture - utilizing capture tools to get every idea captured for later use.
  • The stream of efficiency - ends in tools that make me able to decide what actions to take... actionlists & calendar.
  • The stream of purpose - on the other side of reviews (weekly, monthly, quarterly). Lets me decide on project-level what to spend my energy on.
  • The stream of uncluttering - Let's me get stuff out of the way, into the dustbin, the reference archive or the tickler file. It frees up energy.

Having this map of my GTD-system made it possible for me to make a couple of immediate changes, where the system wasn't flowing.

A queue in the stream of efficiency

Most obvious was processing. Originally I made the processing of stuff at my computer. This was made in a typical batch & queue proces. I would capture and collect lots of stuff, and then proces once a day. I would type everything into my todo-lists in outlook at the computer and then print a list and put it in my organizer.

The LEAN principles teach us to get rid of these waiting areas in the system. This is because it is wasteful to have inventories of stuff along the way.  It also ads lead-time.

This makes sense as it becomes obvious that the stream of efficiency is running through the area of processing. If processing isn't totally up to speed, then the overview and focus at the end of the stream of efficiency is out of sync with reality. Critical actions will get stuck in the queue, waiting for processing, while you're picking actions from an outdated actions list.

Under normal circumstances, when the normal processing routine is functioning... no problem, but in times of stress, this is bad, because one of the most basic benefits of GTD, namely the overview and being able to pick relevant actions in the moment, gets out of sync with reality.

The Uncluttering and Purpose streams also run through the processing area, but the value of these streams were less connected with speed. But the stream of efficiency needs to flow FAST!

So I began to consider how to break down the first in first out, queue and batch mode of my processing. I decided to use another LEAN principle: The introduction of flow.

Introduction of flow in the stream of efficiency

So I decided to break down the waiting area in the stream of efficiency. And this is how I did it.

Up until now, my primary actionlist had been on the computer, with a paper copy in my levenger circa organizer. This paper copy was handy, when I was on the move.

Now I made the levenger paper copy the primary list. This gave me the benefit of being able to enter things into my action list everywhere.

So from now on, when an idea popped into my head, instead of capturing it onto a notepad or into my memo-recorder on the phone, I instead ask myself: "is it acitionable?" If it is a discrete task, then it goes onto an circa-punched index card, with a relevant context, this goes directly into my actionslist in my paperbased levenger organizer.

So instead of putting somewhere in an inbox, for later processing, I immediately decide if it's actionable, and if it is, it goes straight into the efficiency stream and onto my actionlists.

I still use the computer todolist. It's handy for tasks originating from the computer (mails and such), but it's not a plug in the system any more. I now primarily use the computer to tidy up the handwritten lists. Sometimes it's nice to have a neat fresh actions-list to churn from.

It was a small change, but a significant one. Now I have the benefit of efficiency and overview all the time. And since this stream is one of the key values in my system it was well worth the change.

A couple of other things

Having my GTD value stream on this map also made use my project reference material differently, and store it in another way. And there's a couple of other minor things I have mended as well.

Tomorrow we'll look at introducing another lean principle in the GTD system. The principle of PULL. Never making anything until it's needed.

  • Jens Poder
Technorati Tags: , , , ,

This is part 2 of a series of articles on how to trim your GTD system with LEAN techniques.

First step in any LEAN proces is to define customer value. Only then will you be able to know what is value-adding and what is waste, MUDA.

This might seem trivial, but in fact it isn't. Very few companies manage to make customer value the sole measure on the scoreboard. And a terrifiing number of companies go along without ever getting really close to the need of the people they produce for. This includes a lot of companies that spend heavily on market research. It is a mindset thing.

So what is actually the customer value of a GTD system? I have given that some thought. I am the customer of my own system of course, but what value should the system create? Here is my view on the value that a GTD system should give:

  • Capture of all my creative ideas in a place so I'll get more value from them. This means that I must be able to get every idea into a trusted system, from where I can easily retrieve them, when relevant.
  • A feeling of efficiency by having a clear sense of control and being able to give the right tasks the right amount of attention at any given time.
  • A clear sense of purpose and a connection between higher level goals and daily actions.
  • Uncluttering - handling and getting rid of all unnecessary stuff, freeing up ressources.

That's it basically. When I achieve this, I feel in control. The next step is to map the stream of actions that generate this value. So tomorrow: LEAN GTD 3 - mapping the value stream.

  • Jens Poder

Technorati Tags: , , ,

A LEAN GTD System

7. september, 2007 — 1 Comment

lean-gtd

I have been on the Getting Things Done wagon for well over a year now, and I'm a happy GTD'er. It's a great productivity framework for knowledge workers, because it let's you get stuff off your mind, so you can focus on the job at hand.

But I find myself thinking, that my personal version of the system is overly complicated, especially in stressfull periods. When the going gets tough, my GTD habits gets skipped. Piles start accumulating and the only routinely thing about my weekly review routine, is that it gets cancelled routinely.

This results in frequently having  a "Mind like boiling Water" instead of the wanted state of "Mind like Water".

The problem is this: The journey from the perspective of every piece of information through my system simply takes to long. There's a couple of queue and batch areas along the way, and these require me to sit down at the computer and process. When "sitting down in front of the computer time" is scarce, these queue and batch pools in the system gets totally out of hand. And then you have the pain...

So I have decided to fix this. And I'll use LEAN methologies to do it, and make a LEAN GTD system.

The lean principles

Lean thinkers and GTD'ers have a lot in common. Both parties obsess with system management, the difference is, that Lean Thinking is used in production companies, like car manufacturer Toyota, where it was first invented.

The objective of Lean thinking is to eradicate waste in the production process, or MUDA, as Lean Thinkers call it. MUDA is everything in the production proces that doesn't create value. This could be unnecessary storage and inventory. Unnecessary handling and transport.

Lean production systems are typically build very integrated, with no stopping once the process of building a product is started. Products are produced just in time, so no parts are made before there's a request further downstream Lean systems gets the production flowing with a minimum of waste and waiting. This is how I want my GTD system to be.

So I'll start the process of slimming my GTD system with the 5 basic LEAN steps.

  • Define customer value - what is the value created in the eye of the customer.
  • Map the Value Stream - chart the series of action that create the value. Banish activities that is wasteful right away.
  • Introduce flow - make the proces continously flowing by getting rid of queue and batch thinking.
  • Introduce pull - start acting on pull from the value stream instead of making stuff before it's needed.
  • Perfection - make better all the time.

So that's what's in store for me. Tomorrows post: LEAN GTD - defining customer value.

LINKS:

  • Jens Poder

Technorati Tags: , , ,