That was step one.

Step two is visualizing that FIP. Jessica was concerned because her triathlon regimen included both repetitive and non-repetitive tasks. She needed to consume the right amount of calories, be sure to take her meds, and of course work out. This would equate to three repetitive, monotonous tickets per day in Ready –> Doing –> Done.

Many tickets. Too little real information.

Getting the work done for the triathlon was of course, important, but Personal Kanban is built to be an information radiator. What was the real information she needed?  This turned out to be:

1. what workouts did I do
2. when did I do them
3. did my caloric intake match the workouts
4. did I take my meds and, most important
5. am I being consistent or missing anything?

So here we see Jessica’s board. She just had a little white board, so we worked with the walls in her home. Backlog and Done are both off the board (on the walls where the board hung). Her spontaneous tasks still work through a Ready –> Doing –> Done value stream, those tasks were color coded between work, family, studying and other tasks.  But there’s more here than that.

There are two additional “swim lanes” on this board. A swim lane is another value stream or dedicated horizontal lane on our board for special tasks.

The first swim lane is Triathlon Training. We have several metrics here:

Diet: each day net calories, water, and meds are measured. Calories are a number, meds and water are a checkmark for done.

Workout: Type, severity, and subjective well being are noted here. “20” is a 20 minute cardio. On Wednesday you can see “10 mile ride.” E,M,H are easy, medium and hard workouts. Smilies measure how Jessica subjectively felt about the workout.

She can then take these metrics and not only see adherence and progress, but also plan for future workouts.

The second swim lane is Jessica Studying for her Section 65 Certification. She told me that she studies by creating a study plan for herself, studying, and then testing herself on what she just did. So we set up a swim lane with a WIP of one. At any point, she can only be working on one module.

So with this, we took Jessica’s overwhelming combination of things in progress and goals and made them visible and actionable. Take the time to critically look at the different projects you have in flight. In the end, you want to get the work done, but your real aim is to understand what you’re doing. To get those projects done right, Jessica needed some dedicated swim lanes.

I’m willing to bet she’s not alone.

Last week, Eva Schiffer of Net-Map wrote me and said:

I have just erased my to do list and transformed it in something kanban-like. My own to do list format, that always worked well for me, had 4 categories:

Important and urgent
Important, less urgent
Less important, urgent
Less important, less urgent.

That helps me a lot because I normally love the less important, less urgent tasks, and while they often lead to really interesting creative outcomes, it is important for me to keep procrastination at bay and make sure that I don’t just impress myself with the number of tasks performed, but also do those things that are most urgent and/or important.

This got me thinking about the relationship between productivity and effectiveness. Eva recognized that simply increasing her throughput was not enough, that was mere mindless productivity.

What Eva was searching for was effectiveness.

At Modus, we do dynamic prioritization using a priority filter that looks like this:

For Tonianne and myself, this works wonders. We constantly have a short list of items that need doing, and as they move from 3 to 2 to 1 they become more important. However, prioritization is a contextual exercise that varies from moment to moment. As we can see here, “Eat all the chicken on earth” is Priority 2, but that could suddenly change to Priority 1 if suddenly I were in a place where all the chicken on earth was accessible.

Eva, like many organized people, uses a matrix to ascribe values of urgency and importance, which results in something like this:

Major Tom's Backlog

In the case of Major Tom, he has been sent into space to find out what’s there. He’s a celebrity and everyone is watching him. There are a variety of things he could be doing up there, but he has a a backlog that varies between levels of urgency and importance.

So for example, the papers want to know whose shirts he wears. That’s important both to his individual fame and to the space program in general because after all, it’s being good to the press. But at the moment, he’s in space so he can get to that later.

Major Tom's Workflow

If the press scores an interview while he’s up there, though, it can become relevant and therefore is something to complete.

So we reach Major Tom here in the middle of his work day. He’s already managed to tell his wife he loves her very much, and he’s stepped outside the capsule. He’s put his previously active conversation with ground control on hold because at the moment, he’s working on other things. And he’s now floating in a most peculiar way (and noticing how different the stars look).

Major Tom is still limiting his WIP and he’s still visualizing, even if his backlog is drawn as a matrix rather than columns. The matrix is a familiar organizational tool for him, and it should be preserved. (Although he probably should have checked his instruments.)

So Eva’s concern is very real – we stand a real risk of becoming mindless production units, grinding tasks out at hyper-speed without assessing their value. The key with Personal Kanban is to assess the value of what you are doing – however it is that you define value.

We’re all individuals – quality, value and growth are different for us all.

Not only that but quality, value and growth are also contextual. Today, home repair might be very low on your list. After a tornado, however, it’s probably going to be pretty high. Did you put it there? No. Life did. Context shifted. For that reason, just-in-time dynamic re-prioritization is key for workload management.

So be like Eva. Find the way you define your work – visualize it, and thoughtfully examine how you can best be effective.

Don’t strain your brain, paint a train
You’ll be singing’ in the rain…

- Blondie

Action over Words

Your brain is a muscle. As we repeat certain actions, our “muscle memory” becomes comfortable with those actions, and programs itself to anticipate them. As it trains itself to anticipate them, it optimizes for them. This is the basis of kaizen, continuous improvement. Your brain gets used to your workflow, it becomes an subconscious process, and so it looks for ways to do things better.

Smoother.

Faster.

You get sensitized to completion. Sensitized to waste.

So using Personal Kanban on a regular basis, through its visual and tactile interactions, sensitizes you to the building blocks of success.

Tell me and I forget.
Show me and I remember.
Let me do and I understand.

- Confucius

Simply put: your brain responds very well to doing. The active nature of Personal Kanban is what your brain wants. Confucius figured this out 1700 years ago.

Managing your workload with static lists, while they can help you organize, doesn’t have the same brain-training impact as having a visual tool like Personal Kanban. Lists don’t involve motor skills or elements of flow.

Lists merely “tell you.”

Personal Kanban both shows you, and lets you do.

Image by Rob Web

Small adjustments can make all the difference.

In both Agile and Lean management there are points called “retrospectives,” regular and ritualized moments where a team stops to reflect. Checking processes for only a few minutes lets you re-orient the course of your work. These retrospectives allow a team the opportunity not only to celebrate or bemoan accomplishments or setbacks, but likewise to serve as a constructive way to create and direct their course.  A retrospective shows us that things either went well or they didn’t, understanding that either way, there is always room for plotting the effectiveness of future work.

Over the past few months, I’ve spoken with many people who’ve begun to use personal kanban. During the course of this thread, many of them have shared how they’ve started to deploy Kanban as a collaborative tool, using it to plan, prioritize, and do work both at home and in their place of business. Now we have to go that last step – we have to think about what we’ve done.

Whether it’s on our own, with our families, or with a team, a retrospective is vital in being able to identify, elucidate, and enact positive change. Retrospectives can take place at whatever intervals you are comfortable with, and for whatever period of time. Again, I’m not writing a how-to manual here, these tools should help you or your group manage tasks in a way that works best for you.

We can – and will – discuss a range of options for what a retrospective might look like.  But just like a kanban can reside on a white board, a piece of paper, a computer screen, or even a kitchen appliance, a retrospective is what works at the time.  If you are just finishing a project in the garage or on day 4 of hurricane disaster relief, checking your processes for only a few minutes will let you improve what you’re doing

You don’t have to fly to Pluto to gain from small course corrections. You want to always be fine-tuning your workflow and your work management. In upcoming posts, I’ll talk about a variety of retrospective styles – some that are thought exercises and others with statistical rigor. Whatever you prefer, there should be one for you and your team.

Note: When Kanban is working really well, and you have an intimate understanding of your work, then you will achieve what Lean calls a “kaizen state,”  a culture of continuous improvement. At that point, you are constantly doing retrospectives simply because you are so aware of your actions, and a such, a separate retrospective may not be necessary.

NewHorizons2015 is NASA’s Pluto Mission – which requires both course corrections and a whole lot of delayed gratification.