Analysis -> Creation -> Refinement -> Launch

refinement is dependent on both analysis and creation.

That neatly takes care of dependencies, but in our Personal Kanban we really don’t want to have to come up with new value streams for every little project we are doing. So we need to come up with ways to visualize dependencies that will let us maintain a simple value stream.

So let’s look at a few ways we can do that. As always, these are suggestions and we’d love to see how other people work this out.

Task Notation

We can simply notate tasks with where they lie in a stream of pre-requisites. Noting what comes before can help us not prematurely pull a task, letting us know what comes next can help us raise that next task in priority ones it’s antecedent task is completed.

Scheduled Escalation

Sometimes tasks become relevant on or around a specific date. What we can do is place tasks that need escalation on a certain date on an actual calendar. When that date comes, take the task off the calendar and place it in backlog. If is has a due date, be sure to note that date on the sticky.

Sticky Stacks

Tasks that neatly follow one another can simply stack. When a task is pulled, its next task is seen in the backlog. Sticky stacks can also nicely visualize a project without taking up too much space.

–

So that’s it. Some quick ways to deal with dependencies outside the value stream. Of course, do look in Design Patterns to see if you can find ways to deal more elegantly with specific projects.

You can tame what seems difficult

Your backlog is bigger than it should be and it needs to be managed. Everyday people tell us how they are overwhelmed by their backlog, and cannot possibly manage it within a Personal Kanban because it could contain hundreds or thousands of tasks.

Let’s examine this.

On Stephen Smith’s blog, he describes using Personal Kanban to visualize his workflow with his file-card system. Leslie Dewar left this comment:

I have tried this system of cards in the past and found it extremely distracting and demotivating. I was working with a very intensely personal client base of about 280 people and there were dozens of small jobs that probably really needed to be in a tickler file. If I put them all on a “Task” list, it was quite overwhelming, even though some of the work only needed ten or fifteen minutes.

I also suffer from the “out of sight – out of mind” disability. I have gone through many office an office blitz; prioritised; put in folders; sequenced in desktop folders and ……. forgot about it. By the time I do all that organizing, I somehow felt as though I must have also done the job!

Leslie’s issues are not unique. I’m seeing two in particular here. The first is tracking tasks over time (tasks that aren’t relevant for a while clutter up your Personal Kanban and make it hard to read), and the second is Personal Portfolio Management.

Tracking Tasks Over Time

There are things we do every day that are repeating or scheduled out into the future. We need to remember these things and add them to the Personal Kanban when necessary. Products like Outlook or Google Calendar can help here. Simply place automated reminders (what GTD calls “ticklers”) in your calendar at the earliest date you’ll need to be reminded of them. The due date isn’t going to help you – calls to action will. One of the biggest mistakes people make with calendars is that they record the date something will happen rather than recording the earliest date action will be necessary.

Then forget about that thing until the tickler comes up.

Personal Portfolio Management

I have the feeling this is going to become a major theme for Personal Kanban. Everyone has multiple projects. Those projects have features and those actions have specific tasks. Defined:

• Project – a large thing of value that needs to be done – Build Deck
• Features – units of value that, when combined, create the project – Railings
• Tasks – discrete actions that create features – cut 16 posts to 3’5”

We can use Personal Kanban to manage our work at all three levels. Depending on how many projects we have, a project can simply be denoted by the color of the sticky note. Features can be tracked on the Personal Kanban until we start in on the feature – then we can decide how best to break it down.

If the Project is “Make Breakfast,” that probably stands on its own. You won’t need the features (like Toast) or the Tasks (slice bread, place bread in toaster, depress toaster button, double check toast setting to make sure it’s on golden brown, stare at toaster for what seems like an eternity…).

Part of what makes life challenging is that personal work does come in Projects like “Build House” and “Make Coffee.”  Combined, these projects comprise our Personal Portfolio.

Since one of the goals of Personal Kanban is to simplify your life – creating a huge, mandatory system of nested Personal Kanban or secondary tools doesn’t make sense (for everyone).

So What Do I Do With This Wisdom?

Understand that your body of work is a Portfolio. Your Personal Kanban goal is to manage that portfolio in the way that works best for you. If your Personal Kanban is overloaded with tasks, find ways to group them into Features or Projects until it comes time to actually do the work. If you have too many things in the future, remind yourself with an automated calendar.

If you are like Leslie and have 208 clients, manage them in a Customer Relationship Management system. And, if you get to the point where you can’t manage your work at all – you are taking on too much. That’s the point where you go to Odesk and get an outsourced Personal Assistant.  (And manage them with an on-line Personal Kanban!)

Photo by Sea Turtle

The basic kanban: Waiting, Working, Done

A quick trip through personal kanban design patterns demonstrates how they can be created using any number of materials. This tutorial illustrates how to build the most common personal kanban.

Step One: Establish Your Value Stream

Value Stream (vly strm): The flow of work from the moment you start to when it is finished. The most simple value stream possible is Backlog (work waiting to be done), Doing (work being done), and Done (yes, that’s right, work that’s done).  While you can set this up on a white board or even a piece of paper, a white board is preferable. Why? Because as you grow to better understand your value stream, you will want to change your kanban. You will add steps, or refine how you think about work. A white board provides permanence, yet allows ultimate flexibility: you can always erase and draw something new.

Step Two: Establish Your Backlog

Backlog (bklg, -lôg): The work you haven’t done yet. All that stuff you need to do that you haven’t done – that’s your backlog.  Everything you need to do, start writing it down onto Post-its. Big tasks, small tasks, get them all down. Write them onto post-its and start populating your backlog. Don’t sweep things under the rug. Don’t lie to yourself. Your first backlog-fest should be a painful experience. You should, at some point say, “god, there’s way too much of this.”

Step Three: Establish Your WIP Limit

WIP (hwp, wp): Work in Progress Limit – The amount of work you can handle at one time.  We have a tendency to leave many things half-done. Our brains hate this. Part of what makes kanban work is finding the sweet spot, where we are doing the optimal amount of work at the optimal speed. Set an arbitrary number in the beginning, let’s say no more than 5 things.  Add this number to your Doing column.

"Pull" tasks from one kanban stage to the next

Step Four: Begin to Pull

Pull (pl): To take completed work from one stage of the value stream and pull it into the next. You’re ready to go! That’s right – step four is Begin Working.

Beyond Step Four: Prioritize, Refine, and Reduce

Past step four, it’s all about prioritization of work, refinement of the value stream, and reduction of waste.