Mike Rother: The Toyota Kata Practice Guide

When I landed in Detroit last week to visit Menlo Innovations, Mike Rother picked me up at the airport. As soon as I settled in to the passenger’s seat, he handed me my long-anticipated copy of his new book The Toyota Kata Practice Guide. That is the first disclaimer here. The second disclaimer is that last winter he asked if I would do him a favor and take a look through the manuscript with a red pencil. Um… YEAH!

Thus, I can’t say this post is an unbiased book review. Quite the opposite.

What I am going to do here is go through the book and alternately share two things:

  1. Why I think this is a great read for anyone, no matter your skill level or experience with Toyota Kata.
  2. Reflections on my own experience that may have been amplified as I went through it.

The other caveat I really have to offer is this: I have the hard copy of the book. I am absolutely referring to it for the content I am citing. That being said, I drew a lot of the deeper insights I am reporting when I was parsing the manuscript. That was much more than “reading” as I had to really think about what the author is trying to say rather than just read it. If you are serious about learning, I suggest you take your time as you, too, go through the book. Don’t just read. Parse.

And a final disclosure: if you click on the links mentioning the books, it will take you to the Amazon.com page. If you choose to buy the book, I get small affiliate kickback that doesn’t affect the price you pay.

A Bit of History: Toyota Kata has Evolved

From my perspective, I think Toyota Kata as a topic has evolved quite a bit since the original book was published in 2009. The Practice Guide reflects what we, as a community, have learned since then.

As I see it, that evolution has taken two tracks.

1. More Sophistication

imageOn the one hand, the practice has become more sophisticated as people explore and learn application in contexts other than the original industrial examples. Mike Rother and Gerd Aulinger published Toyota Kata Culture early this year. That book provides working examples of vertical linkage between organizational strategy and shop floor improvement efforts. Most of the presenters at Lean Frontier’s recent online Kata Practitioner Day were describing their experiences applying what was outlined in that book. Last year’s KataCon featured a number of presenters who have adapted the routines to their specific situations, and we have seen the Kata morph as they are used “in the wild.” This is all OK so long as the fundamentals are practiced and well understood prior to making alterations – which brings us to the second point.

2. Better Focus on Kata as Fundamentals

The other evolution has been a better insight that the Improvement Kata and Coaching Kata are, in Mike Rother’s words, Starter Kata. They aren’t something you implement. They are routines to practice as you develop the underlying skill.

If you go to a Toyota, or a Menlo Innovations, you won’t see them using Toyota Kata. They don’t have to because the routines that the Kata are designed to teach are already embedded in “the way we do things” in organizations like that.

We use the Improvement Kata and Coaching Kata to learn so that, at some point in the future, we too can create a culture where the underlying thinking is embedded in “the way we do things.” You don’t have to think about it, because it is a habit.

Rather than being a fairly high-level summary of the research findings (as the original book was), the Practice Guide is what the title suggests: A step-by-step guide of how to practice and what to practice.

The Toyota Kata Practice Guide

With all of that as background, let’s dig into the book.

The book is divided into three discrete sections. I’m going to go through the book pretty much in order, with the section and chapter titles as headers.

Part 1: Bringing Together Scientific Thinking and Practice

The first part of the book is really an executive summary of sorts. It is an excellent read for a manager or executive who wants better understanding of what this “Toyota Kata” thing you (my reader here) might be advocating. It sets out the fundamental “Why, what and how” without bogging down in tons of detail.

Scientific Thinking for Everyone

This is the “Why”  and “What.”

In the first chapter Mike Rother makes the case that “scientific thinking” is the meta-skill or habit that found in most (if not all) learning and high-performance organizations. I agree with him. I believe organizations with an innate ability to reflexively apply good scientific thinking are the ones who can readily adapt to changes in their environment. Those who cannot are the ones who keep doing the same things in the face of evidence that screams “Change!”

The next key point is that “scientific thinking” is not the default habit of the vast majority of adult humans – for lots of good reasons leading to our survival as a species. It is a learned skill.

Learning a skill requires practice, plus knowing what and how to practice. The Improvement Kata provides a pattern for practice as well as initial routines to follow in order to get the fundamentals.

And that point is what separates the Practice Guide from the vast majority of business books. Most business books speak in general terms about principles to apply, and ways you should think differently. They are saying that “you need to develop different habits,” and even telling you what those habits should be, but come up short on telling you how to change your existing habits to those new habits.

Thus if you, the reader of the book, are willing to say “I want to learn this thinking pattern,” as well as say “… and I am willing to work at it and make mistakes in order to learn,” then this book is for you. Otherwise, it probably isn’t. That’s OK.

For the rest of you, read on.

Chapters 2, 3 and 4 go into increasing depth on the process of “deliberate practice” how the structure of the Improvement Kata and Coaching Kata supports it.

Part 2: Practice Routines for the Learner (The Improvement Kata)

At a high level the “Improvement Kata” is expressed as a four step process that maps to pretty much any process of learning, discovery or problem solving that works.

image

In this section, there is a chapter for each of the steps above that sets out, in detail:

  • The higher level purpose of the step – the “why?”
  • The discrete steps you should practice, including detailed “How to” instructions as step-by-step Starter Kata that a learner should follow precisely while he is grounding on the basics.

I believe it is equally important for new coaches to work hard to keep their learners focused on the Starter Kata as well – you are both in learning mode. (More about coaches in the next section.)

I do, though, want to discuss the one step where I can see people having the biggest struggle mapping the explicit Starter Kata to their own situation: Grasp the current condition.

The Starter Kata steps for Grasping the Current Condition are explicit and detailed. At a high level they are:

1. Graph the Process Outcome Performance

2. Calculate the Customer Demand Rate and Planned Cycle Time

3. Study the Process’s Operating Patterns

4. Check Equipment Capacity

5. Calculate the Core Work Content

The book devotes several pages to how to carry out each of these steps. However, the examples given in the book, and the way it is usually taught, use the context of industrial production processes. This makes sense. Industry is (1) the origin of the entire body of thought and (2) the world the vast majority of practitioners live in.

But we legitimately get push-back from people who live in a world outside of industry. What I have found, though, is when we work hard to figure it out, we can usually find solid analogies where the Starter Kata do apply to practically any non-industrial process where people are trying to get something done.

Often the mapping isn’t obvious because people in non-linear work are less aware of the repeating patterns they have. Or they live in worlds where the disruptions are continuous, and though a cadence is intended, it seems to be impossible to achieve. However, if you are legitimately making an effort, and having trouble figuring out how to apply the Starter Kata outlined in the book to your own experience, here is an offer: Get in touch. Let’s talk and see if we can figure it out together.

A Little More about Starter Kata

The concept of “Starter Kata” is new since the publication of the original book. Actually it isn’t really new, just much more explicit now.

When we see working examples, such as in books about A3 Problem Solving, we are often looking at the work of people who are unconsciously competent, if not masters, of doing this.

To someone trying to learn it, though, all of these “different approaches” can be confusing if they are trying to just understand what they should do. A coach trying to help by giving them a lot of general guidelines as decision criteria often isn’t helping much to clarify the confusion. (And may well be adding to the frustration.)

The point of a “Starter Kata” is to provide a high level of structure that can guide the learner until she “gets” the higher level purpose. In traditional east-Asian martial arts, this higher purpose is often left unspoken, with the intent that the learner will reflect and come to deeper understanding.*

In the Practice Guide Mike is much more clear about the underlying “why” of the emphasis on initial rote practice. We, the readers, are in Stage 1 in this illustration:

image

 

If you are trying to understand what Toyota Kata is about, or you are trying to up your own skills for process improvement or problem solving, then read the steps that are set out in the book and follow them exactly as they are written to the best of your ability. Do this even (especially!) if they don’t seem 100% appropriate to the problem you are trying to solve.

“But I’m not a beginner” you might say.

Let me issue this personal challenge: Pretend you are a beginner. All of us can learn from going back and applying the basics. You may well discover:

  • Additional insights about things you are already doing. (Which I did.)
  • Some approaches that are simpler and more effective than what you have evolved over the years. (Which I did.)
  • More comfort with using these Starter Kata as a teaching guide for others. (Which I have.)

Although this material on the Improvement Kata has been “out in the wild” for some time, I think I can honestly say that The Toyota Kata Practice Guide is a vastly better expression than I have seen anywhere else – including earlier material from Mike Rother – and my own previous material for that matter. (I started making changes to my own materials based on my early look at the manuscript.)

Part 3: Practice Routines for the Coach (The Coaching Kata)

This is the new and exciting part.

While there has been a fair amount about the Improvement Kata out there for a while, the only things we have had about coaching have been the “5 Questions,” a few YouTube videos and some general principles. I’ve tried on this site to relate my own experiences as I learned, but The Toyota Kata Practice Guide is, in my view, the first truly comprehensive reference that wraps up everything we knew up to this point in a single reference.

Tangent: Learn to Play Before You Coach

Though this is part of the message in the book, what follows are my own experiences and interpretations.

Nearly all managers want to jump right into coaching. They see the “5 Questions” and some of them think that is all there is to it – just ask those questions and we’re good. Actually, that’s kind of OK so long as you realize that you are probably making mistakes, and are consciously and deliberately reflecting on what those mistakes might be. But that reflection is often what doesn’t happen – people tend to presume competence, and don’t challenge their own role if they see learners struggling. It is a lot easier for me to blame the learner, or to say “this kata thing doesn’t work” than it is to question my own competence.

Until you have struggled as a learner to apply the Improvement Kata (using the Starter Kata) on a real problem (not just a classroom exercise) that affects the work of real people and the outcomes to real customers, please don’t just pick up the 5 Questions card and think you are a coach.

Coaching Starter Kata

If you truly understand the Improvement Kata, and then go to a Toyota, or other company that has a solid practice for continuous improvement, you will readily see the underlying patterns for problem solving and improvement. Coaching, though, is a bit more abstract – harder to pin down into discrete steps.

Read John Shook’s excellent book Managing to Learn (and I highly recommended it as a complement to The Toyota Kata Practice Guide), and you will get a good feel for the Toyota-style coaching dialog. You won’t read “the 5 Questions” in that book, nor will you see the repetitive nature of the coaching cycles that are the signature hallmark of Toyota Kata.

Here’s why:

There are a couple of ways to learn that master-level coaching. One is to work your entire career in an organization that inherently thinks and talks this way. If you do, you will pick it up naturally “as the way we do things” and won’t give it another thought. Human beings are good at that – its social integration into a group.

Imagine, if you would, growing up in a community where everyone was a musician. Thinking in the structure of music would be innate, you wouldn’t even be aware you were doing it. Growing up, you would learn to play instruments, to sing, to compose, to arrange music because that is what everyone around you was doing. That is also how we learn the nuance of language. We can see throughout history how mastery in arts tends to run in families. This is why.

And that is how the coaching character in Managing to Learn gained his skill.

But if you want to learn music, or another language, or some other skill, when you aren’t immersed in it all day, then you have to learn it differently. You have to deliberately practice, and ideally practice with the guidance of someone who not only has the skill you are trying to learn but also has the skill to teach others. (Which is different.)

The question Mike Rother was trying to answer with his original research was “How can the rest of us learn to think and coach like that?” – when we don’t live in that environment every day. In those cases we have to be overt and deliberate.

The real contribution that Mike has made to this community is to turn “coaching” from a “you know it when you see it” innate skill into a routine we can practice to learn how to do it. I can’t emphasize that enough.

And, although the Coaching Kata is taught within a specific domain of process improvement, the underlying questions are the basis for anything people are working to achieve. Cognitive Based Therapy, for example, is structured exactly the same way.**

OK – with all of those rambling thoughts aside, let’s dig back into the book.

As in the previous section, we begin with an introduction section that gives an overview of what coaching is actually all about.

Then the following chapters successively break down the coaching cycle into finer and finer detail.

Coaching Cycles: Concept Overview

This chapter emphasizes the cadence of coaching cycles, the importance of frequent practice (for both the coach and the learner), and the purpose and structure of the “5 Questions.”

A key point that bears emphasizing here is that the purpose of coaching is to advance the learner’s knowledge, both of the process being addressed and the “art of scientific thinking.” Thus, the reason the coach asks the questions is to learn where the boundary is between what the learner knows, and what the learner doesn’t know.

Often the learner himself isn’t aware of that boundary. Again, it is human nature to fill in the narrative, complete the story, and create meaning – jump to conclusions even with limited evidence. By asking for specifics, and by gently asking for evidence – “How do you know?” types of questions, the coach learns that point where the learner moves beyond objective facts and into speculating. (Or, ideally, says “I don’t understand” or “I don’t know” about something that needs to be understood or known.) The “next step or experiment” should be a step that pushes that threshold of knowledge boundary out a little further.

In the book, we get an example coaching dialog, and some warnings and cautions about commonly ingrained habits we probably all have to “give the answers” rather than “ask the questions.”

This chapter wraps up with some advice about when (and why) you (as a coach) might need to let go of the formal structure if a learner is struggling with it.

How To Do a Coaching Cycle: Practice Routines

After the overview, Mike gets down to what to do, how do give good corrective feedback, and keep the learner in the game psychologically.

He then gives us a detailed example coaching dialog, and afterwards, puts us into the role of the 2nd Coach, challenging the reader to predict what feedback the 2nd coach should give before reading what actually happens.

The dialog is followed by what I think is the most powerful part of the book as he guides us through each of the “5 Questions.” For each one, we get a description of why that question is important, its purpose, followed by:

  • Key Points – Advice that reflects feedback and helpful tips gained over the years from the entire community.
  • Clarifying Questions – Possible follow-on questions that can help the coach clarify what the learner is intending and thinking.
  • Potential Weak Points – Things to specifically look for that can help the learner construct better logical connections and experiments.

This chapter, in my view, is alone worth the price of the book. Everything else is bonus material.

Conclusion

This post took me quite a bit longer to write than I predicted it would, and I’ll judge that it is still rougher than I would like. But I am going to suppress my inner perfectionist and put it out there.

Anyone who knows me is aware that, even before it was published, I have made no secret about touting this book to anyone who is interested in continuous improvement.

In the end, though, this book is asking you to actually do some work. People who are looking for easy answers aren’t going to find them here. But then, I really don’t think easy answers can be found anywhere if we are honest with ourselves.

As I said about the original book back in 2010, I would really like to find copies of The Toyota Kata Practice Guide on the desk of every line leader I encounter. I want to see the books with sticky notes all over them, annotated, highlighted. The likely reality is that the primary readers will be the tens of thousands of staff practitioners who make up the bulk of the people who are reading this (you aren’t alone).

If you are one of those practitioners, YOUR challenge is to learn to teach by the methods outlined here, and then learn to apply them as you coach upward and laterally to the leaders of your respective organizations. Those conversations may have different words, but the basis is still the same: to help leaders break down the challenges they face into manageable chunks and tackle the problems and obstacles one-by-one.

One Final Note:

The overall theme for the 2018 KataCon is practice – keying off of the release of this book. Come join us, share your experiences, and meet Mike Rother, Rich Sheridan, and other leaders in this awesome community.

——–

*Those of us who were taught by Japanese sensei, such as Shingijutsu (especially the first generation such as Iwata, Nakao, Niwa) were expected to follow their instructions (“Don’t ask Why?… Say “Hai!”). It was implied, but never stated, that we should reflect on the higher-level meaning. Over the years, I have seen a fair number of practitioners get better and better at knowing what instructions would be appropriate in a specific case, but never really understand the higher-level meanings or purpose behind those tools. Thus, they end up as competent, but mechanistic, practitioners.

**Note: Mastering the Coaching Kata will not make you a therapist, though it may help you empathetically help a friend in need.

Heavy Equipment Overhaul: Flow at Takt in 1938!

This is a great contemporary film from 1938 describing the complete overhaul of a mainline 4-6-0 steam locomotive in the U.K.

What is interesting (to me) is:

  • The overhaul involves stripping the locomotive down to individual parts. Each of the parts, in turn, flows through a process of inspection / repair or replacement, with a strict timing to ensure it is delivered back to re-assembly when required.
  • There are 6 positions with a takt time of 10 hours 44 minutes. Everything is timed to this cadence.
  • I can only speculate, but with that degree of rigor in the timing, they are going to be able to see a delay or problem very quickly, and get out in front of it before it causes a delay in the main-line work.
  • The parts that come off are not necessarily the exact once that are put back on. Everything is flowing – there are multiple locomotives in overhaul.

More thoughts below the video.

(Here is a direct YouTube link for those who don’t get the embed in the email subscription: https://www.youtube.com/watch?v=ktHw1wR9XOU)

Flow in Overhaul and Repair

This is a great working example of a process flow that proves difficult for some organizations: Overhaul and repair. “We don’t know what we will find, so there is no way we can sequence and index it on a timetable.”

I’ve seen a similar operation overhauling helicopters. The intended flow was exactly the same.

  • Like the locomotive flow, they stripped everything down to the airframe. The various components had different flow paths for sheet metal, hydraulic components, power-train (engine / transmission), rotor components, electrical, avionics, and composite parts.
  • The objective was to deliver “good as new” items on time back to the re-assembly process.

Here is where they ran into problems:

  • If an item needed repair, then the repairs were done, and the item flowed back.
  • But if an item could not be repaired (needed to be scrapped and replaced) it was tagged, and returned to the “customer” – the parts bin in main assembly. It arrived just like any other part except this one was tagged as unusable. It was up to the assembly supervisor to notice, and initiate ordering a new one.

Who is your customer? What do they need?

The breakdown was that the repair line(s) saw themselves as providing a repair service. If it couldn’t be repaired, sorry.

What their customer needed was a good part to install on the helicopter. If they can create a good part by repairing the old one, great. But if it isn’t repairable, their customer still needs a good one and they need it on time.

The Importance of Timing and Sequencing

In the locomotive video, they emphasize the precise timing and sequencing to make sure each part arrives in the proper sequence, when it is needed, where it is needed.

Even if it actually worked like they describe, I can be sure it didn’t work like that when they first started.

The timing and sequencing is a hypothesis. Each time they overhaul a locomotive, in fact each individual part flow, is an experiment to test that hypothesis. Over time, it is possible to dial things in very precisely.

Why? So you can quickly identify those truly anomalous conditions that demand your intervention.

Normal vs Abnormal

Just because there are frequent issues does not negate the fact that most of the time things can probably flow pretty well. What we tend to do, however, is focus on the problem cases and give up on all of them. “What about this? What about that?” bringing up the legitimate issues and problems, causes us to lose sight of the fact that underneath it all there is a baseline pattern.

What is important is to define the point at which we need to intervene, and set up the process to detect that point. When we can clearly distinguish between routine work and true exceptions, and not try to treat everything as a special case.

Executive Rounding: Taking the Organization’s Vitals

Background:

image

I wrote an article appearing in the current (October 2017) issue of AME Target Magazine (page 20) that profiles two very different organizations that have both seen really positive shifts in their culture. (And yes, my wife pointed out the misspelling “continous” on the magazine cover.)

The second case study was about Meritus Health in Hagerstown, Maryland, and I want to go into a little more depth here about an element that has, so far, been a keystone to the positive changes they are seeing.

Sara Abshari and Eileen Jaskuta are presenting the Meritus story at the AME conference next week (October 9, 2017).

Sara is a manager (and excellent kata coach) in the Meritus CI office. Eileen is now at Main Line Health System, but was the Chief Quality Officer at Meritus at the time Joe was presenting at KataCon.

Their presentation is titled Death From Kaizen to Daily Improvement and outlines the journey at Meritus, including the development of executive rounding. If you are attending the conference, I encourage you to seek them out – as well as Craig Stritar – and talk to them about their experiences.

Mark’s Word Quibble

In addition, honestly, the Target Magazine editors made a single-word change in the article that I feel substantially changed the contextual meaning of the paragraph, and I am using this forum to explain the significance.

Here is paragraph from the draft as originally submitted. (Highlighting added to point out the difference):

[…][Meritus][…] executives follow a similar structure as they round several times a week to check-in with the front line and ensure there are no obstacles to making progress. Like the Managing Daily improvement meetings at Idex, the executive rounding at Meritus has evolved as they have learned how to connect the front-line improvements to the strategic priorities.

This is what appears in print in the magazine:

[…][Meritus][…] executives follow a similar structure as they visit several times a week to check in with the frontline and ensure there are no obstacles to making progress. Like the MDI meetings at Idex, the executive visiting at Meritus has evolved as they have learned how to connect the front-line improvements to the strategic priorities.

While this editing quibble can easily be dismissed as a pedantic author (me), the positive here is it gives me an opportunity to highlight different meanings in context, go into more depth on the back-story than I could in the magazine article, and invite those of you who will be attending the upcoming AME conference to talk to some of the key people who will be presenting their story there.

Rounding vs. Visiting

In the world of healthcare, “rounding” is the standard work performed by nurses and physicians as they check on the status of each patient. During rounds, they should be deliberately comparing key metrics and indicators of the patient’s health (vital signs, etc.) against what is expected. If something is out of the expected range, that becomes a signal for further investigation or intervention.

“Visiting” is what the patient’s family and friends do. They stop by, and engage socially.

In industry, we talk about “gemba walks,” and if they are done well, they serve the same purpose as “rounding” on patients in healthcare. A gemba walk should be standard work that determines if things are operating normally, and if they are not, investigating further or intervening in some way.

I am speculating that if I had used the term “structured leader standard work” rather than “rounding” it would not have been changed to “visiting.”

Executive Rounding

Joe Ross, the CEO at Meritus Health, presented a keynote at the Kata Summit last February (2017). You can actually download a copy of his presentation here: http://katasummit.com/2017presentations/. The title of his presentation was “Creating Healthy Disruption with Kata.” More about that in a bit.

The keystone of his presentation was about the executives doing structured rounding on various departments several times a week. These are the C-Level executives, and senior Vice Presidents. They round in teams, and change the routes they are rounding on every couple of weeks. Thus, the entire executive team is getting a sense of what is going on in the entire hospital, not just in their departments.

Rather than just “visiting,” they have a formal structure of questions, built from the Coaching Kata questions + some additional information. Since everyone is asking the same basic questions, the teams can be well prepared and the actual time spent in a particular department is programmed to be about 5 minutes. The schedule is tight, so there isn’t time to linger. This is deliberate.

After the teams round, the executives meet to share what they have learned, identify system-wide issues that need their attention, and reflect on what they have learned.

In this case, rather than rounding on patients, the executives are rounding to check the operational health of the hospital. They are checking the vital signs and making sure nothing is impeding people from doing the right thing – do people know the right thing to do? If not, then the executives know they need to provide clarity. Do people know how to do the right thing? If not, then the executives need to work on building capability and competence.

In both cases, executives are getting information they need so they can ensure that routine things happen routinely, and the right people are working to improve the right things, the right way. In the long-term, spending this time building those capabilities and mechanisms for alignment deep into the operational hierarchy gives those executives more time to deal with real strategic issues. Simply put, they are investing time now to build a far more robust organization that can take on bigger and bigger challenges with less and less drama.

Results

Though they were only a little more than a year in when Joe presented at KataCon, he reported some pretty interesting results. I’ll let you look at the presentation to see the statistically significant positive changes in employee surveys, patient safety and patient satisfaction scores. What I want to bring attention to are the cultural changes that he reported:

image

Leadership Development

Actually points 1. and 2. above are both about leadership development. The executives are far more in touch with what is happening, not only in their own departments, but in others. Even if they don’t round on their own departments, they hear from executives who did, and get valuable perspectives and questions from outsiders. This helps break down silo walls, build more robust horizontal linkages, and gives their people a stage to show what they are working on.

Since executives can’t be the ones with all of the solutions, they are (or should be) mostly concerned with developing the problem solving capabilities in their departments. At the same time, rounding gives them perspective on problems that only executive action can fix. In a many organizations mid-manager facing these systemic obstacles would try to work around them, ignore them, or just accept “that’s the way it is” and nothing gets done about these things. That breeds helplessness rather than empowerment.

On the other hand, if a manager should be able to solve the problem, then there is a leader development opportunity. That is the point when the executive should double down on ensuring the directors and upper managers are coaching well, have target conditions for developing their staff, and are aware of who is struggling and who is not. You can’t delegate knowing what is actually going on. Replying on reports from subordinates without ever checking in a couple of levels down invites well-meaning people to gloss over issues they don’t want to bother anyone about.

Breaking Down Silos by Providing Transparency

The side-benefit of this type of process is that the old cultures of “stay out of my area” silos get broken down. It becomes OK to raise problems. The opposite is a culture where executives consider it betrayal if someone mentions a problem to anyone outside of the department. That control of information and deliberate isolation in the name of maintaining power doesn’t work here. Nobody likes to work in a place like that. Once an organization has started down the road toward openness and no-blame problem solving, it’s hard to turn back without creating backlash of some kind within the ranks.

Creating Disruption

Joe used the term “Disruption” in the title of his presentation. Disruption is really more about emotions than process. There is a crucial period of transition because this new transparency makes people uncomfortable if they come from a long history of trying hard to make sure everything looks great in the eyes of the boss. Even if the top executive wants transparency and getting things out in the open, that often doesn’t play well with leaders who have been steeped in the opposite.

Thus, this process also gives a CEO and top leaders an opportunity to check, not only the responses of others, but their own responses, to the openness. If there are tensions, that is an opportunity to address them and seek to understand what is driving the fear.

In reality, that is very difficult. In our world of “just the facts, ma’am” we don’t like to talk about emotions, feelings, things that make us uncomfortable. Those things can be perceived as weakness, and in the Old World, weakness could never be shown. Being open about the issues can be a level of vulnerability that many executives haven’t been previously conditioned to handle. Inoculation happens by sticking with the process structure, even in the face of pushback, until people become comfortable with talking to each other openly and honestly. The cross-functional rounding into other departments is a vital part of this process. Backing off is like stopping taking your antibiotics because you feel better. It only emboldens the fear.

These kinds of changes can challenge people’s tacit assumptions about what is right or wrong. Emotions can run high – often without people even being aware of why.

Competence and Clarity: Toyota Kata at Sea

A friend, and reader, Craig sent a really interesting email:

As I was practicing the coaching Kata with one of the First Mates on the factory trawler, whenever an issue arose (usually with the leader blaming an employee) he began asking factory and engineering leadership “what needed to be communicated?” or “what needed to be taught?” He found it encompassed every problem on the vessel and I loved that he made it his own and communicated in manner to which lifetime fishermen could relate.

What I found really cool about this is how it is exactly the same conclusion reached by David Marquet, both in the sketchcast video I posted earlier, and the titles of two chapters in his book. The reasons leaders feel they must withhold authority, remain “in control” ultimately come down to competence – what must people be taught, or clarity – what have we failed to adequately communicate. Maybe it’s being at sea.

In other words, if people know whGiveControl.pngat to do (clarity), and know how to do it (competence), then leaders generally have no issues trusting that the right people will do the right things the right way.

The Improvement Kata  is a great structure for creating and carrying out development plans for leaders (or future leaders) in your organization.

The Coaching Kata is a great way to structure your next conversation to (1) ensure clarity of intent: Does their target condition align with the direction and challenge? and (2) develop their competence, both in improving / problem solving, but also in their understanding of the domain of work at hand.

 

 

 

Learning To See in 2013

With the publication of Learning to See in 1999, Mike Rother and John Shook introduced a new genre of book to us – a mix of theory, example, and practical application. The story invites the readers to follow along and actually do for themselves.

This is one of those books that gives a bit more every time I read it. The more thorough my baseline understanding of TPS, the more I get from some of the nuances of Rother and Shook’s intent.

At the same time, I am beginning to formulate an idea that perhaps this book is often used out of its intended context – maybe a context that was assumed, but left unsaid.

I’d like to share some of the things I have learned over the years, especially as I have worked to integrate the concepts in Learning to See into other facets of the TPS – especially research by Steven Spear, Jeff Liker, and of course, Mike Rother’s follow-on work Toyota Kata with my own experience.

Value Streams

Learning to See introduced the term “value stream” to our everyday vernacular.

Although the term is mentioned in Lean Thinking by Womack and Jones, the concept of “map your value streams” was not rigorously explained until LTS was published.

To be clear, we had been mapping out process flows for a long time before Learning to See. But the book provided our community with a standard symbolic language and framework that enabled all of us to communicate and share our maps with others.

That, alone, made the book a breakthrough work because it enabled a shorthand for peer review and support within the community.

It also provided a simple and robust pattern to follow that breaks down and analyzes a large scale process. This enabled a much larger population to grasp these concepts and put them to practical use.

Learning to See and “Getting Lean”

In Chapter 11 of Lean Thinking, Womack and Jones set out a sequence of steps they postulate will transform a traditional business to a “lean one.”

The steps are summarized and paraphrased in the Forward (also by Womack and Jones) of Learning to See:

  1. Find a change agent (how about you?).
  2. Find a sensei (a teacher whose learning curve you can borrow)
  3. Seize (or create) a crisis to motivate action across your firm.
  4. Map the entire value stream for all of your product families.
  5. Pick something important and get started removing waste quickly, to surprise yourself with how much you can accomplish in a very short period.

Learning to See focuses on Step 4, which implies establishing a future-state to guide you.

In the Forward, Womack and Jones commented that people skipped Step 4 (map your value streams). Today, I see people skipping straight to that step.

Let’s continue the context discussion from the Forward, then dig into common use of the value stream mapping tool..

“Find a change agent (how about you?)” is a really interesting statement. “How about you?” implies that the reader is the change agent. I suspect (based on the “change agents” discussed in Lean Thinking that the assumption was that the “change agent” is a responsible line leader. Pat Lancaster, Art Byrne, George Koenigsaecker were some of the early change agents, and were (along with their common thread of Shingijutsu) very influential in the tone and direction set in Lean Thinking.

Today, though, I see job postings like this one (real, but edited for – believe it or not- brevity):

Job Title: Lean Manager

Reports To: Vice President & General Manager of Operations

Summary:

Lead highly collaborative action-based team efforts to clean out, simplify and mistake-proof our processes and our strategic suppliers’ processes.

This includes using proven methodological approaches, applying our culture and providing our team with technology, best cross-industry practices and all other resources needed to attain ever higher levels of productivity and customer delight.

Essential Duties and Responsibilities:

Endlessly define, prioritize and present opportunities for applying AWO’s, GB/BB projects and other LEAN principles to our supply chain and customer deliverables.

Develop, plan and execute the plans as selected by the business leaders.

Train all team members (and other selected individuals) in LEAN principles and mechanisms to be LEAN and preferred by customers.

Document procedures/routines, training, team results/best practices and the like.

Coaches business team members in the practical application of the Lean tools to drive significant business impact.

Leads and manages the current state value stream process.

Develops and implements future state value stream processes.

[…]

Responsible for planning and assisting in the execution of various Lean transformation events targeted towards improving the business’s performance on safety, quality, delivery, and cost.

Focuses on business performance that constantly strives to eliminate waste, improve customer satisfaction, on-time delivery, reduce operating costs and inventory via the use of Lean tools and continuous improvement methodologies.

[…]

Acts as change agent in challenging existing approaches and performance.

Whew. With all of that, here is my question: What is the line leadership expected to do? In other words, what is left for them to do? And what, exactly, are they supposed to be doing (and how) during all of this flurry of activity?

While all of the “change agent” examples outlined in Lean Thinking (which, in turn, provides context for Learning to See), are line leaders, all too often the role of “change agent” is delegated to a staff member such as the above.

I believe it is entirely possible for a line-leader change agent to also be the “sensei” – Michael Balle’s The Lean Manager shows a fictional scenario that does just that.

But if your “sensei” is a staff technical professional, or an external consultant, the “change agent” function is separate and distinct, or should be.

Which leads me to the first question that is never asked:

Why Are You Doing This At All?

That question can be a pretty confrontational. But it is a question that often goes unasked. 

This is especially true where “getting lean” is an initiative delegated to staff specialists, and not directly connected to achieving the strategic objectives of the business. In these cases, “Lean” is expressed as a “set of tools” for reducing costs.

I do not believe that “creating a crisis” is constructive, simply because when motivated by fear people tend to (1) panic and lose perspective and (2) tend to apply habitual responses, not creative ones. If there are high stakes at risk, creativity is not what you should expect.

On the other hand, a narrow and specific challenge that is set as Step Zero helps focus people’s attention and gives them permission not to address every problem all at once (which avoids paralysis and gridlock).

So, if I were to edit that list of steps, I’d change “Create a crisis” to “Issue a challenge to focus the effort” and move it to #1 or maybe #2 on the list. The “Find a sensei” then becomes a countermeasure for the obstacle of “We need AND WANT to do this, but don’t have enough experience.” (That assumption, in turn, implies a driving need to learn doesn’t it?)

These are appropriate roles for the “change agent” – and they are things that can only be effectively done from a position of authority.

Which brings us to back to Learning to See.

Beyond “Value-Added”

Someone, a long time ago, proposed that we categorize activities as “value-added” or “non-value-added.”

We say that a “value-added step” is “something the customer is willing to pay for.” A “non-value-added step” is anything else. Some non-value-added steps are necessary to advance the work or support the business structure.

While this analysis is fundamentally correct at the operational level, and works to get a general sense of what it possible, this approach can start us off on a journey to “identify and eliminate waste” from the process. (Not to mention non-productive debates about whether a particular activity is “value added” or not.)

Right away we are limited. The only way to grow the business using this approach is to use the newly freed up capacity to do something you aren’t doing now. But what?

If that decision hasn’t been made as a core part of the challenge, the leaders are often left wondering when the “lean initiative” will actually begin to pay – because they didn’t answer the “Why must we do this?” question from the beginning.

Without that challenging business imperative, the way people typically try to justify the effort is to:

  • Analyze the process.
  • Try to quantify the waste that is seen. This would be things like inventory, walking distance, scrap, etc. that are easily measurable. More sophisticated models would try to assign value to things like floor space.
  • Add up the “proposed savings”
  • Determine a return on the investment, and proceed if it is worth it.

The idea, then, would be to deliver those savings quickly with some kind of rapid improvement process.

This fundamental approach can be (and is) taken at all levels of the organization. I have seen large-scale efforts run by a team of consultants doing a rapid implementation of an entire factory over a timespan of a few weeks.

I have also seen that same factory six months later, and aside from the lines that were painted on the floor and the general layout changes, there was no other sign the effort had ever been undertaken. In this case, no matter how compelling the ROI, they didn’t get anywhere near it.

One of the tools commonly (ab)used for this process is value stream mapping.

This approach is SO common that if you search for presentations and training materials for value stream mapping on the web, you will find that nearly all of them show describe this process:

  • Map your current state map.
  • Identify sources of waste and other opportunities on the current state map.
  • Depict those opportunities with “kaizen bursts” to show the effort you are going to make.
  • Based on what opportunities you have identified, and your proposed kaizen bursts, develop the future state map to show what it will look like.
  • Develop the new performance metrics for the future state.
  • Viola – make the case to go for it.

Now – to my readers – think for a minute. Where are the “kaizen bursts” in Learning to See? They are on the current state map, right?

Nope.

Here is the current state map on page 32:

image

 

If, on the other hand, I were to ask “What value do we wish we could create for our customers that, today, we cannot?” I open myself up to a host of possibilities, including creating a new value stream that currently doesn’t exist at all – using freed up resources, at essentially zero net cost (or at least heavily subsidizing the new effort).

Now I ask “What must I do to make these resources available to me?”

In the “find and eliminate waste” model, the staff-change agents are often responsible for the “lean plan.” Like the job description above, they are charged with convincing the leaders (who hired them!) that this all makes business sense.

A Manual for How to Meet a Challenge

In “Part III: What Makes a Value Stream Lean” (the green tab) there is a strong hint of the original intent in the second paragraph:

To reduce that overly long lead time from raw material to finished goods, you need to do more than just try to eliminate obvious waste.

This statement implies that the value stream mapper is dissatisfied with the current lead time, and has a compelling need to change it.

What you are looking for in the Future State is how must the process operate to get to the lead time reduction you must achieve.

For example, given a target lead time and a takt time, I can calculate the maximum amount of work-in-process inventory I can have and still be able to hit that objective.

I can look at where I must put my pacemaker process to meet the customer’s expectations for delivery.

Based on that, I can look at the turns I must create in the pull system that feeds it.

Based on that, I can calculate the maximum lot sizes I can have; which in turn, drives my targets for changeovers.

As I iterate through future state designs, I am evaluating the performance I am achieving vs. the performance I must achieve.

What is stopping me from making it work?

What must I change?

If something is too hard to change, what can I adjust elsewhere to get the same effect?

In the end, I have a value stream architecture that, if I can solve a set of specific problems, will meet the business need I started with.

This is my view on the fundamental difference between creating a generic “crisis” vs. stating a compelling performance requirement.

The process outlined in the book is to develop the future state, and then identify what is stopping you from getting there.

Of the eight KEY QUESTIONS FOR THE FUTURE STATE that are outlined in page 58, What process improvements will be necessary for the value stream to flow as your future state design specifies?” is question #8.

It is the last thing you consider.

The kaizen bursts are not “What can we do?”

They are “What must we do?”

The first thing you consider is “What is the requirement?”

“What is the takt time?”

In other words, how must this process perform?

Here is a clip of the future state map from page 78:

image

The “bursts” are not “opportunities” but rather, they represent the things we have to fix in order to achieve the future state.

In Toyota Kata terms, they represent the obstacles in the way of achieving the target condition, just at a higher level.

What this is saying is “To achieve the future state we need to rearrange the work flow AND:

  • Get the stamping changeovers down to 10 minutes or better.
  • Get the weld changeovers to where we can do them within the takt.
  • Get the welder uptime to 100%.
  • Get the work content for weld + assembly down to under 168 seconds.”

These are the obstacles to achieving the performance we want from the future state value steam.

Notice that the stamping press only has an uptime of 85% on the current state map. There isn’t a corresponding kaizen burst for that – because, right now, it isn’t in the way of getting where we need to go. It might be an issue in the future, but it isn’t right now.

But if we were just “looking for waste” we might not see it that way, and spend a ton of time and resources fixing a problem that is actually not a problem at the moment.

Putting This Together

Thus, I suspect that Learning to See, like many books in the continuous improvement category, was intended for value stream leaders – managers who are responsible for delivering business results.

In my experience, however, most of the actual users have been staff practitioners. Perhaps I should use the 2nd person here, because I suspect the vast majority of the people reading this are members of that group.

You are a staff practitioner if you are responsible for “driving improvement” (or a similar term) in processes you are not actually responsible for executing on a daily basis. You are “internal consultants” to line management.

Staff practitioners are members of kaizen promotion offices. They are “workshop leaders.” They are “continuous improvement managers.” The more senior ones operate at the VP and Director level of medium and large size companies.

No matter what level of the organization, you are kindred spirits, for most of my post-military / pre-consulting career has been in this role.

The people who actually read and study books like Learning to See are staff practitioners.

This creates a bit of a problem, because Learning to See is very clear that the responsible manager should be the one actually building the value stream map. But often, that task is delegated to the staff practitioner.

“Map this value stream, and please present your findings and recommendations.” If you have gotten a request or direction like that, you know what I am talking about. Been there, done that.

In my personal experience, although it gave me valuable experience studying process flows, I can honestly say that relatively few of those proposed “Future States” were actually put into practice.

The one that I vividly remember that was put into practice happened because, though I was a kaizen promotion office staffer, I had start-up direct responsibility for getting the process working, including de-facto direct reports. (That is a different story titled “How I got really good at operating a fork lift”)

Into 2013

Today we see Toyota Kata quickly gaining popularity. The Lean Bazaar is responding, and “coaching” topics are quickly being added to conference topics and consulting portfolios.

I welcome this because it is calling attention to the critical people development aspect that distinguishes the Toyota Management System from the vast majority of interpretations of “lean” out there.

But make no mistake, it is easy to fall into the tools trap, and the Lean Bazaar is making it easier by the way it positions its products.

Just as value stream mapping isn’t about the maps, establishing an improvement culture isn’t about the improvement boards, or the Kata Kwestions.

It is about establishing a pervasive drive to learn. In that “lean culture,” we use the actual process as a laboratory to develop people’s improvement skills. We know that if we do the right job teaching and practicing those skills, the right people will do the right things for the process to get better every day. Which is exactly what the title of Learning to See says.

Steve Spear on Creative Experimentation

On Monday MIT hosted a webinar with Steven Spear on the topic of “Creative Experimentation.”

A key theme woven throughout Spear’s work is the world today is orders of magnitude more complex than it was even 10 or 15 years ago. Where, in the past, it was feasible for a single person or small group to oversee every aspect of a system, today that simply isn’t possible except in trivial cases. Where, in 1965 it was possible for one person to understand every detail of how an automobile worked, today it is not.

My interpretation goes something like this:

Systems are composed of nodes, each acting on inputs and triggering outputs. In the past, most systems were largely linear. The output of upstream nodes was the input of those immediately downstream. You can see this in the Ford Mustang example that Spear discusses in the webinar.

Today nodes are far more interconnected. Cause and effect is not clear. There are feed-back and feed-forward connections and loop-backs. Interactions between processes impact the results as much as the processes themselves.

Traditional management still tries to manage what is inside the nodes. Performance, and problems, come from the interconnections between nodes more than from within them.

The other key point is that traditional management seeks to first define, then develop a system with the goal of eventually reaching a steady state. Today, though, the steady state simply does not exist.

Product development cycles are quickening. Before one product is stable, the next one is launched. There is no plateau anymore in most industries.

From my notes – “The right answer is not the answer for very long. It changes continuously.”

Therefore, it is vital that organizations be able to handle rapid shifts quickly.

With that, here is the recorded webinar.

(Edit: The original flies have been deleted from the MIT server.)

A couple of things struck me as I participated in this.

Acknowledging that Spear has a bias here (as do I), the fact that Toyota’s inherent structure and management system is set up to deal with the world this way is probably one of the greatest advantages ever created by happenstance.

I say that because I don’t believe Toyota ever set out to design a system to manage complexity. It just emerged from necessity.

We have an advantage of being able to study it and try to grasp how it works, but we won’t be able to replicate it by decomposing its pieces and putting it back together.

Like all complex systems, this one works because of the connections, and those connections are ever changing and adapting. You can’t take a snapshot and say “this is it” any more than you can create a static neural net and say you have a brain.

Local Capability

One thing that emerges as critical is developing a local capability for this creative experimentation.

I think, what Spear calls “creative experimentation” is not that different from what Rother calls the “improvement kata.” Rother brings more structure to the process, but they are describing essentially the same thing.

Why is local capability critical? Processes today are too complex to have a single point of influence. One small team cannot see the entire picture. Neither can that small team go from node to node and fix everything. (This is the model that is used in operations that have dedicated staff improvement specialists, and this is why improvements plateau.)

The only way to respond as quickly as change is happening is to have the response system embedded throughout the network.

How do you develop local capability? That is the crux of the problem in most organizations. I was in an online coaching session on Tuesday discussing a similar problem. But, in reality, you develop the capability the way you develop any skill: practice. And this brings us back to the key point in Kata.

Practice goes no good unless you are striving against an ideal standard. It is, therefore, crucial to have a standardized problem solving approach that people are trying to master.

To be clear, after they have mastered it, they earn a license to push the boundaries a bit. But I am referring to true mastery here, not simple proficiency. My advice is  to focus on establishing the standard. That is difficult enough.

An Example: Decoding Mary – Find the Bright Spots

Spear’s story of “Decoding Mary” where the re-admission rate of patients to a hospital directly correlated with the particular nurse handled their transfer reminded me of Heath & Heath’s stories from Switch. One of the nine levers for change that they cite is “find the bright spots.”

In this case the creative experimentation was the process of trying to figure out exactly what Mary did differently so it could be codified and replicated for a more consistent result independent of who did it.

The key, in both of these cases, is to find success and study it, trying to capture what is different – and capture it in a way that can be easily replicated. That is exactly what happened here.

A lot of organizations do this backwards. They study what (or who) is not performing to determine what is wrong.

Sometimes it is far easier to try to extract the essence what works. Where are your bright spots for superb quality? Does one shift, or one crew, perform better than the others? Do you even know? It took some real digging to reveal that “Mary” was even the correlating factor here.

Continuous Improvement Means Continuous Change

Since “continuous improvement” really means “continuously improving the capability of your people,” now perhaps we have “to do what.” I have said (and still say) that the “what” is problem solving.

What you get for that, though, is a deep capability to deal with accelerating change at an accelerating rate without losing your orientation or balance.

It is the means to allow the pieces of the organization to continue to operate in harmony while everything is changing. That brings us back to another dilemma: What is the ROI on learning to become very, very good? You don’t know what the future is going to throw at you, only that you need the capability to deal with it at an ever quicker pace.

But none of this works unless you make a concerted effort to get good at it.

Here is the original link to the MIT page with the video, and a download link for PDFs of the slides:

http://sdm.mit.edu/news/news_articles/webinar_010912/webinar-spear-complex-operating-systems.html

Mike Rother: Time to Retire the Wedge

Note – this post was written pretty much simultaneously with a post on the lean.org forum.

Mike Rother has put up a compelling presentation that highlights a long-standing misunderstanding about the purpose of “standards.”

Some time ago, a (well-meaning) author or consultant constructed a graphic that shows the PDCA wheel rolling up the incline of improvement. There is a wedge labeled “Standards” shoved as a chock block under the wheel to keep it from rolling back. That graphic has been copied many times over the years, and shows up in nearly every presentation about PDCA or standard work.

The implication – at least as interpreted by most – is that a process is changed for the better, a new standard is created, and people are expected to follow the standard to “hold the gains” while they work on rolling the PDCA wheel up to the next level on the ramp.

Slide 6 (taken from the book Toyota Kata) shows the underlying assumptions that are implied by this approach, especially when it doesn’t work.

There are some interesting assumptions embedded in the “wedge thinking.”

The first one is that “the standard can be ‘held’ by the people doing the work.

That, in turn, means that if when things start to deteriorate, the workers and first line leaders are somehow responsible for the “slippage” or “not supporting the changes.”

With this attitude, we hear things like “Our workers aren’t disciplined enough” or “How do I make them follow the standard?” The logical countermeasures are those associated with compliance – audits focused on compliance, and sometimes even escalating punitive actions.

Back in my early days, I had a shop floor team member call us on it quite well: “How can you expect us to hold some kind of standard work if the parts don’t fit?” (or aren’t here, or the tools don’t work, or jigs are misaligned, or the machine isn’t running right, or someone is absent, or we are being told to hurry and just get stuff out the door?)

This is the approach of control. The standard is fixed until we decide to change it.

Taiichi Ohno didn’t teach it this way.

Neither did Deming or Juran. Neither did Goldratt. Nor does Six Sigma, TQM, TPM.

Indeed, if we want creativity to be focused on improvements, we have to look up the incline, not back.

We are putting “standards” on the wrong side of the wheel. Rother’s presentation gets it right – the “standards” are the target – what we are striving to achieve.

The purpose of standards is to compare what we actually do against what we wanted to do so we know when they are different and so we have some idea what stopped us from getting there.

Then we have to swarm the problem, and remove the barrier. Try it again, and learn what stops us the next time.

The old model shows “standards” as a countermeasure to prevent backsliding, when in reality, standards are a test to see if our true countermeasures are working.

I believe this model of “standards” as something for compliance is a cancer that is holding us back in our quest to establish a new level of understanding around what “continuous improvement” really means.

It is time to actively refute the model.

If you own your corporate training materials, find that slide (it is in there somewhere) and change it.

If you see this model in a presentation, challenge it. Ask what should happen if something gets in the way of meeting this “standard.”

“What, exactly do you expect the team member to do?”  That sparks an interesting conversation which reveals quite a bit.

How Do You Deal With Marshmallows?

Yesterday, Kris left great comment with a compelling link to a TED presentation by Tom Wujec, a fellow at Autodesk.

Back in June, I commented on Steve Spear’s article “Why C-Level Executives Don’t Engage in Lean Initiatives.” In that commentary, Spear contends that business leaders are simply not taught the skills and mindset that drives continuous improvement in an organization. They are taught to decide rather than how to experiment and learn. Indeed, they are taught to analyze and minimize risk to arrive at the one best solution.

Tom Wujec observes exactly the same thing. As various groups are trying to build the tallest structure to support their marshmallow, they consistently get different results:

So there are a number of people who have a lot more “uh-oh” moments than others, and among the worst are recent graduates of business school.

[…]

And of course there are teams that have a lot more “ta-da” structures, and, among the best, are recent graduates of kindergarten.[…] And it’s pretty amazing.

[…] not only do they produce the tallest structures,but they’re the most interesting structures of them all.

What is really interesting (to me) are the skills and mindsets that are behind each of these groups’ performance.

First, the architects and engineers. Of course they build the tallest structures. That is their profession. They know how to do this, they have done it many thousands of times in their careers. They have practiced. Their success is not because they are discovering anything, rather, they are applying what they already know.

In your kaizen efforts, if you already know the solution, then just implement it! You are an architect or engineer.

BUT in more cases than we care to admit, we actually do not know the solution. We only know our opinion about what the solution should be. So, eliminating the architects and engineers – the people who already know the solution – we are left with populations of people who do not know the solution to the problem already. This means they can’t just decide and execute, they have to figure out the solution.

But decide and execute is what they are trained to do. So the CEOs and business school graduates take a single iteration. They make a plan, execute it, and fully expect it to work. They actually test the design as the last step, just as the deadline runs out.

The little kids, though, don’t do that.

First, they keep their eye on the target objective from the very beginning.

Think about the difference between these two problem statements:

  • Build the tallest tower you can, and put a marshmallow on top.

and

  • Support the marshmallow as far off the table as you can.

In the first statement, you start with the tower – as the adults do. They are focused on the solution, the countermeasure.

But the kids start with the marshmallow. The objective is to hold the marshmallow off the table. So get it off the table as quick as you can, and try to hold it up there. See the difference?

More importantly, though, is that the kids know they do not know what the answer is. So they try something fast. And fail. And try something else. And fail. Or maybe they don’t fail… then they try something better, moving from a working solution and trying to improve it. And step by step they learn how to design a tower that will solve the problem.

Why? Simply because, at that age, we adults have not yet taught the kids that they are supposed to know, and that they should be ashamed if they do not. Kids learn that later.

Where the adults are focused on finding the right answer, the kids are focused on holding up a marshmallow.

Where the adults are trying to show how smart they are, the kids are working hard to learn something they do not know.

Third – look what happened when Wujac raised the stakes and attached a “big bonus” to winning?

The success rate went to zero. Why? He introduced intramural competition and people were now trying to build the best tower in one try rather than one which simply solved the problem.

Now – in the end, who has advanced their learning the most?

The teams that make one big attempt that either works, or doesn’t work?

Or the team that makes a dozen attempts that work, or don’t work?

When we set up kaizen events, how do we organize them?

One big attempt, or dozens of small ones?

Which one is more conducive to learning? Answer: Which one has more opportunities for failure?

Keep your eye on the marshmallow  – your target objective.

Last thought… If you think you know, you likely don’t. Learning comes from consciously applied ignorance.


Edited 2 August 2016 to fix dead link. Thanks Craig.

“Opportunities” vs “Problems”

Over the decades, I have observed that it is quite common for organizational leaders to try to use the word “opportunity” when talking about a problem.

I can understand the desire to do this – we typically think of “problems” as something to do with people.

But I find the emphamistic language… problematic.

 

 

Mr. Opportunity

 

There is a Honda marketing campaign in the USA that features a cartoon character named “Mr. Opportunity.” His tag-line is “I’m Mr. Opportunity, and I’m knocking.” The opportunity is an invitation to take advantage of discounted prices for Honda cars.

Words mean things.

An opportunity is something that I may, or may not, decide to pursue.

But in lean thinking, no problem can go unaddressed.

Rather than a friendly cartoon character knocking on your door, a problem has kicked your door in and is standing in your living room. It must be dealt with, and dealt with quickly.

It has to be contained, pushed back, and finally resolved to keep it from getting back in.

IF the process for doing these things is carried out correctly, there are opportunities for the organization to learn along the way. But in the vast majority of cases, the only way those opportunites get exploited is if the leaders insist on hearing what was learned. So even those “opportunities” shift to imperatives.

Friendly euphemism that soften the urgency do not help us. If we are to have a true problem solving culture, we have to be willing to call things what they actually are.

Knowing vs. Knowing How To Learn

On the way to the airport a few days ago a couple of thoughts occurred to me that I wanted to toss out there and see how you all responded. This is one of them.

What separates an expert from a master? Actually I need to ask in more prejudicial terms. Some people who are truly experts are also “stuck” in that they try to fit new things they encounter in to an analogy within their (vast) experience. When they find it, they apply the analogy and often come up with a pretty good solution. But they can have problems relating when the encounter something that doesn’t compare with anything they have seen before.

As an example, the classic elements of standard work are described as

  • a repeating work sequence
  • balanced to a takt time
  • standard in-process stock

And, indeed, these things are the elements of standard work when there is a repeating work sequence and when there is a takt time.

Some experts at applying standard work, however, have a hard time seeing application outside of this scope. They know work needs to be standardized, but they continue to try to shoe horn what they see into this model.

Another, more general, lean manufacturing model is the notion that this is about manufacturing, or that it “doesn’t apply” to true job-shops or non-repetitive environments. But this, too, is just a limitation of an “analogy” model. It is the analogy that breaks down, not the concept.

In the analogy model, we try to educate by providing more analogies, more examples of different applications in order to expand the base for comparison.

And, to be honest, this works to a degree. Some people get it, others simply don’t want to expand their analogy base. They are the ones who say “This (model) does not apply to (whatever is their current paradigm)     .

Indeed, people who are tightly holding the view that kaizen events led by trained specialists are the only way to drive improvement can easily be blind to the possibility that an organization that is successfully running daily kaizen is operating at a fundamentally different level. I have seen that as well. And I have seen the same excuses made to explain away the difference in performance. “It isn’t different;”  “it doesn’t scale;”  “it isn’t repeatable.” All of this is defending a mental model – a paradigm – an analogy.

On the other hand, I want to contend here that a true master is not one who has mastered a process, but rather one who has mastered the process of learning about a process.

At an organizational level, true continuous improvement starts to engage when “process” and “standard” become baselines to gain higher understanding. Rather than trying to audit and enforce compliance, they are genuinely curious about the reason why a process is not being carried out as it should. This thinking requires far more work because it is empowering – it simply does not allow playing victim to “they won’t.” It puts the spotlight right back on what can (or should) be learned from the experience.

Put another way, the “expert” knows.

The “master” knows that there is much to learn.