Notes from the 2020 TWI Summit – Part 1

Photo by Michele Butcher of Lean Frontiers

Last week (February 17-20) I attended (and presented at) the TWI and Toyota Kata summits put on by my friends at Lean Frontiers. As always, I took a few notes and I would like to share some of those notes and thoughts with you here.

To be clear, what follows are my impressions and thoughts that were sparked by some of the presentations. I am not trying to be a reporter here, just catch my own reflections.

Martha Purrier

Martha Purrier, a Director of Nursing at Virginia Mason Medical Center in Seattle, talked about “auditing standard work,” though in reality I think her process was more about auditing the outcomes of standard work. More about that in a bit.

My interpretation of the problem: Traditional “audits” are infrequent, and tend to be time consuming for those doing them because there is an attempt to make them comprehensive.

Infrequent checks are not particularly effective at preventing drift from the standard. Instead they tend to find large gaps that need to be corrected. This can easily turn into a game of “gotcha” rather than a process of building habits. What we want to do is build habits.

Habits are built in small steps, each reinforced until it is anchored.

Make it Easy: Short and Simple Checklists

Martha’s organization created short checklists of critical “Key Points” (from TWI Job Instruction) that were critical to the standard they wanted to maintain.

Audit Check Card. Photo from Martha Purrier’s Presentation

As you can see, this is a quick and simple check to see if the contents and organization of a supply cart meets the standard.

But what really caught my attention was how they are triggering the audits.

The Key: Reliable Prompt for Action

This is a pretty typical work task board. There is a row for each person or team. In this case the columns look like they represent days, but they could just as easily represent blocks of time during the day, depending on how granular you want your tracking to be. At some point these start to become a heijunka box, which serves the same purpose.

You can see the yellow bordered audit cards on there. Martha said that when a task is complete, it is moved to a “Done” column that is out of frame to the right.

Here is what is awesome about this: It gives you the ability to “pull” checks according to need.

Do you have a new process that you want multiple people to check during the course of the week? Then put the check card for that task in multiple rows at staggered times.

Do you want to go broad over a group of related checks? Then put different checks on the board.

Who should do the checks? Whoever you assign it to. Totally flexible. Do you want to trigger a self-audit? Then assign the card to the person who does the task being checked, with the expectation that they self-correct.

Do you want to bring a new supervisor up to speed quickly? Assign multiple audits to her, then assign follow-up audits to someone else.

Making it Better: Follow-up Breakdowns

If we don’t want audits to simply become lists of stuff to fix, there has to be some process of following up on why something needed correction.

Martha’s organization introduced a simple check-form that lists “Barriers to Standard Work – (check all that apply)” and provides space to list countermeasures taken.

The lists includes the usual suspects such as:

  • Can’t find it
  • No longer relevant
  • Not enough detail
  • etc.

but also some that are often unspoken even though they happen in real life:

  • Lack of enthusiasm to continue or improve
  • Mutiny
  • Relaxed after training – drift

If a large part of the organization is pushing back on something (mutiny), then the leadership needs to dig in deep and understand why. To continue in our TWI theme, this is a great time to dig into your Job Relations process.

Standard Work vs. “Standards”

In my past post, Troubleshooting by Defining Standards, I made a distinction between defining the outcome you are trying to achieve and, among other things, the way the work must be done to accomplish that outcome.

When I think of “standard work” I am generally looking for a specification of the steps that must be performed, the order for those steps, usually the timing (when, how long) as well as the result. In other words, the standard for the work, not just the outcome or result.

To verify or audit “standard work” I have to watch the work as it is actually being performed, not simply check whether the machine was cleaned to spec.

Now, to be clear, I LOVE this simple audit process. It is an awesome way to quickly follow-up and make sure that something was done, and that the patient or customer-facing results are what we intend. It is flexible in that it can quickly and fluidly be adjusted to what we must pay attention to today.

I realize I am quibbling over words here. And every organization is free to have its own meanings for jargon terms. But when I hear the team “standard work” I am looking for the actual work flow as well as the result. YMMV.

This post got long enough that I am going to let it stand on its own. More to follow.

How Do You Know They Know?

TWI Job Instruction is built around a four step process titled “How to Instruct.”

image

Steps 2 and 3 are the core of the process.

  • Present the Operation
  • Try Out Performance

I want to discuss Step 3: Try Out Performance

Teaching Back as Learning

All too often I see “training” that looks like this:

  • Bring the team members into a room.
  • Read through the new procedure – or maybe even show some PowerPoints of the procedure.
  • Have them sign something that says they acknowledge they have been “trained.”

This places the burden of understanding upon the listener.

The TWI model reverses this paradigm with the mantra at the bottom of the pocket card which, though they vary from version to version, is some form of: If the student hasn’t learned, the teacher hasn’t taught.

Having the learner teach back to the instructor does two things:

  1. The learner has to understand it better to be able to explain it.
  2. It provides a verification check that the instruction has been effective.

Point two is important here. Instruction is a hypothesis: “If I teach these steps, in this way, my learner will be able to perform the process.”

Having them teach back is the testable outcome of this hypothesis. If the the learner struggles, then the instructor must re-instruct. But not simply by rewinding the script and playing it again… we know that didn’t work. Instead the instructor now has to get curious about which points are confusing the learner and why, and correct his instruction.

But that’s not what I came here to discuss. TWI is just a lead-in.

Learning to See – by Practicing

An operations manager who is learning fast was challenging my insistence on having a visual status board that showed the real-time location of product on the line.

In the same breath, he was saying that he wanted the leads and the supervisor to be able to “walk the trapline” and do better seeing issues coming before a train wreck. (Empty positions, overproduction, etc.)

My response was “Having them update the magnets on that board every time something moves forces them to practice seeing what is where.”

In other words, by making them teach you where things are, and demonstrate their knowledge, they have to learn how to see that bigger picture.

“That’s the best explanation I have ever heard.”

The operations manager can walk the line and see the status himself. He doesn’t need the board. In fact, he could see even better if he went up the mezzanine overlooking the line. It’s all there.

But the board isn’t for his benefit. It is a learning tool. It is structure for the leads and supervisors to have a joint conversation, facing the board instead of each other, and reach agreement about what is where.

It gives them a clear indication if they need to escalate a problem, and a way to be able to converse about when and how they might recover (or not).

In other words, it is “Grasp the Current Condition” continuously, in real time. This lets them compare the current condition with the target condition – the standard depicted on the board.

By seeing gaps quickly, they have a better chance at seeing what obstacle or problem prevented them from operating to the target.

That, in turn, gives the manager an opportunity – in invitation – to shape the conversation into one about improvement.

Back to Job Instruction

This is exactly the same process structure as having the learner demonstrate performance. It is a check, right after the operation (present the operation) was performed to see how well it worked.

Fine Grained Observation

All of this is about moving observations, evaluations, checks, verifications away from batching them at the end of a huge block of work and embedding them into one-by-one flow. It builds Ohno’s “chalk circle” into the work itself.

If You Aren’t Being Heard, Then Listen

I was sitting in on a conversation between a Continuous Improvement Manager and the Operations Manager the other day.

The Operations Manager was asking for help developing good leader standard work.

The C.I. manager was responding that she had already developed it for the Value Stream Manager, the Supervisor.

The Operations Manager said he thought right now, they needed to focus on the Team Leads, the first line of leadership.

The C.I. manager reiterated that she had already prepared standard work for the Value Stream Manager and the Supervisor.

The Operations Manager reiterated that he wanted, right now, to focus on the Team Leads.

This went back and forth three or four times, and the Operations Manager moved on to something else.

The C.I. Manager seemed frustrated and even a little angry.

My Working Hypothesis

The C.I. manager was frustrated because the work she had already done had not been implemented or acknowledged.

The Operations Manager was frustrated because his immediate need was not being acknowledged.

So they were each reiterating, again, what they had said before, neither of them acknowledging what the other was trying to say.

Being Heard as a Change Agent

When you say something, and the other person responds by reiterating what they have already said, this is a Big Red Flag for you. They are not going to hear anything you say until they feel you have heard them.

The cool part is that either of these parties can break the cycle of repetition by shifting into listening mode. I am going to take this from the perspective of the C.I. Manager / change agent since most of you reading this are more likely to be in that position.

Book cover: Never Split the DifferenceThere are lots of classes and materials out there about “active listening” but I really like a simple techniques that Chris Voss shares in his awesome book Never Split the Difference.*

At least they seem simple. But they require a lot of deliberate practice to master as they require breaking long standing unconscious habits. At least I know I’m still working on it.

The Goal: Hear “That’s Right”

The first step to listening is to listen!

Is the other person simply reiterating what they have said before in response to your message? Are you even aware of that? (or are you waiting them to stop talking so you can reiterate your message?) Take responsibility for breaking the cycle. Pay attention to their body language. Try to read how they are feeling right now.

Then test your hypothesis.

Instead of reiterating your message, repeat theirs back to them. Even better if you acknowledge the emotions behind their message.

“It sounds like you are really concerned that the leads don’t know what to do.”

Critical: In the words of Chris Voss, this requires that “late night FM DJ voice.”

NO sarcasm. NO implied judgement. You must come from a position of being curious about what they are trying to communicate, and what they are feeling.

You are trying to learn. You are not trying to make them wrong. You are not trying to make a point. You are not trying to be right.

If you are trying to do any of those things, you are not listening. You are, instead, trying to collect ammunition for your next salvo.

You will get one of two responses:

  • The other person will correct you.
  • The other person will give you some version of “Yeah, that’s right.” Those are the magic words you are trying to hear.

Let’s parse that sentence.

“It sounds like…”  (or “It seems like…”). You are not telling them what they are saying. You are telling them what you are hearing and sensing.

This invites correction. “No, that’s not it.” or “No, that’s not what I’m saying.”

They may be frustrated. That is why you must remain the calming influence.

(By the way – this is MUCH easier if you don’t have a stake in the conversation, and the process of being listened to really helps the other person clarify their own position. That is a good place to practice before you are in a high-stakes situation.)

“… you are really concerned…”

Acknowledge how you sense they are feeling. Again, this is inviting correction, clarification or agreement. In either case, you are getting more information.

“… that the leads don’t know what to do.”

This part of the sentence communicates your understanding of what you think is causing the emotion in the other person. Again, this is just an acknowledgment. It doesn’t mean that you agree that this issue should trigger this emotion, you are just acknowledging that it does.

If you don’t get “that’s right” then it is time to humbly and sincerely ask for correction. You have to do so in a way that makes it clear you really care about understanding. (“Seek first to understand.”)

Ideally the other person will attempt to clarify what they are trying to say. Cycle through this until they agree that what you are saying back is what they are trying to convey to you.

Trap: “You’re Right”

Voss points out a trap in this process: The critical difference between “that’s right” and “you’re right.”

First, if you hear “you’re right” that is an indication that the other person perceives you are trying to make your case vs. hearing them. Were you adding to the information? Were you passing judgement?

Next – In this context, “You’re right” often translates as “I’m tired of trying to talk about this.” There isn’t agreement yet. “You’re right” is about you. “That’s right” is about what you were saying. Very different things.

Which leads us to:

Don’t let “being right” about something get in the way of getting what you want or need.

The C.I. manager was right that she had prepared leader standard work for the value stream manager and the supervisor. And she was right that it hadn’t been acted upon.

But by sticking to her guns about that, the Operations Manager was left with the impression that she was refusing to help develop standard work for the team leaders, so he gave up on the conversation.

Here is what happens. Her frustration comes through. His brain (all of our brains) contains “mirror neurons” that invoke in him the emotions he is seeing across the table, which elevates his frustration without him even knowing it.

This is why that calming demeanor is so critical. If the other person picks up sarcasm, negativity, dismissiveness in your voice or body language, that will be reflected right back at you, and amplify everything the wrong way.

After (AFTER!!) getting an acknowledgment that he felt the main priority right now was the Team Leads, the C.I. manager might have created an opening –

State your facts: “I worked really hard on standard work for the value stream leader and supervisor.”

Own your own feelings: “I am feeling frustrated that none of that work was acted upon.” (Avoid victim language like “that makes me feel” or “you make me feel” statements.)

State what you need right now: “I’ll work on the standard work for the leads, but I would like to review the work I have already done and what happened with it so I can avoid the same situation with the leads. Can we do that?”

Finally…

There is no guarantee this works every time. But it works more often than escalating the emotion which probably never works.

_________________

*Why am I touting a book about negotiating? Because change agents must be able to reach agreements with others. And negotiating is a process of agreement creation. Chris Voss is a former FBI hostage negotiator. His job was to create agreements with terrorists, kidnappers, bank robbers. If his techniques work there, they probably work for a change agent in a company.

 

 

Creating Resistance As You Go (Don’t)

The role of “change agent” is actually a role of leadership.

Leading change is difficult work that involves changes in the norms, routines, working relationships, behavior within and between groups. It is required when a simple technical change either isn’t going to get the job done, or requires the above changes to work at all. Most (if not all!) of the “lean tools”* fall into the later: The process changes are straight forward, but making them work requires altering the habitual patterns of how people work together.

Before I dive into what works, I want to spend a little time on what doesn’t work.

The Bulldozer: Creating Resistance

Bulldozer climbing a mound of dirt.

A team had a challenge – the result they were striving to achieve – of getting a 2-3 week administrative workflow (that sometimes went longer) down to a consistent three days. Their target condition was a pretty good work flow that, by all accounts so far, could avoid a lot of delays (on the order of days and weeks).

The changes they proposed would eliminate a number of transfers from one department to another (which always means another queue). However it also calls for eliminating some long-standing work-arounds that involve filling out forms and passing them along by email. But now they have a new ERP system, and the intent has been that this work is done within that system.

Those forms are in another department’s process, and involve people who haven’t been involved (so far) with the work to date. (There are valid reasons for this, and yes, some of this could have been avoided by involving everyone from the beginning, but that isn’t the point of the story.)

A functional department manager set off a flurry of pushback through a series of emails that essentially said “This is the future” and exhorting people to get on board with the new process vs. defending the old one.

One of the tenants of an effective change agent is “Don’t work uphill” with the corollary of “Don’t create hills in front of you.” I call the opposite of this the bulldozer approach. Unfortunately, like the picture above, just trying to push things through tends to build up a mound of resistance in front of you.

What did we learn?

Rather than trying to engage the new idea as an experiment – “Let’s try this and see what we learn,” the change agent tried to use position power to push the idea through. He took an action, and had an (implied) expected result – that people would see the light and adopt the new process.. The actual result, though, was quite different than what was expected – they doubled down on their resistance.**

A scientific-thinking change agent (a.k.a “a leader”) is going to step back and assess. Why did I get the reaction I did? What triggered it? What are the values of this constituency that are being challenged? Most pushback comes from a perceived threat to something that is regarded as valuable.

Perhaps the current workflow solves a very real problem. Perhaps it is otherwise very useful for something I am not aware of. Or maybe there is some emotional stake attached to the status quo. There is likely a combination of all three, or other factors I haven’t mentioned.

When proposing a new idea there is an opportunity to become curious about what previously hidden (to us at least) obstacles have just been uncovered, step back and work on the next one.

Leadership is a series of experiments. Not everything will work. But everything is an opportunity for learning and adjusting or adapting the next step appropriately.

People who expect their position-power to carry them through often tend to assign blame to individuals as “resisting the change.” But if we carry a different assumption – that everyone is doing the best they can to do the best job they can – then we can reframe and possibly reinterpret the reaction we are getting.

What other interpretations could we assign to this pushback other than “They don’t want to?” How many of those interpretations can we think of?

What is your next step or experiment?

Each of those possible interpretations is a testable assumption. Now I can frame my next action, conversation, or intervention to test one or more of those assumptions. This requires me to go into curiosity mode, because I really don’t know if they are true or not.

Now I have a different conversation because I am seeking first to understand. I can test assumptions without threatening anyone. Listen. Don’t defend. Paraphrase back until you hear “That’s right” signaling agreement that you heard what they were saying. That doesn’t mean you agree, but that you heard. Until someone feels heard they aren’t going to be soaking in what you are trying to tell them, they are going to be setting up the next defense of their position.

There is VERY rarely a need to directly confront someone over a different interpretation of the facts.

Don’t be a bulldozer – it doesn’t work.

———–

*And Six Sigma tools, and Theory of Constraints tools, and TQM Tools, and the tools associated with pretty much any other “program” that falls under the umbrella of continuous improvement.

**Though, Dr. Phil’s coaching would probably be something along the lines of “What did you THINK would happen??” (Semi-apology to my non-US readers who may not have context for this attempt at cultural humor.)

If the student hasn’t learned…

… the teacher hasn’t taught.

Do you regard the structure of problem solving as dogma, or as an experiment with a predicted outcome?

If the learner struggles to master the structure, sometimes it is more valuable to find a different structure than to double down on what clearly isn’t giving the predicted result.

The Problem

Early this year I started work with a new client. They were trying to “implement A3,” and as I began to work with them, especially the new-in-the-position C.I. manager, I found they were struggling with what to write in the blocks of the “form.”

Of course there isn’t an A3 “form.” The A3 takes many configurations as the problem solver sets out to share the narrative with her coach. Nevertheless, beginners tend to find a format online, and work to put the right information in the various blocks.

In this case, my impression was that the blocks were getting in the way. “What should go in here?”  “What goes in the next block?” I didn’t really make a deliberate decision here, but I’ll tell you what I ended up doing:

What I Tried

First I tried the Toyota Kata format. He really liked that approach, but ultimately in this case we ran into the same kind of struggle. “Getting the structure right” seemed to be obscuring the bigger picture of the underlying thinking.

So I tried something more drastic: I let go of the format and the structure. Instead, let’s work on solving problems.

Like all organizations, there was no shortage of problems to practice on. So we just picked one.

Without the form, I had him map out the basic process steps. Then what happens, then what happens. What, exactly, is happening here. “The part is dropping off the conveyor.”

“OK, that’s the outcome, but what, exactly, is the mechanism that causes it to drop?” Describe what is happening. Draw it. Write it down. Show me.

After working to see process steps, we took on some pervasive quality issues.

“How is it even possible to produce this defect?” What are the steps involved to make a defective product? Yes – making defective product is a process, just like making a good product is a process. It is just a different process. What is actually happening here?

There were trials, experiments, measurements all with the goal of learning more, digging deeper, until the mechanism of the failure could be described. “This is what is happening.”

OK – how could that happen? Always forcing the discussion toward what is actually happening vs. what is not happening. If there was more than one possible mechanism to cause the problem, then “Based on the evidence we have, which of those can we rule out, and why?” Look at what’s left as a possible cause.

Of those, what trial can we run to see if we can rule that one out, or keep it in play.

At the end of a few of these, his language started to shift. He started speaking to others differently. He was learning to coach in different ways. He started asking different questions, boring in on the details with the intent of inquiry and dialog vs. “showing what I know.”

Oh – and he cracked a couple of chronic problems.

Then when the Corporate C.I. guy started insisting on “using A3” it was a pretty simple transition – it is just a way to describe what you know, what you do not know, and what steps you are taking to deepen your understanding because…

“The root cause of all problems is ignorance.”

– Steven Spear

What I Learned:

A core prerequisite to continuous improvement is good daily management of problem solving that applies solid scientific thinking to find the answers.

Once that thinking structure is in place, it can be expressed many ways, and A3 is but one of them. It isn’t the only one. As the level of scientific thinking deepens, the more the various tools and structures simply become fluid extensions to make it easier to express.

Sometimes I have found that if I try to force a particular format into place, I can end up having a container without any content.

Now… to be clear, there are many instances where the structure facilitates learning. It is just that in this particular case, the structure got in the way.

Asking whether learning is actually taking place, rather than trying to force a specific structure into place, may well be the difference between trying to teach by rote vs. staying focused on what the student is actually learning.

KataCon4–Notes along the way: Part 2

One of the things Menlo does (and I am sure they are not the only ones in their business who do) is create user personas – a biographical profile of a fictional person who represents a category of potential user for the software they are developing.

In Joy, Inc, Rich Sheridan describes the often contentious process of then forcing the customer to pick a single persona as the primary user – the persona whose needs will drive all decisions about optimization. That person goes in the center of their three rings.

image

They allow two personas in the 2nd ring, and three in the 3rd ring.

image

As they make design decisions about their code and user interface, they always defer to the innermost rings. That doesn’t mean that someone in a ring further out won’t have their needs met, but they will meet those needs in ways that don’t compromise the process for personas closer to the center.

Persona Mapping for KataCon

In the spirit of being a temporary Menlonian, I worked paired with Craig (over the phone, and in a shared Google Doc) and we developed a persona map for KataCon. Of course, had we done this correctly we would have gone back in time to the previous KataCon, gotten the profiles from the attendees lists, interviewed people, and put together profiles for “typical” people who attend.

Since we couldn’t do that, we pushed past our threshold of knowledge and combined experience with a bit of speculation. I did confirm some of our assumptions via a phone call to Dwayne at Lean Frontiers who graciously answered my questions as he was driving across Indiana.

This process forced us to actually think about who was in the audience, and why they were there – what they were seeking from their participation in the conference. As Rich and I talked about his message, and later on as Craig and I worked on our “Experiential Workshop” we used the names of these “people” rather than generic terms like “participant” or “audience.” I found that really focused our conversations.

Who Do You Optimize Your Process For?

This really begs the general question: Who is your process optimized for?

Is it optimized for the person doing the work?

For the customer’s specific experience? And if so, who is the “customer persona” you are optimizing THAT for? For example, for an ideal retail experience, a mom with two kids in tow would be a different customer than a single guy. You likely get both, but if you have do something that slightly compromises one in order to optimize the other… who is in the center ring?

Next up: Target Conditions as User Stories

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.

Toyota Kata and The Menlo Way

I have been telling everyone who will listen to read Rich Sheridan’s book Joy, Inc. ever since I came across and read it in the fall of 2015.

Fast forward to earlier this year when Lean Frontiers sent out their request for suggested keynote speakers for KataCon. I wrote to Mike Rother and asked him “Do you think we could get Rich Sheridan?”

Skip ahead a bit more, and I spent four days last week at Menlo Innovations in Ann Arbor – two days “in the chalk circle” paying close attention to the actual day-to-day work there, and two days working (pairing) with Rich Sheridan to work out the key beats for his KataCon keynote.

 

The “So What?” Test

Menlo is well known as a benchmark for a great working culture. But the question you may be asking (and, honestly I hope you ARE asking it) is “What does Menlo Innovations and agile software development have to do with Toyota Kata?”

If you visit Menlo (and I really hope you do!) here is what you won’t see:

  • Learner storyboards.
  • “5 Questions” coaching cycles.
  • Obstacle parking lots.
  • Experiment Records (PDCA Records)

In other words, you won’t see the explicit artifacts that characterize an organization using Toyota Kata to learn how to think about improvement scientifically. In that sense, Menlo isn’t a “Toyota Kata” benchmark.

OK… and?

You don’t see those things at Toyota either. You don’t go to Toyota to see “Toyota Kata.”

The Underlying Thinking Pattern

What you will see (and hear… if you pay attention) at Menlo Innovations is an underlying pattern of scientific thinking and safe problem solving in everything they do.

Let’s review what Toyota Kata is really all about.

Rather than re-writing something elegant here, I am going to quote from my part of an email exchange between Mike Rother, Rich Sheridan and me:

Going back to Mike’s original research premise, we knew that Toyota has this pretty awesome culture thing, but didn’t really understand the “secret sauce” of the exact structure of their interactions. Put another way, we saw and understood all of the artifacts, but copying the artifacts doesn’t copy the culture.

Mike’s research was really the first that dug deeper into the interactions that the artifacts support.

Once he extracted that “secret sauce” he then boiled off all of the other stuff, and what remained at the bottom of the pot was the Improvement Kata steps and the Coaching Kata steps.

In practice at Toyota, those things are deeply embedded in the artifacts. Sometimes they aren’t even spoken.

My informal hypothesis was that if I spent time paying attention to, not just the artifacts, but the way those artifacts guided interactions at Menlo, and then boiled off the other stuff, what would remain at the bottom of the Menlo pot would also be the Improvement Kata and Coaching Kata steps. And, though I didn’t do this formally, and yes, I had confirmation bias working here, I believe I can safely say “I have no evidence to contradict this hypothesis.”

For example:

In our conversation on Friday, Mike pushed back a bit on “just run the experiment,” [context clarification: Experiments to randomly try stuff, without a clear target condition rarely get you anywhere] but the reality I observed and heard was that “purpose” (challenge and direction) and “current condition” are deeply embedded in the day-to-day interactions, and “just run the experiment” is, indeed, working on a specific obstacle in the way of a target condition of some kind.

[…]

“What problem are you trying to solve?” is Menlo jargon that I overheard many times just listening to people talk.

Within Menlo, that term is contextual. Sometimes it is about the higher-level direction and challenge.

Sometimes it is about an intermediate target condition.

Sometimes it is about an immediate problem or obstacle.

As we say in Kata world, it is fractal. It is truly fractal at Menlo as well, to the point where the words don’t change at various levels.

The words DO change at various levels in Toyota Kata’s jargon, but we can’t get hung up on the terms, we have to look at the structure of problem solving.

Menlo’s co-founders already had this thinking pattern, and deliberately sought to embed it into the culture of the company they were starting. There wasn’t really any need to explicitly teach it because they weren’t trying to change the default behavior of an organization. New Menlonians learn the culture through the interviewing and on-boarding process and adopt very quickly because the very structure of the work environment drives the culture there.

In fact, spend any time there even just hanging out, and it is very difficult NOT to get pulled into The Menlo Way. Like everyone else, Rich and I were in the daily stand-up as pair-partners, reporting our work progress on his keynote.

image

What About Toyota Kata?

Menlo has had hundreds (thousands, actually) of visitors, and those who are “lean savvy” all ask if Menlo is “using lean” as their guideline. The answer is “no, we are just trying to solve problems.” While they have certainly incorporated most of the artifacts of “agile software production,” the purists push back that they aren’t “really doing it” because they didn’t copy those artifacts exactly. Nope. They used them as a baseline to solve Menlo’s problems.

When we see an awesome problem-solving culture, it is tempting to try to reverse engineer it by copying the physical mechanics, such as heijunka boxes (work authorization boards), kanban, “standard work” and the like.

But we have to dig down and look at the routines, the behavior that those artifacts and rituals support. When we do, we see the same patterns that Toyota Kata is intended to teach.

You need to begin with the thinking pattern. Use Toyota Kata to learn that.

As you do, take a look at your artifacts – the procedures, the policies, the control mechanics of your work. Reinforce the ones that are working to create the kind of culture you want. Challenge the ones that are getting in your way. Do both of those things as deliberate experiments toward a clear vision of the culture you want to create.

That is the benefit of studying companies like Menlo.

I hope to see you all at KataCon, hear what Rich has to say to our community, and establish a link between these two communities that have, up to now, been separate.

katasummit.com

Overproduction vs. Fast Improvement Cycles

A couple of weeks ago ago I posted the question “Are you overproducing improvements?” and compared a typical improvement “blitz” with a large monument machine that produces in large batches.

I’d like to dive a little deeper into some of the paradoxes and implications of 1:1 flow of anything, improvements included.

What is “overproduction” – really?

In the classic “7 wastes” context, overproduction is making something faster than your customer needs it. In practical terms, this means that the cycle time of the producing process is faster than the cycle time of the consuming process, and the producing process keeps making output after a queue has built up above a predetermined “stop point.”

If the cycle times are matched, then as an item is completed by the upstream process, it is consumed by the downstream process.

If the upstream process is cycling faster, then there must be an accumulation of WIP in the middle, and that accumulation must be dealt with. Further, those accumulated items are not yet verified as fit-for-use by the downstream process that uses them.

The way this applies to my “Big Improvement Machine” metaphor is that we are generating “improvement ideas” faster than we can test and incorporate them into the process.

“Small Changes” Doesn’t Mean “Slow Changes”

No matter how good your solution or idea, it is just an academic exercise until it is anchored as the an organizational norm. The rate limit on improvement is established by how quickly people can absorb changes to their daily, habitual routine.

Implementing and testing small changes one-by-one is generally faster than trying to make One Big Change all at once. When we do One Big Change, it is usually actually a lot of small changes.

I hear “we don’t have time to experiment,” but when I ask what really happens if a big change is made, what I hear almost every time is they had to spend considerable time getting things working. Why? Because no matter how well the Big Change was thought through, once you are actually trying it, the REAL problems will come up.

Key Point #1: Don’t waste time trying to develop paper solutions to every problem you can imagine. Instead, “go real” with enough of the new process to start revealing the real issues as quickly as possible.

In other words, the sooner you start actively learning vs. trying to design perfection, the quicker you’ll get something working.

Slow is Smooth, Smooth is Fast

Your other objective here is to develop the skill within the organization to test and anchor changes quickly, as a matter of routine. This will take time.

When we see a high-performance organization making rapid big changes, what we are typically seeing is making small changes even more rapidly. They have learned, through practice over time, how to do this. It isn’t reasonable to expect any organization to immediately know how to do this.

Key Point #2: If managers, or professional change agents (internal or external consultants, for example) are telling people exactly what to do, this learning is not taking place.

It is critical for the organization to develop this learning skill, and they are only going to do it if they can practice. Learning something new always involves doing it slowly, and poorly at first. If your internal or external consultants are serving you, their primary focus is on developing this basic competence. Their secondary focus is on getting the changes into place. This is the only approach that actually strengthens the organization’s capability.

The same is true for an operational manager who “gets” lean, but tries to just direct people to implement the perfect flow. It will work pretty well for a while. But think about how you (the operational manager) learned this stuff: Likely you learned it by making mistakes and figuring things out. If you don’t give your people a chance learn for themselves, you limit the organization in two ways:

  1. They will never be any better than you.
  2. They will wait to do what they are told, because that is what you are teaching them to do.

Think about what you want your people to be capable of doing without your help, and make sure you are giving them direction that requires them to practice doing those things. It will likely be different than telling them what they layout should look like.

Improve your Cycle Time for Change

Coming back to the original metaphor, if you want fast changes to last, you have to work speeding up the organization’s cycle time for testing improvement ideas. Part of this is going to involve making that activity an inherent and deliberate part of the daily work, not a special exception to daily work.

Part of that is going to be paying attention to how people are working on testing their ideas. The Improvement Kata and Coaching Kata are one way to learn how to deliberately structure this work so that learning takes place. Like any exponential curve, progress seems painfully slow at first. Don’t let that fool you. Be patient, do this right, and the organization will slingshot itself past where you would be with a liner approach.

Small changes, applied smoothly and continuously become big changes very quickly.

Are You Overproducing Improvements?

Imagine a factory with a large monument machine. It takes several days to set up. When it does run, it runs very fast, much faster than you can actually use its output. Therefore, you take the excess output and store it to use later. Actually, you don’t know how many items you need to make, so you make as many as you can while the machine is available to you.

image

Some of that excess output may prove to be less useful than you thought, but there is pressure to use it all anyway since it was so expensive to produce.

After a run making items for one process, you change it over to make items for a different process, and build up a queue of output there.

When all of the output is used, it all may or may not work the way you expected it to.

Most of us would see this as a classic case of “overproduction” – overwhelming the system with excess output that hasn’t been checked for quality, that isn’t needed right now, and might or might not be useful in the future. But it seemed like good efficiency to make it while we could.

Our lean thinking tells us we want to do a few things here. Ultimately, we want to work hard to break up the batches, and make the value flow more evenly to each of the customer processes, and ultimately to the end customers. The work we must do to keep things moving smoothly and evenly will pay off in both tangible and intangible ways.

One of the primary reasons we push hard for 1:1 flow in the lean world is to enable one-by-one confirmation.

We want to test each item of output to confirm that it actually performs as expected rather than making lots of them without knowing if they are any good.

How Do You Produce Improvements?

Now, imagine doing improvements this way. What would it look like?

A process would be scheduled to receive the rapid output of the Improvement Machine.

The Improvement Machine would be set up over a period of several days to produce improvements for the target process.

Once it was running, we would run the Improvement Machine very fast for a week or so. It would produce improvements faster than the target process can really absorb them.

At the end of the run, we might test the improvements as a batch. We might not test them at all, but rather report that they have been implemented with the assumption that they will work. We would also have excess improvements stored on a to-do list for future use.

Those excess improvements might, or might not, prove to be useful, but we would have huge pressure to implement them because they are on the list.

Once the machine was done producing improvements for one process, it would be set up to produce improvements the same way for another.

We would measure how many times we were able to run the improvement machine in a year, not so much the actual sustained impact we were making.

Improvements that were made without the machine might not be measured or credited at all. Or worse, these rogue improvements might actually be discouraged since they are made by people who aren’t certified to run the machine.

Now… substitute “kaizen event” for “improvement machine” and see if it makes any sense.

Why Are Big Batches Necessary?

The reason the Large Monument Machine has to cycle batches of output to different customers is because those customer processes don’t have the internal capability to do what it does. We need an outside resource to do it.

The countermeasure we strive to apply in these cases is to identify the capability that the customer process does need. We then work hard to develop it on a scale they can incorporate into their daily work. This is typically smaller, more specialized, and scoped to their needs.

My purpose here, though, is to apply a metaphor, not to discuss the economics of large capital equipment.

When we “batch improvements” it is often for the same reason: The area that is being improved can’t do it themselves, so we have to dedicate a scarce outside resource – an improvement expert – to lead them through it. Since that improvement leader can’t be there 100% of the time, he has to work as hard and fast as he can when he IS there.

Making Improvements vs. Teaching How to Make Improvements

The countermeasure in both scenarios is the same: Develop the capability within the process. In the case of making improvements, this means asking ourselves “Why can’t they do it?”

All of these are harder than just doing it for them. But if we want improvement to flow, this is the work that must be done.