" "

Primers

Slack: Why Limit WIP Series, Post 3

Bob_slack02

Slack.The word conjures up images of slothfulness, of days spent lazying about in a seaside hammock beneath the fronds of a blowing palm tree.But relaxation is not necessarily sloth. Just because someone or something appears to not be fully utilized is not an indication of their disutility.Consider the belts in your car’s engine. In order to operate effectively, they can’t be too tense, they must have some give. Engine optimization relies on belts having the appropriate amount of slack.It’s the same with our work. We need slack for our own optimization. In our work, we’d like to have a degree of slack to:

    1. Make sure we are able to focus on the tasks at hand;

    2. Make sure we have the capacity to deal with unforeseen events;

    3. Make sure we can stop periodically to allow our brains to perform vital functions in memory, processing, and regeneration; and especially to

    4. Make sure we don’t work ourselves into an early grave.

When we have unlimited WIP, we tend to start multiple tasks concurrently, and then run in circles trying to complete them. As we’ve discussed in our previous posts in this series, overwork creates additional work, heightens stress, and results in a poor quality product.

Focus on Tasks at Hand

Slack allows us to focus on the tasks at hand simply by giving us the ability to work in a non-freaked, sans-OMFG state. In the absence of slack, we aren’t only working on our current task, we’re fretting because we know there are countless other tasks we’ve started and that they demand completion. We live with an underlying fear that something, somewhere will break and when it does, it’ll be unlikely we’ll be able to deal with it.Slack is, in the end, a recognition that our time, our brainpower and our emotional fortitude are all limited. If we tax all these resources, we will not be able to do the work on our plate or deal with unforeseen events.

Unforeseen Events

When we’re overloaded with work, we invite panic. We invite emergencies. When we have zero capacity for new work, additional work exacerbates our overload. The thing is, unforeseen events are inevitable; they happen all the time. We can’t predict the future, we can only give ourselves the slack to deal with whatever may come our way - good or otherwise.If we have three tasks in process and something unexpected comes along, we - at worst - have four tasks in flight. This is still a substantial number less than most people currently have.  This doesn’t make the unforeseen event a welcome one, but it does make it a manageable one.

Rest, Processing, and Catch-up

Francesco Cirillo’s simple yet profoundly powerful Pomodoro Technique invites us to use a timer set to 25 minutes during which we focus without distraction. The timer’s ring alerts us to rest. The ratio suggested is 25 minutes of work to 5 minutes of rest - and then repeat (taking an even longer break after 4 successive pomodori). This isn’t merely to let us have a “coffee break.” Our brains need recharge points.The brain is not some easy going organ...it’s a resource hog.When we’re working intently on something, our brain burns a lot of calories, uses a lot of water, and gets tired. Allowing periodic points of slack allows us to hydrate, grab a snack, and recharge.Not only this, but the brain also works in three memory modes: short term, mid term, and long term. Having slack and taking breaks allows the brain to pause and write vital information from short to mid term memory. The more we overload ourselves with work, the more we forget.

Stayin’ Alive

As we can see, without incorporating slack into our work day, we end up taking on too much work, too much stress, and with too little down time. These factors decrease happiness and longevity. That’s not a good thing.We limit our WIP specifically to achieve a comprehensible workload that allows us to complete, understand the costs of our choices, make better decisions, and react elegantly to life’s surprises.

Why Not a WIP of One?: Why Limit WIP Series, Post 2

With only two guiding principles - Visualize your work and Limit your WIP - much of Personal Kanban seems fairly straightforward. But it’s not as obvious as it seems, and there’s actually a lot going on under the hood.Tons, actually. So let’s discuss.We said in the previous post we want to limit our work-in-progress, our “WIP,” and set it within a reasonable limit. But there’s still some confusion about what WIP really addresses.Does it mean:

A: At this very moment, what task am I actively doing with my hands?

or

B: At this very moment, what tasks am I am actually doing with my brain?

To be clear, your brain does more than your hands.This goes back to the role of the visual control in your life. As a visual control, your Personal Kanban keeps you honest about the work being done in your head.  The visual control is not necessary there to track what’s going on in your hands.So the Personal Kanban doesn’t need to tell you (A).This comment was left on our latest post How to Set Your WIP Limit:

Interesting. My WIP limit on my personal kanban has always been 1. Perhaps it’s just the way I’ve got it set up. For instance, right now the card I have in work is “read blog posts and comment”. Now, I have a ‘waiting’ lane for cards where I’m blocked from taking any direct action. So by having a different lane I suppose that’s an additional WIP item since it’s not complete, but I like to split that out if I can’t take any action on it myself at the moment. It re-enters my pull queue when the block has been resolved.What do you think about that Jim? Can I do better?-Josh

We’ve encountered numerous people who set their WIP limit to one and believe they are working on only one thing at a time. They will actually move cards in and out of DOING to note whether they are actively working on them. Again, what you are doing with your hands should tell you this.However, those tasks that were moved back into WAITING are still active. They are still IN PROGRESS. Simply because your fingers aren’t moving them right now, doesn’t mean your brain is not still DOING them.This is important, as the Zeigarnik Effect tells us two things about how we work:1: We have a psychological need to complete a task. Incomplete tasks tend to create intrusive thoughts, causing us to dwell on what we’ve left unfinished.2: We forget things that we’ve completed.In the book and in our talks, we go into great detail about how this impacts our work. For now, let’s focus on #1.When we begin a task and leave it unfinished, our brain keeps thinking about it. Psychologically we need closure, which can come from two sources - actual completion or officially deciding not to complete.If we have a column in our Personal Kanban that is just holding incomplete tasks, there will be an irresistible temptation to put more and more tasks in that column. We will come up with excuses like, “This one is more important” or “I don’t have time for that right now,” or “I’ll get to it later.”We want the DOING column to exert pressure on us. Our goal with Personal Kanban is to have a realistic WIP limit that is honestly displayed so that we can understand our options, better manage our work, and finish what we begin.More on this in future posts in the Why Limit WIP Series.

PK Basics: Why Limit Your WIP Series, Post 1

Limit your Work in Progress

In Personal Kanban we have only two rules. One of them is to limit your WIP.That sounds simple enough. But what does limiting your WIP really imply?This series describes what we mean by "WIP," why it's important to limit it, and - with all the competing demands on our time - how we can begin to go about doing just that.

WIP = Work-in-Progress

WIP is an acronym for "work-in-progress." It's the proverbial "stuff on your plate," the "balls you are juggling." It's the work you've begun and currently have in process.Now consider those things in your life that can and will at some point constitute your WIP:  deliverables you have at the office, improvement projects piling up at home, monthly bills that need tending to, doctors appointments that need scheduling, phone calls that need returning. Now take into account the things you enjoy doing (but that often get put on the back burner), like taking a photography class or working on your yoga practice. Things you both need and want to accomplish can add up to a huge number of tasks you have to hold in your head simultaneously.Some of these tasks are fairly low-impact. Others are more challenging and might require additional attention.We want to limit the number of active tasks we juggle because we have a "capacity" - a maximum amount of work we can process at a given time. We simply cannot do more work than we can handle.

What Happens When We Don’t Limit WIP

When we exceed the amount of work we can handle, it heightens our distraction and decreases our concentration.  Our attention to detail suffers, we leave things unfinished, or compromise the quality of our finished product.  All of these outcomes create more work or us in the future.

Forgetting

When we forget something - whether it entails leaving out important details or missing a deadline - invariably someone else will point out our misstep. When they do,  a conversation (most likely a pointed one) often ensues. Addressing and compensating for missteps takes time and effort, compounding cost, and ultimately frustration.

Leaving Things Unfinished

When we leave things incomplete we have two outcomes: (1) We never finish them or (2) We finish them later.For case (1) it's likely we've wasted time, effort, and resources.In case (2) we return to the task at a later date, when the task's context (its need, impact,  or resources available) might have changed. Oftentimes that requires looking at the task and figuring out exactly where we left off,  why we made the decisions we did, and what – exactly – was our preferred course to completion. This reorienting process of remembering and reorganizing likewise can consume time, and incur additional effort and resources.

Compromising Quality

A job poorly executed is sometimes worse than a job left incomplete. When work is done poorly, it usually contains defects. When defects become work multipliers, there are consequences down the line: defects can slow work down, break something else, or even hurt someone. Or they might just make your work product less helpful than it could have been had proper care been taken initially. If your defect is deemed serious enough to require repair (in essence, doing your work over again), first that defect must be discovered, then appreciated, then discussed, then deemed worthy of repair, then the repair needs to be identified, then acted upon.And those are the easy ones.When we compromise the quality of our work, we don’t just “do a bad job,” we leave someone to clean up an expensive and time consuming mess.

What Happens When We Do Limit WIP

We'd like to say that limiting WIP will solve all these problems, but it won’t. Nothing makes these things go away entirely.However, not limiting WIP means we are pretty much guaranteed to fall victim to these time wasters, and we are guaranteed to do it often.When we limit our WIP, we have less distractions. We are able to focus on correct decisions, completion, and quality.When we set a WIP limit, we are telling ourselves and the world around us that we want to get work done quickly, and we want to do a quality job.Even though prioritizing some tasks over others means some tasks have to wait, those tasks will still be completed sooner than they would have if we started them all right away. Since we are no longer paying the penalties for forgetting, incompletion, or poor quality, the work we finish is done faster and does not cause additional work.

What’s Next

This is just the tip of the iceberg as to why we should limit WIP. Over the upcoming months, we will be releasing more benefits to both Limiting Your WIP and Visualizing Your Work.Until then, there are other related resources on this site. Simply check out articles tagged “WIP,” or visit the PK 101 page.

What If I Had A Slack Card?

Showing Slack Card

“All things in moderation, including moderation.”― Mark TwainIn yesterday’s post, you may have noticed that we have a “Slack Card” in our Personal Kanban for the day.The problem we, like most people, were having was this:Productivity feels good.The Zone feels good.But productivity and the zone can lead to burnout.Just like Pomodoro includes rests every 25 minutes, we wanted to include a Pomodoro that was nothing but slack.What we assumed was that we have eight half hour pomodoros in an eight hour work day.Interruptions, non-focused tasks, and other minutia tend to make pomodoros not start back-to-back.Of those eight, the slack card is kind of a “get out of jail free” card. It can let you spend a free half hour just resting, it can be spent collaborating on less focused tasks, it can be used to “throw away” if interruptions stop you from being able to do one of your Pomodoro.  Ultimately it’s a visual place holder for an option. You be the judge.

How To: Mapping Your Value Stream

When we build our kanban – whether for ourselves or for a team – we first need to build a value stream. A value stream is simply a list of the steps you take to create value. When we build a kanban, work flows along the value stream and this visualizes our flow.

Before We Begin

There are some quick tips about a value stream.

  1. It should match reality as closely as possible.

  2. It should be only as detailed as necessary to see and understand your work flow.

  3. As your understanding and contexts change, your value stream will also change.

These three tips are telling. Words like stream,flow, and value are all difficult to pin down. They change, they evolve. In tip number one, we want to match reality as closely as possible. We will never draw a map that perfectly matches our workflow forever.

The Beginning: Start with the Ends in Mind

What is it you are doing?In a meeting you may be:

  • fully discussing a topic

  • coming up with action items

  • planning a future set of tasks

At home you might be:

  • delegating chores

  • planning a vacation

  • building a deck

During the workday you might be:

  • creating documents

  • managing staff

  • building a section of an airplane

Kanban End States

All nine of these might have very different end-states.So, if we are writing a report, the end state might be “publish.”The other end … your backlog … is usually called “Backlog” or “Ready”. That is where your value stream starts. So, for our publishing value stream, our backlog looks like this:

Next Step: Fill in the Blanks

Full Sample Value Stream

Between start and finish is creation. What steps do you take to create something? Working backwards from publish, we might have collation, before that is final, before that is second draft, and before that might be the first draft.This now starts to build a stream into which the specific sections of the report can flow. The report team can now track each section or chapter as it moves toward completion.

Important Bits to Remember

1. Your value stream is your best educated guess as to how your work is actually occurring.

For some teams, the value stream above will work nicely. They would likely have a report that is from a template and being updated or customized, because the value stream suggests a very orderly process with no surprises or constant re-writes. Other teams will have a value stream that visualizes more editing, document re-organization, or people involved.

2. Your value stream will change.

As mentioned above, your value stream will change as you better understand your work. You do not need to sit around for a month figuring out the perfect mapping of your value stream. Just get one up and start working. You can refine as you move along. Different phases of projects may require very different value streams. Do not allow yourself to fall into the trap of rigid process.

3. Your Value Stream is Fault Tolerant

If you move a stickie to the right and something changes to make you move it back to the left – this is not a problem. It is reality. You really did move a chapter from the first draft to the second draft, conditions changed and then it moved back to the first draft stage again.

This is a Personal Kanban 101 Post. See others in the series.

" "