Kanban For Lawyers
Kanban For Lawyers
Buy on Leanpub

Chapter 1: Do this Now

Most books begin with a bunch of “why” statements, or a history of the topic, or some other bunch of words designed to convince you that buying the book is or was a good idea. We’re not going to do that.

You’ve started reading—that means you’re at least minimally interested in using Kanban. That’s good, but the best way I can get you really interested in using Kanban is for you to start using Kanban. We’ll get to some history and why stuff later, but starting with Kanban is so darn easy that it simply makes no sense to delay.

The number one thing I hear from people once they start using Kanban to visually manage their work is that they can never see it another way. And they love it.

So if you are ready to commit to improving your productivity, your delivery of client value, and the way you feel about your law practice, I ask you to do the following:

  1. Grab a pad of sticky notes. Any shape or size. (If you honestly don’t have sticky notes, some paper and tape will do.)
  2. Find a pen.
  3. Look around and identify a wall with some empty space.

Great. Now you have all the tools you need to start Kanban.

I’m dead serious about you physically doing this. Kanban is participatory, not conceptual. If you just scanned the above list and thought to yourself “Ok, I’ll go get those things in a bit after I read some more” then stop. Go back. Now please actually do those three things right now. Thank you.

Okay. Now write on a sticky note “Build Kanban Board.”

Look at your wall. Mentally divide it into three vertical columns. Take the sticky note you just wrote and put it in the left-hand column.

Now write each of the following on three more stickies:

  • To Do
  • Doing
  • Done

Put the “To Do” sticky at the top of the left-hand column on your wall, above your “Build Kanban Board” note. If you need to move your existing note around a little to accommodate the new one, please feel free to do so.

Now put the “Doing” sticky to the right of the “To Do” sticky. Then do the same thing with the “Done” sticky, to the right of the “Doing” one. The spacing is up to you—make it feel right.

Then take your “Build Kanban Board” sticky and move it into the “Doing” column.

This next part is very important. Do not skip it!

Step back from your wall and look at it. Take a moment to appreciate that there is one thing right now that you are doing. One. Thing. I’m sure you have lots of thoughts in your head about things that you could be doing, maybe even should be doing. We’ll deal with those things very soon. But right now, at this moment, you are doing one thing: Building your Kanban board.

Great.

Now take your “Build Kanban Board” sticky and move it to the “Done” column.

This next part is also very important. Do not skip it!

Step back from your wall again and look at it, especially that item in the “Done” column. Appreciate that you have just taken something from start to finish. It took very little time, almost no financial investment, and not a lot of effort. But it is done. Finished. Complete. So savor the accomplishment! It is a small accomplishment so a small savoring will do: maybe a deep breath or a quick sip of tea. But savoring accomplishments is essential to your success with Kanban, so make sure you do it.

Nicely done. You have started, and that is the most important thing.

Chapter 2: A Retrospective

Wait a minute—we’re one chapter into this book and already we’re having a retrospective? Seems a little premature, doesn’t it?

Bear with me.

When I said before that completing your “Build Kanban Board” task was a small accomplishment, I was lying. You have actually accomplished a great deal.

First, you have conceived, implemented, and tested a Minimum Viable Product1. That is, you have created a simple thing of value that you can actually use right now to accomplish your work. Oh it is going to get better—a lot better actually—but you’ve built something: A good start.

Equally important, you’ve learned something from the act of building (and from the act of using) your creation. You are now a little bit smarter, a little more experienced. Everything from here forward will be improvement.

Second, you have made your workflow visible. Granted, what you have on your wall right now is a crude approximation of your workflow, but the basic structure is there. We’ll tease out some more detail shortly (maybe a lot of detail eventually). Even this simplistic level of workflow visibility, however, will begin to unlock the incredible power of Kanban.

You have also made your work visible. Well, one task is visible for now. But you saw it! An actual, tangible task that you took from conception to completion through your workflow.

As lawyers, especially modern computer-oriented lawyers, our work is largely invisible. We do lots of things every day, possibly every hour, but we don’t really see most of them. A contract reviewed, a motion drafted, some research done—all of the progress typically lives in our heads, or at most in the ones and zeros of our devices and the ephemeral glow of our displays. We may print off something on occasion, but we quickly send it away to somewhere else. Our work is hard to see.

As humans, this is foreign. We evolved while doing physical, tangible things. If we needed to gather food, we went out into the physical world and plucked edibles until we couldn’t carry any more or it was time to eat. If we needed greater capacity, we wove physical baskets that started with nothing but a pile of reeds and, through a process, finished with something significantly more valuable.

This series of events—identifying a need, inventing some methodology for meeting that need, and then refining the methodology to satisfy the need more effectively—is the baseline for all human progress. It is what distinguishes human progress from evolutionary progress, where a random mutation renders an individual slightly more or less fit to succeed in its particular environment (and, if all goes well, successful mutations are passed along to the next generation).

There’s the thing: Evolution requires generations to progress, but Humans can conceive, build, test, and improve much more quickly. Think about that. Conceive. Build. Test. Improve. Just pondering those steps feels like progress.

My point is that we are much better at interacting with the physical world than the virtual one. If you disagree, then ask why our virtual devices are constantly becoming smaller, more portable—from ENIAC to desktop to laptop to mobile to wearable. I tend to think it is because most people want our devices to accompany us into the world at large where they compliment, not supplant, our physical experience.

Kanban gives all of your invisible, virtual work a visible, physical analog. It isn’t quite the same as doing actual physical work, but it is enough to trick your lizard brain into experiencing the work in a more familiar way. This, in turn, allows your brain to start doing what it does best: recognize patterns, categorize items, perceive threats and dismiss trivialities. Once you can actually see your work in a Kanban board, you will experience a sense of order and control that has no-doubt been missing from your work-life for some time.

The third thing you have accomplished (or the fourth, it isn’t important) is that you’ve experienced the power of working on one thing at a time, and of working on it until it is done. In manufacturing this is called Single Piece Flow. There is decades of evidence showing that Single Piece Flow—as opposed to the alternatives: multitasking and batch flow—is the best way to get lots of things done in a fixed amount of time. There is other, more recent, evidence that we humans are pretty lousy multitaskers (texting and driving is a familiar example), and don’t get me started on batch flow—a false idol of misperceived efficiency if there ever was one. But we’ll dive into the concept of Flow very soon.

Finally (for now), you are about to complete a Retrospective. This should become as familiar a part of your personal cadence as brushing your teeth. This first Retrospective isn’t actually a great example—I’ve been a little long-winded and we haven’t followed much of a structure. But we can fix that now.

As you develop a habit of retrospection2, I find it helpful to ask the following three questions:

  1. What went well that I should keep doing?
  2. What didn’t go well that I should stop doing?
  3. What should I try next time that is different?

This chapter so far has focused on the first question. Although you may not fully understand all of the whys yet, many things went well when you used Kanban for the first time. We won’t always go into such detail, but acknowledging and appreciating success helps to reinforce it. Early success, no matter how small, establishes a foundation for progress.

As for the second question, I’ll leave that mostly up to you. Perhaps you didn’t choose the best section of wall, or your writing was hard to read, or you ran out of room on your stickys, or who knows what else. For me, I’ll admit again that this first retrospective is taking too long.

This isn’t the time to beat yourself up. The shortcomings aren’t nearly as important as the successes, for they can always can be fixed. This also isn’t the time to do the fixing; it is a time for thinking. More diagnosis, less prescription.

Spending time just thinking may be harder than you suspect since our culture predisposes us to want to take action. To everything there is a season, however, and the season for reflection is every bit as important to your cycle as the season for doing.

The third question also requires some discipline, especially in the early stages of Kanban. Already your mind may be racing through different ideas about how you can improve your board, define your tasks, or maybe get other members of your team up there. These are great, and we’ll want to consider them all, but not immediately. For each idea you have, write it on a sticky note and put it on the wall to the left of your To Do column.

Wait… To the left of “To Do?” That sounds like we need to add a column to our Kanban board. Let’s start there.

  1. The Minimum Viable Product concept comes from Eric Reis’s excellent book The Lean Startup. It is an essential guide to entrepreneurship and product development that any technology client of yours has almost certainly read. If you have technology clients, you should get familiar with it so that you can better connect with those clients. But even if you don’t, its concepts will absolutely help you improve your own practice and better understand your value proposition to your customers.
  2. Weekly is great, every other week is totally fine for personal work or smaller teams. If you stretch it to monthly you’ll probably find that you have too much to handle in a single Retrospective. As you start with Kanban (and Agile methodologies in general) I’d say more frequent retrospectives are better. Once you get the hang of it, you may or may not want to stretch them out over time.

Chapter 2.5: A Word about Software

By this point you’ve probably started thinking “I bet there is some great software tool I could use to automate this!” Your Google or App Store search history may already contain some version of the term “kanban app.”

This is natural, I get it. It is a good thought actually. And yes, there are some great programs out there for building and maintaining Kanban systems.

But you’re not ready.

Soon we will be able to consider software, but first you need to know why making an investment in researching, buying, implementing, and maintaining a software tool is the best possible use of your resources right now. And right now, it is not.

You just built your first Kanban board with an incredibly low investment. Now this board hasn’t helped you deliver greater value to your customers (yet), and it hasn’t enabled you to capture some of that value in the form of revenue (yet), but it has given you something that is even more important to your long-term success: knowledge.

This Minimum Viable Product you’ve created, along with the retrospective you just conducted, has taught you something. And it promises to teach you much, much more without a whole lot of additional investment. But if you go off and install an app, your relative investment in this thing will skyrocket. You’ll have to pay some money, spend some time learning the tool, and you’ll risk being sucked down the rabbit hole of endless configuration and modification.

I’m glad you’re excited and I understand your desire to get this Kanban thing up and running as quickly as possible. But moving quickly isn’t the point: The point is learning. Learning how to see your workflow. Learning about your tasks and your products (yes, you have products) and how to describe your work. Learning how to recognize value and how to avoid waste. These things will come, and they will come more quickly than you expect. But software will force you into some programmer’s view of how you should work, and that will inhibit your learning. At best it will delay your progress, and at worst it will stall your efforts completely. And then all your investment will have been for naught.

There is something irreplaceable about learning in a physical environment. A big part of what we’re trying to do is get you to truly see your workflow in the broadest sense, and I doubt you have a screen that can rival your wall for size and scope and taking it all in. Even if you do (and someday we probably will), there is something tactile and kinesthetic about bodily interacting with the stickies and columns on your board. Once you learn to see, and feel, and experience, your workflow in a physical way, then you will be in a position to translate that experience to a virtual tool.

You may even decide to start using software at that point, but you may not. I know of people and teams who have been using Kanban for years without making that choice. If and when you do come to that decision, however, I want it to be from a position of strength. Strength comes from confidence, and confidence comes from knowledge and experience.

Building strength, however, requires training, and effective training must follow a plan. Right now your training plan involves channeling your inner Rocky Balboa to move physical objects through the world, not some mechanistic Ivan Drago interacting with newfangled machines. It may seem rustic, maybe a little quaint, but I guarantee you there is no better way to train.

So please, set aside your software aspirations for now, and let’s get stronger.

Chapter 3: Fleshing out your board.

Okay, now we’re ready to make some real progress. First thing: On a sticky write “Expand Kanban Board v1” and put it in your “To-do” column. Now move it to your “Doing” column. See? Progress again. (Yes it is hokey, but it’s still progress!)

The “v1” is, of course, shorthand for “version 1,” which implies that we’re not going to get this thing completely right the first time. That’s okay. In fact its not only okay, it is necessary for iterative improvement. We won’t necessarily be tracking each version of our activities like they were software releases, but for now we’ll use the “v1” to remind you that you don’t have to nail something on the first try. You just have to try to make it better.

Now we’re gonna need some more wall space. Perhaps the spot you picked will do, but we’re about to at least double the number of columns on your board so you may need to create some room. Maybe use your whiteboard if you have one, or take your diploma off your wall (for now), or even use your window.

Good. Now grab your pad of sticky notes and make three new headings: “Backlog,” “Queue,” and “Waiting.” We’ll talk about what they’re for in a bit. If you’ve got different sized sticky notes, then these headings might be a good use for the larger ones (4” x 6” works well, but the size isn’t critical).

Rearrange the columns (and their contents) so that they are in the following order from left to right:

1 Backlog | Queue | To Do | Doing | Waiting | Done

Under these headings you will have a few tasks. “Build Kanban Board” should still be in the Done column. “Expand Kanban Board v1” should be in the Doing column. If you wrote down some ideas for improving things at the end of our Retrospective, then you can place those stickies in the Backlog column.

Why don’t they go in the To Do column? Good question, and the answer will help us understand the reason for each of the columns on the board. But first let’s talk about the concept of Flow. We touched on it in the Retrospective when we mentioned “Single Piece Flow,” but that does Flow really mean?

In a river, the Flow is obvious1. The water will run downhill, and it will find the path of least resistance to the river’s Goal: The ocean or lake where it accumulates. But the path of least resistance isn’t always the most direct path.

At a large scale there will be hills or mountains in the way. These force the river to bend, sometimes back on itself in an oxbow, in order to ultimately reach its Goal. Even the smoothest flowing river will have a few hills to contend with.

On a smaller scale, there will be boulders or logs or stumps that interrupt the Flow. These create turbulence that slows the river’s progress and sometimes even creates an eddy—a place where the river swirls backwards a bit instead of progressing toward the Goal. Get enough of them together and the water will begin to pool upstream, growing deeper and building up pressure until it can overcome the obstacle and must then rush ahead to try to make up for the interruption.

On a smaller scale still, there are disruptions under the surface of the water that interrupt Flow: smaller rocks, tree branches, maybe that old boot from the cartoons. These too create turbulence, though at a certain rate of Flow the water will run right over them and the turbulence will be hard to see.

Factory Flow works much the same way. In a typical factory, the raw materials enter at one end of the building and Flow through a Work Stream consisting of People, Processes, Policies, and Tools until a finished product emerges at the shipping docks at the other end. As with a river, this Flow can be interrupted by many things large and small, but the Goal is to get finished product out the door in response to customer demand.

And as with a river, factory Flow must deal with resistance. If a Person or Tool isn’t available to do work, or a Process or Policy causes delay, then the Flow will stall and the unfinished work will begin to pool in front of the interruption. The manufacturing world refers to these interruptions as Constraints, or sometimes Bottlenecks, and plant managers are constantly working to create smoother Flow by addressing them.

Your Work Stream is no different, it is only harder to see. Your Goal, however, is to create finished products by moving Work through your system of People, Processes, Policies, and Tools until some product or service that delivers Customer Value emerges at the end.

Now look again at your wall. By now you have probably figured out that your Kanban board represents your Work Stream. This is how we make your work more visible, and also how we will see when and where your Flow is getting interrupted. It is still pretty basic, and we will continue to tease out more detail, but it should be plain to see that your Goal is to get tasks (as represented by sticky notes) to progress smoothly from left to right until they are Done.

Make sense? Good (although if it doesn’t, please don’t hesitate to contact me and I can try to help you figure it out). Now let’s start filling up your board. We still need to talk in more detail about what each column is for, but that conversation will be easier if we have some actual tasks to work with.

One quick note on design: You may feel like making your board a little more formal at this point, and I’m all for that. You need to live with this thing and it should reflect your aesthetic. The simplest and most common thing to do is to add some lines between the columns to make them a little clearer. If you’re working with a wall or window, some painter’s tape (I’m partial to blue) is a good tool for this. If you’re using a whiteboard you can just draw them for now. And if you don’t have either don’t sweat it; the lines are decorative, not required.

Don’t do anything too permanent yet—you will almost certainly want to make changes. Also, be sure to leave yourself some extra room for the Backlog column—you’ll soon see that it has a tendency to get pretty full.

Great. Now take your “Expand Kanban Board v1” sticky and move it to the Done column. Once again, savor this moment. You’ve accomplished another thing, hopefully learned a little more, and you’ve strengthened your foundation for making even greater improvements. Nice work.

Now grab another blank sticky and write on it “Brain Dump v1,” then stick it in your To-Do column. It probably should have started in the Backlog, but for the last time I’m going to impose my order of events on you. Henceforth I’m going to take a step back into a guide’s role and let you call the shots.

  1. The analogy of factory flow to a river’s flow originates with Taichii Ohno, regarded by many as the father of Lean manufacturing.

Chapter 3.5: Take a Break

And now go take a break. Seriously, do it. Okay, I’m not imposing it on you, but as your guide I strongly suggest it. At least 10 minutes, maybe 15 or 20.

Ideally go do something that will replenish you rather than deplete you. I understand that you have work you need to do. You will always have work you need to do. But you’ve been using your brain and its energy stores for a while now and you’ll perform better if you do something first to fill them back up.

Go take a walk outside, or have a (non-work) conversation with somebody, or go look at some art, or read fiction, or poetry, or listen to music, or exercise, or meditate. Walk away from your computer and leave your mobile thingie in your pocket. Or leave it behind—the world will last a few minutes without your attention. Don’t go check your email, or your social media feed, or move right back into some work-related task. Your brain needs breaks, so give it one.

I’ll keep this tangent brief, but if you’ve somehow missed all of the scientific evidence that shows why breaks actually make you more productive, then go search the web for the phrase “take frequent breaks” or check out the NY Times story at http://nyti.ms/LcUmnU. But after you do, be sure to take a break.

Chapter 4: Brain Dump Part 1, The Done Column.

Welcome back. I hope you are feeling refreshed, now let’s get back to work.

Take that “Brain Dump v1” sticky and move it to the Doing column.

We’re getting to the fun part. Make sure you have a good pen (I like Sharpies) and a good supply of stickies. If you have a few different colored ones, this would be a good time to get them (no problem if you don’t).

If you are using color, pick one to use for your client work. Now write the words “Client Work” on a note of that color and stick it on the wall above your board so you have a visual key to remind you which color means what. Now pick another color and do the same for “Back Office,” and maybe another one for “Personal.” Keep the number of categories small for now; it is easier to add granularity later than it is to combine categories. And really one category is just fine if you just want to get going.

If you’re not using colored stickies but you do want to use categories, then you can accomplish the same thing by putting a mark of some kind in the top-left corner of the sticky. Maybe it is a slash with a colored pen (your whiteboard markers will work), or maybe it is the letter “C” for Client, “B” for Back Office, etc. Whatever you choose, just make sure you make a key. As you will soon see, there is no sense in holding your methodology in your head (and there is a lot of sense in putting it on your wall).

One more thing before we start. Take one sticky, ideally a square one, and turn it 45 degrees so you have a diamond. Draw a big dollar sign on it (or pound sign, or euros—whatever currency motivates you) and place it on your board, right above the line (or imaginary line) that precedes the Done column. This is your payoff line. Your Goal is to move work across that line.

Your board will now look something like this:

1 **Kanban board image goes here

You’ve already got a couple of items in the Done column, but let’s fill it out a little more. Think back over the last few days, no more than a week, and make a sticky for each task that you actually finished recently. It can be for something that was a one-time thing, maybe finishing some client document, or it can be for something that recurs periodically like writing a blog post or sending bills.

If the task you completed was client work, then be sure to grab the right colored sticky (or make the proper mark). Also, if it is work you or your firm got paid for, then write the amount the task was worth on the bottom-left corner of the note.

Also, if you remember it, write the date you first started working on the task in the upper-right corner of the sticky, and write the date you completed it in the bottom-right corner. If you don’t remember, again no problem. We’ll start building this out as we move more tasks through your board.

So your sticky note should look something like this:

1 **Sticky note image goes here

Try to leave a margin down the right-hand side of your sticky when writing your task description—we’ll use it shortly. And keep your task descriptions short; you want to be able to read them from a distance and capturing a lot of detail isn’t important right now.

As an aside, I will say that if you have the room on your wall, getting some larger sticky notes may be a good idea—I like the 4”x4” ones—though the standard 3”x3” ones really are just fine. Ultimately you may want a variety of sizes to signify different things (we may even be adding stickys to stickys). No need to run out to the office store just yet, but maybe make yourself a note that says “Buy multi-sized stickys” and stick it in the Backlog.

Great. Now spend some time filling out those Done stickys. We won’t spend a ton of time reviewing these, but they’re a good chance for you to develop a format that works for you. If you didn’t take a moment to savor the accomplishment of a completed task when you actually completed it, you can catch up on that savoring now.

Just make sure the items that go in the Done column are truly and completely finished. If you start to write out a sticky and realize you still have some work left on that task, go ahead and finish the note but set it aside. We’ll find a home for it soon.

Okay. Once you’ve finished writing out your recently completed tasks and putting them in the Done column (making sure to acknowledge your accomplishments), its time to move upstream to Waiting.

Chapter 5: Brain Dump Part 2; The Waiting Column.

The Waiting column is a special place on your board: it is the one column you hope to be able to skip completely whenever possible. The purpose of the Waiting column is to act as a parking lot for tasks that you have started working on, but somehow they got stuck.

If you’re like most people, dealing with little sticking points is probably a big part of your day. We live in an “interconnected” world with lots of “dependencies.” That means we will necessarily spend a good deal of time waiting on other people or processes to do their thing.

Waiting is not always a bad thing. In fact, there is a very good kind of waiting: you wait while someone—maybe a client or a colleague—finishes their piece of work and delivers to you all of the necessary materials you need to finish yours. We often don’t do enough of this type of waiting; we get impatient and want to start working on our piece. But when we jump the gun on our work we frequently have to go back and change things once we get new information, or we hit a roadblock where we can’t actually finish a task until some additional information is available. At that point we have to stop what we’re doing, store away the Work in Progress on that task, and switch gears to go work on something else.

That lack of good waiting will almost always lead to a more insidious type of waiting that will divert your time and attention and increase the drag on your entire system. We’ll call it wasteful waiting after the Lean concept of Waste1, and it often results from starting a task before it is Ready for your work. Again, if you’re like most people, you probably don’t give much thought to the notion of the task being Ready for you to work on it. Instead you probably focus on whether you feel ready to work on that task.

They are sides of the same coin, but don’t confuse one for the other—they are both necessary conditions for you to be able to work that task to completion. You’ll usually have a good sense of whether or not you’re feeling ready to work on something, but how do you know whether or not the task is Ready for your work? In a few chapters we’re going to talk in detail about the Definition of Ready and its close sibling, the Definition of Done, but it is worth a quick overview now.

In a nutshell, the Definition of Ready is a checklist containing all of the conditions precedent to your being able to complete work on a particular task or stage of a process. All of them. The checklist may contain information, raw materials, tools, a block of time, or completion of a prior task or process phase. For tasks or processes you complete on a regular basis you’ll eventually develop a pretty complete Definition of Ready checklist for each checkpoint along the way. You’ll always be learning and making improvements, but you’ll develop a reliable guide that will tell you whether or not a particular task is Ready for you to begin working on it.

For less common tasks your Definition of Ready may never be totally accurate. But as you train yourself to think in terms of a Definition of Ready you will undoubtedly make improvements on these less frequent tasks as well.

The reason for having a Definition of Ready comes back to the advantages of Single Piece Flow. As I said before the most efficient and effective way to complete a task is to begin it and work it all the way to completion without interruption. Period. Starting and stopping work on a particular task, or frequently turning your attention from one task to another, has switching costs: Your brain takes time and energy to shut down work on Task #1 and change its focus to Task #2, and the amount of time and energy available to your brain are finite. The more you switch, the more mental resources you waste.

On top of that, the unfinished work on Task #1, the Work In Progress, has a carrying cost. Your brain, and your other systems, must hang on to enough detail about that task to be able to pick it up at another time and continue work. Here too, your ability to do this is limited. You may have a great short-term memory, but it is not infinite. It takes energy to recall specific details and your brain only has so much energy it can use in a single day.

All of this waiting—both the good and bad kinds—lead to tasks that get stuck in your system. And I’ll bet that stuck tasks are the single biggest source of turbulence in your workflow. The purpose of the Waiting column on your board is to give you the tools and information you need to get those tasks unstuck and restore your system’s flow.

With that background, go to your board and take the “Waiting” column header off the wall. On that sticky (or on a new one if you don’t have room) I’d like you to write the following: “On what?” and “Since when?” These are the crucial pieces of information you need to break those tasks free.

We’re going to focus just on the Bad Waiting tasks at first. Remember, these are tasks that you started working on but had to stop due to some unforeseen dependency. In other words, you hit a roadblock. Often your roadblocks will be external, e.g. waiting on some other person to get you the information you need to continue, but roadblocks can be internal as well. Maybe you need to do more research or get the right tool for the job. For now, don’t worry about tasks you haven’t started yet because you are waiting for them to be Ready for Work; we’ll deal with those in a bit.

So grab your blank sticky notes and start writing down tasks you’ve started working on but aren’t able to finish without some additional tools or information. Remember your categories if you’re using them (whether with color or by notation), and, if you know them, write the task’s start date in the top-right corner and the rough value of the task in the lower left (don’t spend a lot of time on these if aren’t top of mind).

At this point the stickies should look a lot like the ones in your Done column. The next step is to note what you are waiting on, and when you started waiting. For now, you can use the space down the right-hand side of the sticky, below the task’s start date. Or, if your stickys start to look crowded, you may want to consider using a separate sticky note (maybe a slightly smaller one) to capture this information and hang it as a flag off of the task note.

Notice that I said “on what” instead of “on who.” If you think the who is important, then by all means write it down too. But the actual dependency is the action item, not the actor. Notice also that I suggest noting the date you started waiting rather than imposing a due date. This is a more subtle distinction, but it is my experience that an elapsed time works better in most situations. I won’t go to the mat on this one, however, so if you think a due date will work better for you then by all means go with that.

Repeat the process for everything you can think of where you are waiting on something before you can finish a task. Place the stickies in the Waiting column in rough order of importance, with more important tasks going toward the top and less important ones below. What’s important? That’s up to you. A roadblocked task may be important because it stands to make you a lot of money, or it may be important because there is a looming deadline. You don’t need to nail it exactly, just give your tasks some relative priority. You can always move things around later.

Once you’ve written down as many of your “Waiting” tasks as you can think of, take a step back and look at your board again. In the past when we’ve done this it has been to inspire a feeling of satisfaction for having completed a task. This time I want to inspire a sense of urgency.

Look at that thin line between “Waiting” and “Done.” Now look at the dollar sign (or whatever currency you chose) that is above that line. This is your payoff line. Your main goal, really your only goal, is to move tasks across this line. When you do that—when you work a task to completion—several good things happen.

First, you get to savor the accomplishment of finishing a task. We’ve been practicing that, and the reason we’ve been practicing is that it is a great motivator. Success breeds confidence, and confidence breeds more success. So think of how good it will feel to get some of those tasks out of the Waiting column and across the line to Done.

Second, you may very well get paid. Not all of your tasks will have immediate payoff, but for client work in particular, finishing your task means you can deliver something of Value to your customer and ideally get paid for it. This is probably the reason you are in business, or at least one of the most important reasons. Sure if you work in a large firm or as an in-house attorney the payment may not be directly to you, but delivering Value is still the main reason for your job to exist and you will take satisfaction in doing that job well.

Finally, and you may not see the benefit of this yet, but by completing tasks you free up some capacity in your system to handle more work. One of our goals here is to increase the Velocity of your work. That is, the speed at which you complete a task once you start working on it. At first Velocity may sound synonymous with efficiency, but they aren’t quite the same thing.

Efficiency is your ability to complete a task without wasted effort, whereas Velocity is your ability to complete a task quickly. Greater efficiency will almost certainly lead to increased Velocity, but it isn’t the only thing keeping you from greater speed. As I keep saying, the amount of Work In Progress you have in your system has a carrying cost, and one of those costs is a tendency to create turbulence for the system as a whole. The more work you are keeping track of—even if you are performing the tasks themselves fairly efficiently—the longer it will take for each task to flow into the Done column.

One of the catch phrases you will sometimes hear about Kanban is “Start less, finish more.” The idea is to carry less Work In Progress in your system as a way to reduce the carrying costs of that work. Lower carrying costs will lead to the remaining tasks flowing through your system at a greater Velocity. And with a greater Velocity, the more tasks you will complete in a given time period and, usually, the more money you will make. This is not necessarily true of efficiency.

Again, this may be hard to see at this point in your Kanban journey. As you keep using your board, learning from that use, and adjusting your methods, however, you’ll see that keeping track of fewer tasks at a time will help you complete those tasks more quickly. Consequently, you will get more tasks done.

So look again at your Waiting column. What does it tell you? Who do you need to call (which is better than email), and what do you need to ask for in order to stop waiting and get that task back to Doing, or even over to Done? Great. Make it so.

  1. In Lean parlance, Waste is any activity that doesn’t add Value to your product or service (Value being measured from the perspective of your Customer). “Waiting” is traditionally one of the Seven Wastes of Lean (some people count eight), but as I said above there is good waiting and bad waiting. Failure to engage in good waiting (i.e. waiting until a task is truly Ready for your work) will inevitably lead to some of the other Wastes, namely Pre-work and Re-work. Bad waiting comes when the task is Ready, but you, for some reason, are not.

Chapter 6: The Doing Column.

Phew. We just introduced a lot of new concepts in our discussion of the waiting column. If you’re playing along at home—and again, I truly hope that you are—now might be a good time for another one of those replenishing breaks.

If you feel like you need to check your email or voicemail, or tackle some other bit of work that is tugging at your conscience, I understand. Please remember, however, that doing different work is not a break. Before you move on to some other thing, I recommend you take a real break first to digest this new information and let your brain rebound a bit. If you do, you’ll be much better equipped to carry on with your day.

Ready? Great.

The Doing column is where you’ll put the work that you are actually and actively doing right now. This is not your “I should be doing something” wish list and it is not your “I promised someone I would do this” list. It is where you have committed to doing a task, have started working on it, and intend to see it done.

Right now there should be one item in that Doing column: “Expand Kanban Board v1.” We’ve been working on completing that item since Chapter 3, and we’ve still got some work left to do.

Whether you’ve actually been working on just that one thing this whole time is another matter. If I had to guess, I’d say you haven’t. Heck, I even gave you permission to go do other work a few paragraphs ago. This is normal, and natural, but that doesn’t mean it is optimal.

So the first step in setting up your Doing column is to go ahead and fill it up with all of the things you are actively working on. You may come up with your own criteria for what “doing” means to you, but I’ll suggest the following: A task goes in the Doing column if the following conditions are met:

  1. You have started work on it.
  2. You are capable of finishing all of the required work without any outside help, materials, or information.
  3. You intend to finish it.

In other words, you are “doing” a task if you have begun working on it and, given enough time, will finish it on your own without another person or thing.

Take a few minutes now to write down the tasks that fit your definition of “Doing,” one per sticky, and put them on your board (keeping with the format you developed in the Waiting chapter). While you do this, you may realize you have a few more items where you are actually waiting on some outside resource before you can continue work; you probably guessed that these should go over in the Waiting column. You might also come up with things you need or want to do but haven’t started yet. Write those down too, but put them two steps to the left in the “Queue” column (we are going to have a separate set of rules for the “To Do” column, so leave it empty for now).

A lot of people start to freak out a little once they fill up their Doing column. Many folks are astonished at the number of things they are trying to accomplish at once that they’ve been holding in their heads. Even those who already use checklists or other productivity tools are often surprised at how it feels to see physical representations of their tasks right there in the room with them rather than tucked away in a notebook or on a screen. This minor freak-out is normal, and it is a feeling we’re going to try to harness as a weak version of revulsion therapy.

Finished? Okay.

I won’t pretend to be able to guess how many tasks you just put in your Doing column, but I’ll bet you’re not very close to that Single Piece Flow I keep talking about. If you are, you probably don’t need this book. As I keep saying, working one thing at a time, and working on it until it is finished, is the best way to get lots of things done1; however, it is something of a Platonic ideal. We should all aspire to it, and we might approach or even achieve it with practice, focus, and retrospection. But I’m certainly not there yet, and you probably won’t be anytime soon.

The question, then, is how can we erect a support system to help us move towards this ideal of “one thing at a time,” or at the very least reduce our susceptibility to doing too many things at once.

This gets to one of the great benefits of Kanban (and many productivity methods that precede it): its ability to provide a framework to help us combat some of our perfectly normal (but ultimately harmful) tendencies in our quest for improved Flow.

You’ve already been experiencing the visual representation of otherwise invisible work, which I think Kanban’s most effective tool. But this next one runs a close second: We are going to establish a constraint on the number of items each stage of your workflow can process at a time. Specifically, we are going to limit the number of items you are allowed to put into your “Doing” column at once.

Wait a minute—we are going to create a constraint? I thought the whole point of this exercise was to remove constraints, not introduce new ones.

First off, this will be an artificial constraint—it is a construct, not a commandment, and you are free to break it so long as you do so intentionally. That way we won’t be introducing any actual bottlenecks. In fact, this false constraint will have the opposite effect of reducing the pressure on your actual bottlenecks, thereby improving the Flow of your work through them.

What we are about to do, then, is establish your first WIP Limit. WIP is a manufacturing acronym that stands for Work In Progress, and we’ve touched on this concept already. In the Lean world (originally a manufacturing one), WIP is a form of inventory and is seen as a necessary evil: You have a process, and raw materials must flow through that process in order to become valuable products to your customer. But while it is in-progress, that unfinished work (a/k/a WIP) represents investment without realized benefit, and investment without benefit is waste.

Think of a simple manufacturing line, let’s say for bicycles. As soon as the raw metal tubing for a bike frame gets delivered to the bike-making plant, it represents WIP. Someone has to take delivery of the goods, pay for them, and spend some time and effort deciding where they go next. Each of these activities requires some investment in time, money, and/or energy without realized benefit. The raw metal then gets cut (investment), welded (more investment), sanded (you get the idea), painted, tricked out with various components, and ultimately shipped off to a customer. Each stage adds value to the raw metal tubing, but it isn’t until all the stages are complete that anyone will pay full value for the bike.

All along the way you have WIP—investment after investment without realized benefit. True, there is the promise of future benefit; like I said, WIP is a necessary evil and it cannot be wholly eliminated. But the key to an effective manufacturing line is to reduce, as much as possible, the amount of time, money, and effort it takes to work your raw materials into something valuable. Only after all of the value-adding steps are complete can you sell that valuable product or service to your customer.

Let me reiterate that ultimate goal: to deliver valuable products (or services) to the customer. Does the person who buys a bike care how beautifully welded the frame is when that frame is sitting in a factory waiting to be painted? Of course not. She only cares about the welds, and the paint, and everything else when she is whizzing down the street atop the finished product. The steps it took to make the bike are only valuable to her as part of the whole package.

Put another way, a reasonable customer will not pay you until you have delivered something of value. We lawyers sometimes pervert this simple law of economics by assuming that our time is what is valuable to our customers. It is not, and surely you know it is not.2 What is valuable to our customers is outcomes, and customers will pay for outcomes (or, if you’ve set expectations well, for clear milestones along the way to an outcome).3

WIP limits help you deliver Value to your customer more quickly by ~~forcing~~ encouraging you to finish (and ideally deliver) one thing before starting another. It is the antidote to having “too many balls in the air,” because a WIP limit prevents you from launching a new ball until one has landed. Some Kanban practitioners have reduced this concept to a catchphrase: “Start less, finish more.”

Enough background. If we are going to establish a WIP Limit to your “Doing” column, what should that limit be? This is a somewhat personal choice. I’ve mentioned the Platonic ideal of doing just one thing at a time, but most people find a WIP limit of 1 to be unworkable, especially at first (though if you think you can do it, by all means give it a try!). Other numbers have their own strengths and weaknesses, but the trick is to find one that works for you.

I’ll offer two possible suggestions. If you just want to pick a number and go with it, I usually say to shoot for somewhere between 3 and 5. That seems to be a range that most people can achieve and sustain with a little practice. If you have fewer than 10 items in your column, I’d suggest going for this range. But if you’re used to having lots and lots of balls in the air, even getting down to five may be too aggressive at first.

My second suggestion, then, is to simply count up the number of items in your “Doing” column and reduce it by 25%. If you put 12 items in there, your first WIP limit will be 9, if you’ve stacked it up with 20 items, try to whittle it down to 16 and see how that feels. But the whittling should be iterative. Once you’ve made it from 20 to 16 (meaning you’ve finished four items without letting new things come in), then you should try to get it down to 12, then 8, and then that 3-5 range. It may take a few weeks to get there, but that is OK.

Whatever number you choose, go ahead and take your “Doing” sticky (the column header) off the wall and write your WIP limit in parentheses after the word “Doing” (or make a new sticky if you didn’t leave room). Now, if you’re really motivated, see if you can complete a few tasks to get the number of stickies in your Doing column down to your WIP limit. But don’t worry if this seems like too heavy a lift right now—you’ll be just fine if it takes you a day or three to get down to the limit.

One final thought before we leave the Doing column for now: think about using vertical positioning of your stickies within each column as an indicator of priority. In other words, put your highest priority items at the top of the column and your lower priority ones beneath. And try to make it a single vertical column—you ought to be able to give each task a priority relative to the others (and if you can’t then the order of similar priority tasks probably isn’t important). This isn’t to say you absolutely positively have to work on your highest priority tasks first, but if you are going to work on a lower priority one (say because it better fits the time you have available), I want to you do it intentionally. We’ll use this vertical ranking concept for all of the columns on your board.

Now when that “Expand Kanban Board v1” sticky makes it to the top of your “Doing” column, you’ll be ready to move another step over to “To-do.”

  1. If you still don’t believe me, try this exercise. Your job is to accomplish three tasks: writing 1 to 10 in Arabic numerals, writing 1 to 10 in Roman numerals, and writing the first 10 letters of the alphabet. Grab a piece of paper and divide it into three columns, one for each task. You also need a timer (your smartphone probably has one). You’re going to do this at least twice. In round one, you must complete all the “ones” before you move on to the “twos.” So your sequence will go “1,” “I,” “A;” “2,” “II,” “B,” and so on. Start the timer when you’re ready and go to it. When you’re done, note your time and flip the paper over to make three columns again. Now repeat the exercise, but this time you must finish one column before you move on to the next, so you’ll write 1-10 in Arabic numbers, then in Roman, then in letters. Compare your times and call me a liar if you weren’t faster the second time (you can tweet it to me at @jegrant3). And if you think your speed on round 2 is because you got better at Roman numerals, go back and do round one again to double check.
  2. This is not necessarily an indictment of hourly billing. While many people criticize hourly billing as it is currently practiced in service industries, I believe that Kanban and other Agile project management methods can support a relationship where hourly billing is defensible and even preferable to provider and client alike. That said, hourly billing as practiced by lawyers with inefficient and opaque processes is rightfully suspect.
  3. One advantage that service providers (like lawyers) have is that we don’t need to wait until everything is done to start delivering incremental value to our customers. We can deliver knowledge and insight and outputs (letters, filings, etc) that will help the client advance her understanding of status on a particular matter, and we can and should expect the client to compensate us for that incremental value. But that still doesn’t mean that our costs for delivering the value (our time) is the best proxy for that value in our customer’s eyes. The customer’s perception of value will naturally flow from her understanding of the benefits of the work, not her lawyer’s calculation of its costs.