Metacognitive Tool: Element #8 of the Kanban

double loop learning

METACOGNITIVE TOOL is one nice chunk of jargon.Metacognition is “learning about learning.” When we have a tool for it, that tool teaches us about how we learn. When we have some understanding about that, we can start to look for new ways to use the tool to learn more effectively.This is where something called “double-loop learning” comes in.When we use the kanban in our daily work we are employing several real-time techniques and strategies to get work done. “I’m going to make my tasks so they’ll take less than a few hours to complete.” “Today I’m going to work entirely on the City of Pelentagagagua proposal.” “I will do the work for my lawyer after I get this thing out of the way for my boss.”But while we are working, we are basing those decisions on a variety of assumptions. The kanban shows us, in real-time, the impacts of our assumptions. If we begin with an assumption that our office work is more important than getting things done for the family, after a while we’ll end up with a lot of aging family tickets and a DONE column filled with work tasks.When we see this, we’ll see that there is a cost to that assumption. That cost is a lot of pent up work for the house and likely an angry spouse.Other assumptions we might be making is that one client is more important than another, that if we do large tasks first we’ll get more done, or that if we deliver product at two-week intervals we’ll have a more predictable delivery schedule.We can use the real results from the kanban to question these basic assumptions, then alter our assumptions and see the results of that.As we do this, we learn:

• the results of our actions (single-loop);

• the effects of our basic assumptions (double-loop); and

• how that understanding impacts how we work, how we create experiments, and how we react to change (metacognition).

5s in Personal Kanban

Introduction

Personal Kanban is a great tool to visualize your work, to limit your WIP and to take better control of your life, either alone or together with your significant other, your kids or even your team at the office. In contrast to industrial Kanban, in Personal Kanban, the items contained in the value stream are often less defined and more often than not even the outcome is not clear. A "go shopping for dinner" task might be clear enough but you could as well end up checking the shelves in the supermarket and decide you prefer to get a Chinese takeaway instead.Nevertheless, if you have a Personal Kanban in place, customized to your own wishes and needs, suited for the way you like to work, things might or might not improve. After all, Kanban is only a tool, a method, and you still have to find the motivation inside you to make proper use of it. If you are so inclined, a simple Japanese philosophy might help you with this task.

5S

Like Lean and Kanban, 5S comes from Japan and is regarded as one of the fundaments for what literature named "Just-In-Time" production. It basically is a set of steps that streamline the way people work, eliminate waste and inefficiencies and help in reducing variation in the process. Of course, your daily schedule is not such a process but the basic idea of these five steps is still helpful. If you pay attention to them, your Personal Kanban will prove fruitful for you and you will reap the benefits. If you are reading this, chances are high that you already are, without knowing it.

Step 1 - Seiri

Seiri means as much as cleaning, throwing your junk away, and in a certain way, this is what you need to do when implementing your Personal Kanban. If you have used (or still use) different ways of keeping track of your tasks, get rid of them. No scribbles next to your keyboard, no sticky notes next to your phone, no random reminders in your mobile phone. Do a spring clean, if it's a task, put it in your Personal Kanban (the backlog, if it's for later on), if it's useless information, dump it. Make sure that there is only one place for you that contains all the information you need.

Step 2 - Seiton

Seiton means to bring things in order so you can use your Personal Kanban efficiently. It doesn't matter if you are using a big whiteboard, a table or your office door but whatever you use, you should have everything you need accessible. Stock up on post-it notes in different colours, have pens at hand, maybe even a filer so you can store your finished tasks for later. Whatever it is, you should not have to search for it when you want to work with your Personal Kanban, and the tools should neither be far away nor in an uncomfortable position. A corner in your room for example is a bad idea, as I guarantee that you'll lose your motivation if you constantly have to bend down to get a new post-it note.

Step 3 - Seiso

Seiso means to clean things or to shine them. This does not only mean that you should regularly take a cloth and scrub your whiteboard, if you have one, as noone likes dirt and dust. The bigger part of this means that you should keep your Personal Kanban tidy and in good shape. At the end of your workday, take a look at it, and ask yourself whether it is still a representation of your work. If tasks have become obsolete, then mark them as done. If you like to make notes to your tasks for later retrospectives, then now it's the time to do so. Rearrange what's left, reorder, make it look good. These minutes are not a lot of effort but if you start the next morning with a clean and up-to-date Kanban, you will feel better than if you had to start your day with cleaning things up first.

Step 4 - Seiketsu

Seiketsu is the task of standardizing things. Define for yourself a method for your Personal Kanban, and stick to it. If you use different colours or shapes for different kinds of things then be consistent with it. If you usually categorize doing your dishes as house chore, don't suddenly use a different category just because you couldn't find a post-it of the correct colour at hand. If you like to add deadlines to task items, make sure that each task with a deadline is marked accordingly. You want to be able to rely on the information your Personal Kanban gives you to make your decisions.

Step 5 - Shitsuke

Shitsuke means to sustain things and to be disciplined. Pay attention to the four steps above regularly. Use your Personal Kanban. Keep things clean and tidy, stick with the system you defined for yourself, restock on tools and whatever you need. And, above all: commit to what you are trying to achieve. Without discipline, your method will deteriorate over time and you'll gradually fall back into your way you worked before you introduced Personal Kanban. With discipline you will not only maintain but also over time improve your flow (through Kaizen), and you will have more often successful days when you see what you've done.

Conclusion

Most likely, all of the five steps mentioned above will sound obvious to you. For me, personally, they have formed a ritual and a mindset that help me maintain order and stability in my Personal Kanban, which leads to clarity and allow me to make the right decisions.

The Language of Metrics: Lean Muppets Series Post 4

It’s like a really heavy iPhone.

muppet brrrring scale

Silly aliens!In business, we mistake inanimate objects for our customers, our employees, our teams, and everyone else. Our inanimate objects are metrics. Just like the telephone, they are things we make to convey information, but we make a key mistake: we believe that metrics are in some way arbiters of reality.But just as we are what we eat, we become what we measure.The aliens here are vice presidents coming down to talk to the workers.They descend in their ship and approach the area in which their intelligence tells us the workers reside.In lean parlance, they are going to the gemba.Now, here's the really funny bit: the telephone really isn't the metric. The worker is the worker.These are workers who have been supplying management with meaningless statistics that measure output on a dual axised BRRRRRRRING scale. The longer and louder the BRRRRRRRING the better.The managers approach the worker who, after getting three consecutive raises for BRRRRINGing like there's no tomorrow, is on the fast track to becoming an alien.  That worker, after a time, does everything to satisfy the metric - to the point that it becomes the only way he can conceive of doing his job.Initially, the managers approach the worker and try to discuss things in English, then hunt around for other languages, only to learn that BRRRRING is all anyone can say.And the scary part is the end, where they are happily BRRRINGing along with the employee, because now it's the only thing the company can say.In his 14 Points, Deming said "Eliminate management by numbers and numerical goals. Instead substitute with leadership."  The more we rely on metrics to tell us what happened, the more we distance ourselves from the actual work being done. We lose sight of changes in context and cannot deftly react when necessary. Further, we build games and systems that reward paying attention to the metric and not the success of the company.People will care about what the system cares about. If your company has reams of reports generated daily or weekly, you are not "managing by the number" you are building a culture of BRRRRRRING.This is fourth in a series of Lean Muppet posts. For a list of Lean Muppet posts and an explanation of why we did this, look here. -> Lean Muppets Introduction

Mozart’s Record Store: Personal Kanban Anti-Pattern 2: Only One Value Stream

 I will not be accused of burying the lead here and say right up front:

Your Value Stream Is Wrong

Normal PK Board

And it always will be.This is a good thing, as we work from day to day the steps we take to complete work subtly or even violently change. When we move from home to work to a special project, there are subtle and important differences to how we do what we do.Today’s anti-pattern is is painful to watch. When people fall into a certain way of visualizing their work or a certain value stream, it becomes comfortable to them. So comfortable, in fact, that they are reluctant or downright resistant to change or improve it. They then flounder in increasing painful work because their value stream doesn’t match their actual needs.Let’s say for example that Mozart is the manager of a record store in Bavaria.  He has three main types of work over a given month. One is order new stock from a variety of suppliers. The second is make sure the books are in order. The third is … everything else.Everything else is actually easy - even though it may be rather chaotic at times. We visual this type of work with a standard Personal Kanban value stream of READY | DOING | DONE. The work is going to be varied and extremely task-focused. Each of Mozart’s tasks is its own element of value. The best way to manage this work, to weigh these options, and to get these tasks completed is in a model that accepts the complexities and inherent chaos of day-to-day work.However, in other more project centered types of work, he may get more from value streams geared toward tracking of that specific work or project.For example, when ordering stock, the ideal world would tell you that orders are placed and received each month at set times. Mozart’s store has a mix of goods provide through suppliers ranging from large vendors to one person in their basement. Order responses are highly varied, leaving Mozart having to track not only the rate at which inventory is sold, but also the average response times for ordering popular items.So here we see Mozart’s order processing kanban. The value stream is quite specific to the value created. This is repeating value created in a fairly predictable way. If Mozart was only using the READY | DOING | DONE value stream for this type of project, he would have dozens of tasks polluting the rest of his work. The stages in these value streams may not actually be tasks. So, say he finds it’s time to order a new set of Buddha Machines - so he contacts the people in China via email. When he does that he can move the Buddha Machine ticket to ORDER.  A few days later, they might send him a letter saying, “We received your order and will get to it soon.” Mozart can then move the ticket to CONFIRMED - even though he really didn’t do any task himself. The point here is that there is new useful information about the state of the Buddha Machine order. A few days later, he gets an e-mail saying that the Buddha Machines have shipped. Mozart again can move the ticket.From time to time, new tasks may appear in Mozart’s regular Personal Kanban that say things like “Order new AxMxAx album”. At that point, when Mozart does do the ordering, he will move that ticket to done, but also start a new ticket in the order processing kanban.So, here we see that Mozart’s work can have more than one value stream.Now, let’s say this works for Mozart for a while, but he begins to notice that even after he receives confirmation many orders are not shipped.  Tickets start to back up at the “ordered” stage but don’t progress beyond. Mozart can then come up with ways to fix that problem. For example, he could insert a “remind vendor” column that he can move tickets to if they aren’t shipped in less than a week.Mozart must change his value streams to meet his needs. So must we all.

Planning is Indispensable. Personal Kanban Anti-patterns Series 1

In the early 2000s, people discovered how great pomegranate juice is. It’s filled with antioxidants that help us avoid colds and other maladies. Well, no one likes to be sick, so people started buying the juice by the case. Sure enough, they felt healthier. So they drank more and more until they started getting ulcers because they were repeatedly filling their stomachs with acid.This is an “anti-pattern”. A by-product of a beneficial act that corrupts that act into something harmful. It doesn't mean that pomegranate juice is evil. It means you can use it for better and for worse.This series discusses some Personal Kanban anti-patterns I’ve been seeing evolve over the last few years.Over the last several months, I’ve run into several situations where people have uttered variations on a disturbing statement… “We don’t do planning because we have a kanban.” This is our first anti-pattern.Some teams, weary of lengthy planning meetings in the past, have misinterpreted flow-based systems as systems that – in essence – are self-planning.A flow-based system is not self-anything – except perhaps self-reporting.The whole point of having a Kanban is to be aware. It is dangerous to turn control of your life, your work, or your future to anything – especially a white board with sticky notes on it.You as a person or team using Personal Kanban need to be vigilant that you are making the right decisions at the right time. In order to do that, you need to understand what work is coming on the horizon, why it is there, and what is NOT being done while you are doing something else.If you are not planning as you go along, you are ignoring what is coming up. It is also highly likely you are missing opportunities to improve, complete, and find efficiencies.Personal Kanban does not preclude planning, it makes planning more enjoyable.