KataCon 2020: Billy Taylor on Deliberate Practice

The first official day of KataCon kicked off with a keynote on deliberate practice by Billy Taylor. I first met Billy back in 2012 when I was doing some work with Goodyear. When I saw him at last year’s KataCon it was like running into an old friend, but that is who Billy Taylor is – even if you just met him.

Billy Taylor on Deliberate Practice

Pull quotes and thoughts

The Concept of Deliberate Practice
  • Toyota Kata has two sides, like a coin. On one side is scientific thinking. On the flip side is deliberate practice.
  • Traditional practice is often just mindless repetition. Deliberate practice has focused attention on perhaps one aspect of the routine.

A couple of things come to mind for me here. First is that too many coaches go through mindless repetition of the Coaching Kata. They just ask the next question on the card, and never practice using the questions to nudge the learner’s thinking to the next level.

This means they never practice in a way that pushes them as coaches. More about that below.

The other is that we, all too often, take a learner through the entire process much too fast. We do this in classes to give them a taste of the whole process. But in real life, perhaps it would be best to anchor each Starter Kata step and ensure there is at least understanding before moving to the next.

When 2nd coaching it is equally important to focus both the coach AND the learner on improving a single aspect of the board.

As I am writing this, I am reflecting more, and parsing more. This slide offers a ton of insight for me:

From Billy Taylor’s KataCon6 Presentation

There is so much here on a lot of levels.

This is how I interpret the graphs: On the left we have “Just Practice.” Maybe I am learning to play a song on the guitar. As I practice I learn to play it better and better. Then I hit a plateau because I am comfortably good and not challenging myself anymore. I am just playing. And that feels awesome, because I validate to myself that I am pretty good.

At a higher level, this is the “lean plateau” that so many companies hit. They get really good at running kaizen events, or black belt projects, or whatever they do. They hit a pretty good level of performance, but things erode. They reach a plateau when the implementers are spending all of their time re-implementing what has eroded. They shift into mindlessly repeating the familiar rather than challenge themselves. What are we missing? Why is the skill concentrated into the same half dozen individuals who have been doing this since 1999?

The graph on the right represents something that is the same, but different. Take a look – each little squiggle repeats the graph on the left, only smaller. Each time a plateau is hit, the learner challenges herself to practice a new aspect. Things get a little worse for a bit, then as the new aspect is mastered, the process is repeated.

I see the job of the coach as two fold:

  • To challenge the learner in small steps, always looking for the obstacle to the next level of performance.
  • To offer up specific things to practice.

Billy’s presentation covered a lot of overlapping territory – enough for at least two more posts – stay tuned.

KataCon 2020: Ninja Kata and Kata in Secret

Clipped from Steven Kane’s presentation

In his level-set / coaching demonstration, Steven Kane talked extensively about obscuring the jargon of Toyota Kata to defuse pushback.

Tracy Defoe had a separate brief presentation titled “Kata in Secret” – and this has been a topic of discussion in the weekly Cascadia Kata Coaches call that Tracy hosts.

The two cases were a little different. In Steven’s case, he was (I think) talking about an organized effort. Lots of companies trying something new need to alter the jargon a bit. On a broader scale, there are quite a few companies where Japanese jargon will create an immediate wall of resistance, so why create the problem? Just change the words.

And I’ve certainly encountered cases where there was resistance to the very idea of any structure at all. Dealing with that took regressing away from the Coaching Kata and back to the more informal conversation that the Coaching Kata is teaching us to have.

Tracy’s cases are a little different. She is collecting stories from often solo practitioners who are practicing Toyota Kata under the radar because they are perceiving career risks if they are overt. In one cases a leader was explicitly told not to use Toyota Kata because it ran counter to the corporate lean program. She did anyway.

While I find these stories interesting, I am not surprised by them. I have seen, and even advocated, this for a long time. I call it “camouflage.” My principle is this:

Do the right thing, but make it look like what they expect to see.

In other words, there is no point getting dogmatic about something unless doing so advances your cause in come way. In still other words, don’t let “being right” get in the way of what you are trying to get done.

For example – one company I have worked with for a long time got hard pushback from their corporate continuous improvement mafia office. “We don’t have obstacle parking lots. We have kaizen newspapers.” OK, fine. They labeled the obstacle sheet “kaizen newspaper” and just call it “improvement coaching” and everybody is happy.

The key is this: Don’t dilute what you are trying to do. If you start moving away from developing a pattern of scientific thinking in the people you are helping, then you are letting the tools take precedence.

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.

The Cancer of Fear

File:Nandu River Iron Bridge corrosion - 03.jpg

I am sitting in on a daily production status meeting. The site has been in trouble meeting its schedule, and the division president is on the call.

The fact that a shipment of material hadn’t been loaded onto the truck to an outside process is brought up. The actual consequence was a small delay, with no impact on production.

The problem was brought up because bringing up process misses is how we learn what we need to work on.

The division president, taking the problem out of context, snaps and questions the competence of the entire organization. The room goes quiet, a few words are spoken in an attempt to just smooth over the current awkwardness. The call ends.

The conversation among those managers for the rest of that day, and the next, was more around how to carefully phrase what they say in the meeting, and less about how do we surface and solve problems.

This is understandable. The division president clearly didn’t want to hear about problems, failures, or the like. He expected perfect execution, and likely believed that by making that expectation loud and clear that he would get perfect execution.

That approach, in turn, now has an effect on every decision as the managers concern themselves with how things will look to the division president.

Problems are being discussed in hallways, in side conversations, but not written down. All of this is a unconscious but focused effort to present the illusion that things are progressing according to plan.

Asking for help? An admission of failure or incompetence.

This, of course, gets reflected in the conversations throughout the organization. At lower levels, problems are worked around, things are improvised, and things accumulate and fester until they cannot be ignored.

They the bubble up to the next level, and another layer of paint is plastered over the corrosion.

Until something breaks. And everyone is surprised – why didn’t you say anything? Because you didn’t want us to!

In a completely different organization, there were pre-meetings before the meeting with the chief of engineering. The purpose of these pre-meetings was to control what things would be brought up, and how they would be brought up.

The staff was concealing information from the boss because snap reaction decisions were derailing the effort to advance the project.

And in yet another organization they are getting long lists of “initiatives” from multiple senior people at the overseas corporate level. Time is being spent debating about whether a particular improvement should be credited to this-or-that scope. It this a “value improvement,” is it a “quality improvement,” is it a “continuous improvement” project?

Why? Because these senior level executives are competing with one another for how much “savings” they can show.

Result at the working level? People are so overwhelmed that they get much less done… and the site leader is accused of “not being committed” to this-or-that program because he is trying to juggle his list of 204 mandated improvement projects and manage the work of the half-a-dozen site people who are on the hook to get it all done.

And one final case study – an organization where the site leader berates people, directly calls them incompetent, diminishes their value… “I don’t know what you do all day”, one-ups any hint of expert opinion with some version of “I already know all of that better than you possibly could.”

In response? Well, I think it actually is fostering the staff to unite as a tight team, but perhaps not for the reasons he expects. They are working to support each other emotionally as well as running the plant as they know it should be run in spite of this behavior.

He is getting the response he expects – people are not offering thoughts (other than his) for improvements, though they are experimenting in stealth mode in a sort of continuous improvement underground.

And people are sending out resumes and talking to recruiters.

This is all the metastasized result of the cancer of fear.

Five Characteristics of Fear Based Leaders

Back in 2015 Liz Ryan wrote a piece in Forbes online called The Five Characteristics of Fear Based Leaders.

In her intro, Liz Ryan sets out her working hypothesis:

I don’t believe there’s a manager anywhere who would say “I manage my team through fear.”

They have no idea that they are fear-based managers — and no one around them will tell them the truth!

And I think, for the most part, this is true. If I type “how to lead with fear” into Google I get, not surprisingly, no hits that describe the importance of intimidation for a good leader – though there are clearly leaders (as my example above) who overtly say that intimidation is something they do.)

My interpretation of her baseline would be summarized:

People who use fear and intimidation from a position of authority are often tying their own self-esteem to their position within that bureaucratic structure. Their behavior extends from their need to reinforce their externally granted power, as they have very little power that comes from within them.

They are, themselves, afraid of being revealed as unqualified, or making mistakes, or uncertain, or needing help or advice.

I have probably extended a bit of my own feelings into this, but it is my take-away.

She then goes on to outline five characteristic behaviors she sees in these “leaders.” I’ll let you read the article and see if anything resonates.

Liz Ryan’s article is, I think, about how to spot these leaders and avoid taking jobs working for them.

This post is about how the organization responds to fear based leadership.

The Breakdown of Trust

A long time ago, I wrote a post about :The 3 Elements of “Safety First”. Today I would probably do a better and more nuanced job expressing myself, but here is my key point:

If a team member does not feel safe from emotional or professional repercussions, it means they do not trust you.

Fear based leadership systematically breaks down trust, which chokes off the truth from every conversation.

Here is my question: Do you want people to hide the truth?

If the answer is “No,” then the next question is “What forces in your organization encourage them to do so?” because:

Your organization is PERFECTLY designed to produce the BEHAVIORS you are currently experiencing.

– VitalSmarts via Rich Sheridan

LEI Book: Getting Home

“Are you ahead or behind?” seems an innocent enough question.

But when asked by a Toyota advisor, the simple process of becoming able to answer it launched Liz McCartney and Jack Rosenburg on a journey of finding consistency in things that were “never the same” and stability in things that “always changed.”

Getting Home is, first and foremost, a story. And, with the “business novel” being an almost worn-out genre, seeing a non-fiction story was refreshing. So when Chet Marchwinski from the LEI offered a review copy to me, I accepted.

For the story background, I’ll leave it to you to read the blurb on Amazon.* Better yet – read the book – and it is worth reading. I’ll say that right up front.

Yet with stories like this it is all too easy to dismiss them because they have different circumstances from “my” specific case and say “Yeah, it worked there, but won’t work here.”

I would contend, however, that in this case “it worked” in situations that are far more difficult than anything we are likely to encounter in most organizations.

What I want to do here is help pull their specific achievements into more general application – what lessons are here that anyone can take away and apply directly.

What They Achieved

I can’t think of a lot (any?) business circumstances that would have more built-in variability and sources of chaos than the process of rebuilding communities after a disaster such as a hurricane or flood.

Every client has different circumstances. The make, mix and skill levels of the volunteer workforce changes continuously. Every community has different bureaucratic processes – not to mention the various U.S. government agencies which can be, well, unpredictable in how and when they respond.

Yet they have to mobilize quickly, and build houses. This means securing funding, getting permits, mobilizing unskilled and skilled labor, and orchestrating everything to meet the specific needs of specific clients on a massive scale… fast.

How They Achieved It

When they first connected with their Toyota advisor, the simple question, “Are you ahead or behind?” prompted the response that drives all improvement, all scientific advancement, all innovation:

“We don’t actually know.”

Actually they did, kind of, but it was in very general, high-level terms.

And that is what I encounter everywhere. People have a sense of ahead or behind (usually behind), but they don’t have a firm grasp on the cause and effect relationship – what specific event triggered the first delay?

This little book drives home the cascading effect of ever deepening understanding that emerges from that vital shift from accepting things as they are to a mindset of incessant curiosity.

Being able to answer “Are you ahead or behind?” means you have to have a point of reference – what is supposed to happen, in what order, with what timing, with what result. If you don’t know those things, you can only get a general sense of “on track” or not.

They had to develop standards for training – what to train, how to train – volunteers! – , which meant challenging assumptions about what could, and could not, be “standardized.” (A lot more than you think.)

A standard, in turn, provides a point of reference – are we following it, or are we being pushed off it. That point of reference comes back to being able to know “Are we ahead or behind?”

 

It Isn’t About the Specific Tools

Yet it is. While it isn’t that important about whether this-or-that specific tool or approach is put into place, it is critical to understand what the tools you use are there to achieve.

As you read the book, look for some common underlying themes:

Information as a Social Lever

The project started revolving around the ahead/behind board.

In the “lean” world, we talk about “visual controls” a lot, and are generally fans of status boards on the wall. We see the same thing in agile project management (when it is done well).

These information radiators work to create conversations between people. If they aren’t creating those conversations, then they aren’t working. In Getting Home it was those conversations that resulted in challenging their assumptions.

Beyond Rote Implementation

Each tool surfaced more detail, which in turn, challenged the next level. This goes far beyond a checklist of tools to implement. Each technical change you make – each tool you try to put into place – is going to surface something that invites you to be curious.

It is the “Huh… what is happening here?” – the curiosity response – that actually makes continuous improvement happen. It isn’t the tools, it is the process of responding to what they reveal that is important.

Summary

Like the tools it describes, Getting Home is an invitation, and that is all, to think a little deeper than the surface telling of the story.

My challenge to you: If you choose to read this book (and I hope you do), go deeper. Parse it. Ask “What did they learn?” ask “What did this tool or question reveal to them, about them?” And then ask “What signals did they see that am I missing in my own organization?”

 

 

———-

*This is an affiliate link that give me a very small kickback if you happen to purchase the book – no cost to you.

It will feel worse because it’s getting better.

image

The line is starting to flow, or at least there is more time flowing than not flowing. The places where it isn’t flowing well are now much more evident.

Things are speeding up. That is placing more stress on the engineering and materials supply processes where, before, they were shielded by a rough start-up that was always behind schedule.

They are catching up on the backlog, closing in on “on schedule shipment.”

“John” forgot to send a batch of parts to an outside processor. Before that would have been no big deal, it would be a day or so before those things were actually needed. But this time it briefly stopped the line and forced a work-around.

When everything was a work-around, nobody noticed. This time it got on the radar. It feels worse because the system is sensitive to smaller problems now, and there are plenty of those.

It isn’t “John’s” fault. He is flooded with a constant flow of things he needs to react to. There isn’t a structure for him to work within. That is the next opportunity.

Thus, it is critically important to remember a Toyota mantra:

‘No problem’ is a big problem.

If problems are not coming up, then your system is hiding them, plain and simple. You have stopped learning, stopped improving, stopped growing.

It is an easy groove to get into because we get all kinds of feel-good brain chemicals when things are going smoothly. We want more of those, less of the ones that call us to action.

But it is those “call to action” things that drive us to get better.

If You Think “We Can’t Please Our Customers” You’ll Be Right

The center of the B Concourse at O’Hare Airport in Chicago is dominated by a Brachiosaur skeleton, part of the Field Museum exhibit for their store there.

IMG_20131206_215236_938

As a reminder for those of you over the age of 14, the Brachiosaurus was 70 feet long, 30 feet tall, weighed in at around 60 tons.* It had a brain the size of an avocado. It wasn’t smart. It wasn’t fast. Its main defense against predators was that it was simply too big to catch and eat.

In the shadow of the Brachiosaurus is United Airlines’ main customer service desk for their headquarters hub.

Back in June, Chris Matyszczyk published some really interesting commentary on Inc. Magazine’s site: The CEO of United Airlines Says He Can’t Really Make Passengers Happy

In his article, he quotes from an interview Oscar Munoz, the CEO of United Airlines, gave to ABC. From the interview:

“It’s become so stressful,” he said, “from when you leave, wherever you live, to get into traffic, to find a parking spot, to get through security.”

“Frankly,” Munoz added, “by the time you sit on one of our aircraft … you’re just pissed at the world,” and improving the flying experience won’t ultimately depend on “what coffee or cookie I give you.”

My interpretation? “We have given up trying to please our customers.”

That was the interpretation of Ed Bastian, Munoz’s counterpart at Delta Airlines:

…when Munoz’s views were put to Delta CEO Ed Bastian by Marketplace.

His response was, well, quite direct:

“I disagree. Those certainly aren’t Delta customers he is speaking to.”

My Perspective as a Frequent Flyer

Just so you know my perspective: In the course of my work, I typically purchase between 10 and 20 thousand dollars worth of airfare a year. While this isn’t anywhere near the highest, I think I am the kind of customer an airline wants to get and retain.

Further, I know the system. I know what to expect, can quickly distinguish “abnormal” from “normal” and know how to maneuver to get out in front of issues I see developing. I pay attention to weather and other events that might disrupt the system, and contingency plan accordingly. I know, generally, how to arrange my stuff to get through TSA smoothly (though they can be arbitrary).

And I have the perks of a heavy frequent flier, which buffers me from a lot of the “stuff” that casual travelers have to contend with.

Munoz used some words that really identify the problem: …by the time you sit in one of our aircraft…”

This casual statement, which correlates with my experience as a former United Airlines customer** implies a belief that the customer service experience begins once you are on the plane. This isn’t where United’s reputation is created. Once you are on the plane, the customer experience of all of the major airlines is pretty similar.

My experience reflects that it is what happens on the ground that differentiates one airline from another.

Assumptions About Customers Come True

The assumption that customers are just “pissed off at the world” and there is nothing we can do about it is a self-fulfilling prophecy.

If that is the attitude from the top, then it lets the entire system off the hook for making any effort at all to understand the things that might take some of the sharp edges off the experience.

On the other hand, if the attitude is “We are responsible for the experience of our customers – even if we aren’t” then the effort can get focused on understanding exactly what kind of experience we want our customers to have, and engineering a system that delivers it to the best of our ability. That, in turn, allows reflection when we miss, and improvement for the next time.

One is a victim attitude. “We’ll get better customer satisfaction when our customers are better at understanding how hard it is.”

The other is empowering – “Even if our customers *are* pissed off at the world, we will own it and work to understand what we can do.

How Does Your System Respond to Stress?

This in my mind, is what really differentiates a good system from a broken one. Like I said, it’s easy when everything is flowing smoothly. But what happens when the system is disrupted?

Is there a mad scramble of figuring out what to do – like it is the very first time a maintenance issue has caused a flight to be cancelled? What are we going to do with all of these passengers? Process them through two people? (See the line in my photo above!)

Or is there a clear process that gets engaged to get people rebooked – leaving the true difficult cases for the in-person agents?

Ironically, the major airline with one of the very best on-time schedule records also has one of the best recovery processes. Go figure.

Then there are little gestures, like snacks or even pizza for those suffering through a long delay.

“It’s not our fault” easily leads to “you’re on your own.”

“We’re going to own it, even if we don’t” leads to “let’s see if we can help.”

Now… to be clear, the entire airline industry has a long way to go on this stuff. But my point is that some are making the effort, while others have given up.

What Experience Have You Designed for YOUR Customers?

That, ultimately, is the question I am posing here. If you start with the experience you want your customer to have – a standard – then you have a point of comparison.

Did we deliver that experience? If so, then could we do it more efficiently?

If not, what got in our way, how do we close the gap?

Without a standard to strive for, there can be no improvement – and I think this is what Taiichi Ohno actually meant.

——

* Estimates of the weight vary quite a bit.

Rough metric equivalents would be around 20 meters long, 9 meters high,  50 tons. About the weight of mid-cold war era tank.

——

** With one exception that was booked for me, I haven’t flown on United since mid 2014 after an experience that could not have been better designed to tell the customer “We don’t work as a team or talk to each other.”

I cashed in my frequent flier miles for a camera about a year later.

Ambitious Growth Plans? Your Customers Will Right-Size You

I’ll call the title of this post “Dave’s Observation.”

He is reflecting his experience in varied industries that if a company grows beyond its ability to deliver quality product, on time, then order volume will drop until it reaches a point that performance returns.

The business literature is full of examples of this – companies who could not keep up with their own success, their performance deteriorates and, well, many of them go out of business.

I have seen more than a few companies with aggressive growth plans that outrun their ability to actually execute, and they get into trouble.

This also happens in mergers and acquisitions where one company is merged into another with the assumption that the combined company can execute and perform in ways neither company has ever done. Starry-eyed executives often look only at the financial models, maybe equipment capacity, and skip over the operational aspects of their due diligence.

In the end, though, if the operational capability is not there, then none of the plans actually matter. Your “synergy” or “economy of scale” will evaporate like an ice cube on the Moon until equilibrium is restored.

Bottom line: If you are engaged in an ambitious growth plan, then list everything that has to be different for your model to work.

By “different” I mean you are asking for or expecting some task execution or level of performance that does not exist today as a matter of mundane routine.

Then ask “What is our plan to close this gap?” – and run the same exercise on executing that plan. “Change” is really hard, and just telling people what needs to be different, no matter how pretty the PowerPoint slides are, no matter how slick the presentation is, won’t make anything change. (If anything, it often breeds cynicism because it is read as unrealistic.)

Change requires step-by-step, methodical, practice to anchor each small change into the system, then the next, then the next.

Toyota Kata offers a good pattern for this. Just don’t confuse the underlying pattern with the methods used to teach it.

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.

 

 

Toyota Kata and Culture Change

I am still digesting my experience at the Toyota Kata Summit (KataCon) and the TWI Summit but I wanted to reflect on one of the emerging themes, and some of the reactions.

One of the themes that emerged at both conferences – and to be clear, something I had a hand in influencing as well – was mechanisms for altering the culture of the organization. In other words, what we brand as “change.”

This is what I would call an “advanced topic”

What is Culture?

Books have been written about “organizational culture” and trying to create models that define “it” in some way. In the end, I think they all come down to various ways of saying “how people talk to each other.” This includes who talks to whom, and what structures and rules guide those conversations.

When we study “culture” we are looking at the groups’ default patterns of interaction. If we want to change those patterns, we have to alter people’s habitual behaviors. As I said in my KataCon keynote, This. Is. Hard. It is even harder when you are talking about group behavior vs. simply individuals.

Making Toyota Kata Work is Changing Culture

The point of using Toyota Kata is to practice and learn a scientific mindset. Getting an improvement storyboard set up that is focused on a challenge, and going through the Starter Kata of Grasping the Current Condition; Establishing the Next Target Condition; Identifying Obstacles; and Running Experiments Against Obstacles is a technically straight forward.

It is easier with an experienced coach to help you through it, but can be learned on your own if you are willing to be self-critical and persevere through things not working as well as you thought they would.

But beyond the scientific thinking pattern, we are also working to change the default behavior pattern toward one of working in Coach / Learner pairs on an ongoing daily basis. This is not the default mode of most organizations. (If it were, then Toyota Kata would be redundant.)

This means (to me) that, while actually practicing the Starter Kata is very important, getting people to do so in the first place often requires leading past the technical aspects. It requires altering the way people interact and work together.

Whose Work Is It?

Of course this is ultimately the work of line leadership, represented by the “advance group” or “steering team” or “shepherding group” or whatever you call them. Sometimes those people, too, have to learn a new way to lead and manage.

Leadership

The Kansas Leadership Center, whose programs are based on the “Adaptive Leadership” model from Harvard, defines Leadership as:

“The activity of mobilizing people to do difficult work.”

They further assert (and I agree) that leadership is an activity, not a position.

I am bringing these things up because if we want an organization to begin practicing ways to engage one another differently, it is common to run into resistance. In other words, we must mobilize people to do the difficult work of changing their default thinking and routines of interaction.

In doing so, we will surface clashes of hidden values, senses of loss, anxiety and fear: Things which cause people to find reasons to opt out of participating.

Sometimes it isn’t as simple as saying “Just follow the Starter Kata.”

How to Deploy Toyota Kata

Actually the message of “adaptive leadership” has been present since at least the first KataCon back in 2015. One of the mantras that emerged that year was “Kata your Kata” – in other words, there isn’t a clear-cut path that works every time. You have to learn your way into it as an organization, as a leader.

The difficult part is that this requires going in deeper than the Starter Kata, and applying the underlying pattern of Challenge; Current Condition; Target Condition; Experiments against Obstacles.

The pattern is the same, but this isn’t about cycle time variation, it is about influencing (mobilizing) people, reaching agreements, encouraging them to “just try it” – in a process of discovering what works in that case, with those people, then doing it again.

A New Way of Working vs. Business as Usual

So… if we are going to get Toyota Kata out of the classroom, and past the first challenge or target condition into a sustaining, habitual process, we’ll have to address cultural issues.

The skill set for this is different than a technical process change skill set. We’ll have to learn our way through the grey zone for this part as well.

I’d love to see your thoughts and comments.