What Does Your Customer See?

Travel plans sometimes come together at the last minute. I went to the green company’s web site to rent a car, and got a message saying the site was down for maintenance.

It said to please call the 800 number if I wanted to make a reservation.

I called the number.

The nice person on the phone asked if I wanted to make a new reservation or discuss a current one.

I said new reservation.

“Oh, our system is down for maintenance. Can you try again in a few hours?”

It was already midnight, so I really didn’t want to do that.

“That’s OK, I’ll just call Hertz.”
Which I did.

I encountered two problems here.
First was the message that implied that a human could make a reservation while the system was down. The accurate message would have been “Our system is down for maintenance. If you want to make a reservation, please try again in a few hours.”

And, since this is the de-facto process, I have to assume that the company is doing it this way on purpose.

Then again…
Do their executives rent cars through the online system? Do they experience what their customers do? Do they see the “we’re closed, please go away” sign that is part of their normal process every Saturday night?

Another company once put me on hold. The system kicked to a local radio station rather than silence. And so I was waiting for a customer service response while listening to Mick Jagger “I don’t get no… sat is fact ion…”

Standard Problem Solving

A key point of Mike Rother’s book Toyota Kata is that the organization develops a very deep core-competency in problem solving.

In order to develop competency at anything, there must first be a standard to strive for. What I am realizing is the precise method used doesn’t matter nearly as much as having a method (that works) and rigorously striving to follow it.

Why is this important?

Consider the opposite. Let’s say, hypothetically, that we have a team of very good problem solvers and they are trying to tackle a tough problem. However each of these people brings a different method to the table.

As they discuss the problem, each will be trying to frame it in his or her paradigm for how to go about arriving at the root cause and finding a countermeasure. Indeed, even those words (root cause, countermeasure) might be different.

Some of them might not even call it a “problem.” A team member steeped in Theory of Constraints is going to be referring to a “constraint” – what is constraining the system from advancing to the next level of performance.

Someone else will insist on calling it an “opportunity.”

No matter how competent each individual team member, the group is going to expend a lot of time and energy with how to go about even defining the problem. This is time and energy that is not spent actually solving it.

Things get worse if there are weak problem solving skills to begin with. Someone might have heard of “5 Why’s” for example, and try simply asking “Why?” repeatedly, and writing down the answers on the flip chart in a mistaken belief that this effort leads the team to the root cause of the problem. (it doesn’t, as the room is hermetically sealed to information flow).

So if the organization has a structure, a method, for problem solving there are at least steps that should be consistently followed.

Introduce a good facilitator / teacher / mentor into the mix, and they get an opportunity to practice with coaching, and develop skill.

But “without a standard, there can be no improvement” and the same thing applies to problem solving and improvement itself. If you want to get better at it, you need to start with a standard you are striving to achieve, and then study what keeps you from achieving it.

Measuring Improvement

One of the most common (and frustrating) problems for the staff lean practitioner is being asked to “measure the savings” resulting from specific improvements.

(This problem is related to, but different from, trying to measure “lean progress” or the status of implementation.)

There are two issues in play here.

First is the level of understanding in the leaders who ask for this in the first place. Frankly, it isn’t their fault. Authors, consultants, and practitioners have been “selling” the concept of “lean production” as a stand-alone thing to do for decades.

It is really easy, in the initial excitement of grasping the potential, to just try to push the tools and promise that great savings will result from simply implementing them.

The initial literature was all about describing the performance of benchmark companies (like Toyota, though there were others), describing the visible tools and saying, in effect, “if you just implement these tools, you’ll get this kind of results.

But making these changes can be expensive. The obvious costs are consulting fees, time (perceived to be) taken away from production work. Therefore, there must be a sufficient ROI to “justify” making the changes.

For the practitioner, the countermeasure is to try to shift the focus to establishing a business objective first.

This shifts the conversation from “justifying improvement” to “what problems must we solve to hit the objective?”

The financial evaluation then shifts from "justifying moving beyond the status-quo” to evaluating alternative solutions to the problem.

If you ask directly, most managers will have things in mind that they would like to do better. The challenge is to get those things framed in enough detail that some value is created for actually getting there.

Boeing Moving Line

Boeing’s “PTQ” (Put Together Quickly) videos show a time lapse of an airliner in production. They have been producing the for years – certainly since I was working there.

This one, though, shows something a little special.

When I first started working there, the idea of a line stop was unthinkable. The plane moved on time, period. Any unfinished work “traveled” with the plane, along with the associated out-of-sequence tasks and rework involved.

The fact that the 737 is now built on a continuously moving assembly line in Renton is fairly well known.

But what struck me in this PTQ video is that one of the things highlighted in it is a line stop. It happens pretty quickly at about 1:57.

The video is also full of rich visual controls to allow the team to compare the actual flow vs. the intended flow. See many many you can spot.

Some Healthcare Observations

A couple of weeks ago I had the opportunity to return and see my friends in the Netherlands, and I’d like to share some observations from the Lean Thinking in Healthcare Symposium I attended over there.

But that conference was on Friday. I arrived in-country on Monday morning at 7:30am. By 10:30 am I was in sterile scrubs in an operating room observing a knee replacement operation. (I was told of this agenda while on the way there, at about 9:30.) I’ve got to say it was quite an interesting experience, and here is my public, if belated, thanks to Dr. Jacob Caron, who graciously brought me into his domain. Thanks, also, to his patient for allowing me into this bit of her life as well.

The experience was fascinating, and enlightening. Here is the core value-add of a long and complex process as the patient is moved through the various stages of treatment. And at that core, things are organized, quiet, efficient. Of course it is nothing like an O.R. on television. Drama is the last thing a real-life surgeon (or patient, for that matter) wants in the O.R.

The work flow of instruments caught my eye. We all know that the surgeon asks for the instrument he needs, and the O.R. nurse hands it to him, usually anticipating his request.

But there is a return flow as well. As the surgeon is done with an instrument, he puts it down as he asks for the next one. The O.R. nurse then quickly picks it up, wipes it (if necessary), and re-orients it so she can pick it up quickly when it is needed again.

None of this is really surprising with a little thought. I imagine the tight circle around the patient is organized pretty much the same way in every operating room in technologically advanced countries. In manufacturing, we use the “like a surgeon” analogy to describe how team members who directly add value should be supported.

Later that afternoon, I was touring the ward where the orthopedic surgery ward with the supervisor.

They are working on kaizen, they have an Problem – Improvement board and do a decent job keeping track of things that disrupt work.

“No time” seemed to come up a lot as a reason for the nurses. And, from what I know of the workload of hospital nurses, this is not a surprise either.

But where does their time go?

Let’s consider that nurses are the front line. Yes, the physicians get the attention, but aside from cases like surgery, it is the nurses who actually deliver the care to the patient. In other words, though the physicians design the care, it is the nurses who actually carry it out.

So here was my question / challenge to the audience at the conference:

No operating room in the developed world would ever tolerate a situation where the surgeon had to go look for what he needed to deliver care to the patient. The surgeon’s world is fully optimized so she can devote 100% of her attention to the patient.

Yet, in those very same hospitals, all over the world, we tolerate – every day – conditions where nurses, who are also primary care providers, spend too much of their time fighting entropy, looking for what they need, improvising, dealing with interruptions – all of the things we would never tolerate in the O.R.

Why the disparity?

Toyota Under Fire

Toyota Under FireSo many of us were wringing our hands a year ago. Our idealized vision of Toyota as the source of all perfection and example was tarnished and crumbling before our eyes. Prominent “names” in our field were talking about the need to go beyond Toyota. The vaunted TPS was clearly failing.

Or was it?

Like everyone else, I could only speculate based on a mix of the (mis) information emerging from regular press reports, the opinions of some insiders, and the insights I could glean from contacts with direct access into the company.

When McGraw-Hill offered an early copy of the book for review, I eagerly accepted because I, too, wanted to know the whole story. (<— smooth, seamless disclosure for the benefit of the FTC)

What really happened?

That is the question that Jeff Liker (with Timothy Ogden) set out to answer in the book Toyota Under Fire.

Losing Money

When I hear the term “Toyota under fire” I think of the “sudden uncontrolled acceleration” debacle from late 2009 through the spring and summer of 2010.

Perhaps that is because I didn’t consider that reporting three quarters of losses was the kind of adversity I would consider “under fire.” At least not for Toyota.

In retrospect, I probably glossed over that period because I felt I could predict Toyota’s response to the great recession and the economic problems it caused them – they would double down on what they have always done, and strive to do it even better than they had in the past.

They would first work to get the problem contained – and return to profitability without compromising their core values.

Then they would work to eliminate the root cause(s) of the problem by reducing their break even point.

The result would be the emergence of an even more formidable competitor that is capable of weathering an identical recession without incurring these losses.

And, according to Liker and Ogden, that is exactly what happened.

In the first half of the book, they tell the story of how Toyota responded to the recession in a rich detail that captures how this amazing corporate culture functions when it is under financial pressure it has not experienced since 1950.

What we see is the entire company mobilizing and carrying out its kata pretty much as described by Mike Rother in his book.

But there is also more. We see that this was only possible because the company had worked hard in the good times to be prepared for this kind of adversity, even as it was unthinkable. This enabled Toyota to do things that only Toyota could do.

No matter what other companies may say about their values around team members and suppliers, there are few that could (or would) continue to make payroll, support key suppliers, and continue to invest in R&D while reporting losses and facing a 30% drop in their top line, even if they wanted to.

And we see another side of the story – how an incredibly ignorant, uninformed and uncurious press force-fit the things they saw into their own management paradigms – turning a show of strength in the face of adversity into a negative story. It turns out this is a precursor for what was to follow.

Losing Faith

In August 2009, just as the financial crisis was coming under control, a tragedy set a series of events into motion that would test the company to its very core.

…Mark Saylor and his wife, daughter and brother-in-law were killed when their Lexus, on loan from a dealer who was servicing the family’s own vehicle, careened out of control at more than 100 mph, collided with another vehicle, and crashed into a ravine, setting the car ablaze.

Liker and Ogden offer a comprehensive account of the events that unfolded over the next year while this story spun out of control as the press, politicians, attorneys all fed on – and added to – the public’s fears about the safety of their automobiles.

The story is both fascinating and frustrating as Toyota’s technically oriented culture is focused on facts and data while it is confounded and overwhelmed by a political and litigation culture that focuses on sensationalizing rumors and innuendo.

Toyota learns a hard lesson – that reputation has less to do with the truth than about perception, and decades of work can be destroyed in weeks in the political-legal-press feeding frenzy.

In the end, though, the Toyota Way emerges. Just as they did in the recession, they accept responsibility for the things that affect them, regain focus on their customer’s needs – technical as well as emotional – and double down on what Toyota does best. This time, though, they learn to do that in a different context – the global / cultural one.

A great story in the classic mold of the protagonist emerging stronger from adversity while confronting his personal shortcomings.

Overall

I strongly recommend this book for anyone who wants to be able to articulate the story of how Toyota persevered through the most trying time in their history since they emerged as a global company. This was a transformative time for the company, possibly as significant as the losses and strike in the late 1940’s that set the path for the future.

That being said, there are two areas where I think Toyota Under Fire could have done better conveying this story.

The first is context. And context begins with background.

In the decades prior to all of this unfolding, Toyota had done little (in my opinion) to alter the public’s view of them as a “foreign” company even though they directly employed tens of thousands of people in the U.S. and sourced many millions of dollars of parts from U.S. companies. I believe they failed to put a human face on the American side of the company. They allowed the product to speak for them. In effect, they allowed their competitors to control a large part of Toyota’s cultural positioning.

Hal-9000Next is the aspect of technology. Liker and Ogden address the gap between engineering reliability of the electronic controls and the public’s emotional confidence in them.

However I am not sure they convey the cultural gap between that emotional confidence (or lack of it) in the USA vs. what would be felt in Japan or even Europe. Simply put, Americans are less trusting of technology in their cars. I am not certain the engineers in Japan fully grasped this gap. If they did, I am not certain they didn’t dismiss it.

With all of that as background, while the Saylor’s accident would have been tragic at any time, late August 2009 could not have been a worse moment for Toyota.

The accident was a scant two months after General Motors’ controlled immolation into government-owned bankruptcy, and the company was still breaking up. Chrysler was sold off to Fiat. Ford’s stock was selling for under $5.

And the day before the Saylor accident, Toyota had announced that the NUMMI joint venture was being closed after GM had pulled out.

With Toyota relatively healthy (compared to everyone else), still perceived as a “foreign” company, and seen by many as “responsible” for the demise of GM, they were operating in a public and political atmosphere that was fuel and oxygen rich. The Saylor accident was a spark.

Had Toyota grasped how precarious their political and cultural standing was, they might have acted much more aggressively and much sooner when this story started to unfold.

The fall of 2009 and spring of 2010 was slow for domestic U.S. news, so there was nothing to push the Toyota story out of the news cycle.

While Liker and Ogden correctly and accurately relate how Toyota managed to finally “get ahead of the story,” the precipitous drop in negative press reports about Toyota occurs in August 2010 – as the drama of the trapped miners in Chile begins to unfold.

I mention this context because it is not only important for the reader, but equally important for Toyota. They learned a hard lesson about the U.S. news cycle, especially how a story can get legs under it. This had to be tough for a company used to dealing in a world of verifiable facts and data.

To a company who values, above all, being in control of their own destiny, they had allowed much of the background to be written by others.

This story was as much about Toyota’s total lack of an emotional connection into the overall U.S. culture as it was about their cars and engineering. And while Liker and Ogden talk extensively about Toyota’s aggressive countermeasures to establish better connections to customer’s perceptions, I would like to have read about how Toyota addressed (or didn’t) this cultural positioning as well.

The only other quibble I have is I believe the book could have been a little more tightly edited. I am giving this a pass, though, because the final technical report from NASA came out in March 2011, and this book landed on my porch a scant couple of weeks later – the ink was still wet. So from that standpoint, I recognize the last minute frenzy of writing and editing that had to be done to include the latest relevant information.

In the end – buy the book but recognize it is still a bit insular – much as Toyota can be. That is perhaps something they still need to address.

Breaking News

Two stories of interest as I am writing this.

Toyota Wins Key Unintended Acceleration Case

(April 1) After deliberating for approximately 45 minutes, a jury reached a defense verdict in favor of Toyota Motor Sales, U.S.A., Inc. in an alleged unintended acceleration case brought by Dr. Amir Sitafalwalla, who claimed that an unsecured driver’s side floor mat was the primary cause of the crash of his Scion vehicle in August 2005.

During the course of the week-long trial, Dr. Sitafalwalla’s primary expert, Dr. Anthony Storace, withdrew his assertion that the Electronic Throttle Control System in the Scion could also have been a cause of the accident based on his acknowledgment that he had no basis to support that claim.

Of note is that the news reporting of this story is buried.

This story, however, was on the news tonight (April 4):

Toyota: N. American plant closures likely in April

By BRUCE SCHREINER, Associated Press – Mon Apr 4, 4:56 pm ET

LOUISVILLE, Ky. – Toyota Motor Corp. said Monday that it’s inevitable that the company will be forced to temporarily shut down all of its North American factories because of parts shortages due to the earthquake that hit Japan.

The temporary shutdowns are likely to take place later this month, affecting 25,000 workers, but no layoffs are expected, spokesman Mike Goss said. Just how long the shutdowns last or whether all 13 of Toyota’s factories will be affected at the same is unknown and depends on when parts production can restart in Japan, he said.

So far the North American plants have been using parts in their inventory or relying on those that were shipped before the earthquake, Goss noted. But those supplies are running low.

“We’re going to get to a point this month where that gap in the pipeline starts to show up. So we’ll have to suspend production for a while,” he said.

While interesting, this story buries the lead into the middle of the second paragraph: “… affecting 25,000 workers, but no layoffs are expected.”

This statement is ambiguous, but if it means “we are going to keep paying everyone and working on improving the work while the plant is shut down” that is the story here. Otherwise, this sounds like a routine shutdown-and-furlough-the-workers story.

What makes it more interesting is that Toyota’s press release site refutes the story altogether:

Toyota Statement Regarding Status of North American Production

NEW YORK, NY (April 4, 2011; Posted at 3:15 PM EDT) Contrary to recent headlines, nothing has changed from our update from March 23rd regarding our North American operations.

We continue to assess our supply base in Japan following the earthquake/tsunami. We have communicated to team members, associates and dealers here that some production interruptions in North America are likely. It’s too early to predict location or duration.

Currently, the greatest majority of parts for our North America-built vehicles come from approximately 500 suppliers in North America. Also, we continue to receive parts from Japan that were already in the pipeline, limiting the immediate impact. We will continue to work closely with suppliers in North America and Japan to minimize any disruptions to Toyota’s overall North American operations.

The reason I bring up this little chain of news stories is that it reinforces my notion that Toyota is still playing “business as usual” in how they manage the news cycle. In this case, no harm, but my questions for them are:

  • What is your target condition for public perception of these stories?
  • What is the current public perception?
  • If there is a gap, what is keeping it from being closed?
  • What is your plan to address that issue?
  • When can we see what you have learned from the first step?
because every process is subject to kaizen.

Why before What

In this TED video, Simon Sinek summarizes a key thing that differentiates an idea that catches on vs. one that plops.

This is relevant to us at a couple of levels.

First, as Sinek points out, truly great companies succeed because they stand for something higher. They have a “why” that drives what they do and how they do it.

Companies that cannot articulate what they stand for are at a competitive disadvantage vs. those who can.

But these concepts are also critical to those of us who are trying to sell the concept of changing the way our own organizations run. Watch the video – then continue below.

In spite of what is taught in the business schools, business decisions are rarely made based on financial analysis and rates of return. Those things are carefully constructed, but often after the fact to justify what someone wants to do already (i.e. has already decided to do).

When we try to sell our changes, we often try to address the “what’s in it for me?” but still continue to try to make logical “what” type arguments.

That doesn’t work. It has to feel right.

Think about your own organization. When or where do things feel like they are going really well, what is aligning? What values are being realized? How do those moments differ from times or places where things are not going so well?

What makes people say “OH Yeah!” ?

As you try to make the case for “lean” or continuous improvement in your organization, are you crystal clear what you believe in? Can you articulate it? Do others in the company want to believe in the same things?

The Report-Out

The classic one-week kaizen event ends with a report-out by the team that outlines the improvements they have made, and the results they have achieved.

Actual results, though, are notorious for falling short of what was reported. Action items are left over, and things frequently peter out unless there is a huge effort to force sustainment.

Let’s look at this a little differently.

Typically what happens during the kaizen week is that a new process is designed, and some things are put into place to enable it – point of use, rearranging things for flow, etc.

The report out is describing expected results, and how the process must operate to deliver them.

In other words, a very common outcome of a kaizen event is a pretty well thought out target condition. This is how we want the process to operate, this is the result we are going to strive to achieve. It is all future tense.

What happens next will make or break things.

The next question that should be asked is “Great! When are you going to try it, and what do you expect to learn?” If the report-out does not directly address this question, then you can expect the typical result – steady erosion.

In fact, the process of seeing and addressing those problems must be embedded into the daily management process itself.

The report-out is the beginning of kaizen, not the end. The next phase is not “follow-up.” It is a natural continuation, if less intense, of the kaizen process. The report-out is describing an engineering prototype. Now it is time to test it and discover what we didn’t know during the design process.

 

Lean Facilitators are Countermeasures

What is the role of your lean facilitator?

This question comes up now and again, was recently posed on the LEI forums by someone looking for help with a job description.

I extrapolated from his question that he was looking to the job description as a line of defense against dilution of the facilitator’s focus and effort by projects that might not be going in the appropriate direction.

In effect, this is putting the lean facilitator in the role of a weakened zampolit with the role of educating the “correct view” and challenging decisions that run counter to it. Except that more often he has to sell the “correct view” rather than impose it.

The fact that the question is being asked at all indicates that the organization has not really thought through what their operational vision is. How will the company work, what are the responsibilities and roles of the leaders?

What are the leaders’ job descriptions in this new world?

Those job descriptions become a target condition for each of them.

What is the gap?

If there are gaps in skills and knowledge, then we need countermeasures.

At this point, the role and responsibility of a lean facilitator might begin to emerge as one of those countermeasures. Don’t have the expertise? Import it.

What doesn’t work, though, is to use the lean facilitator to substitute for the leader’s full and direct participation in the process of improvement. And no job description, no matter how carefully crafted, can fix that.

Notes on A White Board

WHAT STOPPED THE WORK TODAY?

Identify each step (details!)

For each step ask:

Why is this necessary? What is its purpose? —-> Eliminate unnecessary, wasteful details.

Can this detail be done outside of the critical flow? —-> re-sequence. Prior to the start, everything ready to go.

Clearly define who must do what and when.

  • Content
  • Sequence
  • Timing
  • Outcome

How will we continuously verify actual work vs. the plan?

Ask “What stopped the work?”

  • Why must the team member leave the work area?
  • What slows him down?

(Back to start)