Evidence of a Problem

In most references describing the process of good problem solving, the first real step is to explain what actually is the problem.

It is easy to get tripped up at this stage and describe the problem in terms of the desired target, or in terms of “lack of” a specific countermeasure. That, of course, skips over the whole point of gaining a deep understanding of the situation before moving too far into intestigating causes.

I heard a great way to frame that first bit of description tonight from Richard.

“What is the evidence of a problem?”

That word, “evidence” does a much better job of conveying the point that this should be a description of the things that are observed, heard, felt, etc. rather than any kind of analysis.

In many cases a “big problem” is actually evidence of many small ones. “Too much inventory” is one of those. So is “defect rates” or any other aggregated measure. If you are running KPIs you probably know that, because they aggregate so much, they are often relatively insensitive until things are so far into the hole that it is a mess to untangle. Better to instrument your processes at much finer levels and get “evidence” in real time.

Genchi Genbutsu in a Warehouse

Now and then something comes across that makes it all worth it. And nothing is more “worth it” to me than to know something I said or did contributed to someone’s insight or impetus to do something spectacular.

Yesterday Earl sent me an email that is one of those times. I was going to edit it from an email to me into a story about Earl’s experience. But instead, I decided to just publish it (with his permission) pretty much as I got it. But to be clear, this is about Earl, and his learning, not about me or my teaching.

Mark,

I received this email [see below] the other day from John.

John was one of the lean leaders working for me in Rochester when I was the Lean Director for Kodak’s Global Logistics team and you were the Lean Director for Equipment Mfg. He is now a professor at RIT teaching lean.

One of the things he does with every class is bring them through his old operation in Kodak. The operation is an outbound crossdock for all of Kodak Park where, through applying our lean principles, primarily “flowing at takt”, we have taken a 2,000,000 square foot (186,000 m2) warehouse and replaced it with an 85,000 square foot (<8000 m2) crossdock.

Along the way we reduced the costs by 70%, improved the reliability to +/- a few hours, and amassed an enviable safety record….and as you can see in his note, we’re making it better every day.

When I think back to how we got here, I have to go back to what started as an innocent Friday night, when you, Paul Cary, and I were sitting around his office and you and Paul were pushing on me that we weren’t really thinking about lean in the right way in Logistics, and I was pushing back that “you didn’t understand”….that we just move pallets around the warehouse.

I can remember like it happened yesterday, but it was actually a few years ago, you and Paul looked at each other, looked at me, jumped up and said “Let’s go see”, so we did.

Several hours later, we emerged from the warehouse, not tired and worn out, but energized and excited. You had helped me to see what was invisible to me (and everyone else around)….even though I was the local “lean expert”.

The approach was classic “Mark”, and I have to admit I’ve stolen it and used it as my own many times, although not nearly as effortlessly. At your insistence, we entered through the outbound dock door, as you pointed out, “closest to the customer”. As I started to walk through and into the warehouse proper, you stopped at the door, and made me stop and describe what I was seeing.

The “Five Why’s” were relentless, and I think it was something like 30-40 minutes before we even moved off that spot, but the seeds were planted right then and there. I had now started to see the whole warehouse as “waste” and totally unnecessary if we could only get product flowing at takt. I can’t tell you how many times I’ve relied on the lessons learned that night to guide me when I get in the middle of something unfamiliar to me.

Well, it took us a couple of years, but your invaluable and patient counsel over the next few years shaped a whole organization’s culture. I know better (now) than to suggest “we’ve arrived”, but the principle of using “flow at takt” and making waste visible to drive continuous improvement is firmly rooted in our DNA now.

Aside from the impressive performance statistics of the operation I know you’ll appreciate more that the things you taught me have been dutifully passed along from me to the manager of the area, and through him, to his successor, and now through the college to many more. All we have to do now is close the loop and get you to hire one of the RIT students somewhere!

I’ll not pretend that a couple of hours on a Friday night several years ago was all it took, and I’m forever indebted to the many hours you spent with me afterwards helping me to grow, but it was truly a life changing event, and I thought you’d appreciate seeing a snippet of what it’s led to. Thanks again for all your insight and support in our, and my, journey.

If you ever find your way back East, you have to stop in to see it, drinks are on me. It is pretty wild, but if you do, I might tiptoe carefully around the idea that you’re the guy that taught me to “physically constrain the process to force it to flow at takt”. It was an essential part of our journey, but obviously anyone that would suggest we can change a 2,000,000 square foot warehouse into an 85,000 square foot crossdock can’t be seeing the world the right way! (Of course I have to follow that up with one of my favorite quotes one of the VP’s here used….”If it wasn’t for the fact we already did it, we would have said it’s impossible”. Thanks again.
This is the email he is talking about:

Dave and Tony, thanks again for giving the walk through to my 25 advanced lean class students yesterday. Some observations:

I think the floor was about the cleanest I have ever seen it. It is always clean, but yesterday seemed even more so.

The evidence of continuous improvement is amazing. Yesterday I saw a number of things that I did not see in my last visit Feb 10 – new lane structures, hybrid cards, changes in box 2, clearer e-box sheets, new standard work sheets and visuals, etc.

I really appreciate you taking to heart the input I gave you based on the feedback from my last class on the tour structure/agenda itself. The last tour was very good, this one was awesome. The standard work sheet Dave showed me for the tour was great standard work – content, sequence, timing and outcomes were all vividly clear. I asked for more of a focus on the production control system and you delivered on that request. Dave, in your intro, you sounded like me teaching my class (maybe not a good thing?!?).

[…]I was pleased the students had more time to ask more questions. I keep preaching continuous improvement in class and you guys model it which helps give the message credibility in the minds of the students.

The other thing that struck me, which is not new but seemed different for some reason I can’t explain….. You are moving large volumes of freight, […] and the floor is just so calm. There is no panic, no arguing, no anxiety, just people following the processes, getting product from point A to point B, in a quiet, controlled, efficient way. I still remember when I brought the facilities class over last spring, and especially 2 of the folks with lots of work experience said “I never imagined that a warehouse type of environment could actually look like this.”

Your safety performance is stunning. I know the record when I was there was 534 days. Then we had 2 “old-age” repetitive motion injuries in 2 weeks, then you went 600 + days. Now you are at 200+ days. Absolutely remarkable in a tight space with fork lift trucks moving around. 3 OSHA reportables in 4 years, wow.

I clearly remember “that Friday night.” I think we were in there until 10:00 or later. Paul and I had a really good synergistic style, we reinforced each other, and it was an intense experience for whoever was on the receiving end. This was not the last time we took someone through this exercise.

To be sure, it was Earl and his team that did all of the heavy lifting. All Paul and I did was give him a sense of an ideal flow, and challenged them to discover, and overcome, the obstacles between the current state and that vision – one problem at a time, a couple every day.

Amazon.com Gets It

Not many people know that Amazon.com is one of the “places to see” if you are looking for companies practicing the TPS. The fact that their sales and profits are hitting records as most others are scratching and clawing to stay in business is telling.

This recent post by Kevin Kelleher on Gigacom really sums the whole thing up with one sentence quoted from Jeff Bezos’ letter to shareholders:

At a fulfillment center recently, one of our Kaizen experts asked me, “I’m in favor of a clean fulfillment center, but why are you cleaning? Why don’t you eliminate the source of dirt?” I felt like the Karate Kid.

If you have to keep cleaning up a mess, find out where the dirt is coming from.

But the philosophy goes deeper.

If an assembly Team Member is continuously spending time cleaning up threaded holes, go find out how the debris is getting in there (or find a way to keep it out). Go and see.

If you keep losing market share, find out why customers prefer your competitors products. (And don’t sit around a mahogany table talking about it, GO AND SEE.)

Other posts on the same site relate to eBay’s troubles trying to compete with Amazon. The difference, I think, is summed up in a quote from an Amazon executive related to me by someone who was a fly on the wall in one of their meetings:

“At an eBay sellers meeting last quarter, my counterpart was booed off the stage. That is not going to happen here.”

Kaizen is less about the tools than it is an obsessive curiousity about what the next problem is between you and perfection.

Kaizen Express – and the Lean Enterprise Institute

The Lean Enterprise Institute has recently published Kaizen Express, an overview of the classic characteristics of “lean manufacturing” and, by implication, the Toyota Production System. As I set out to review the book, I found myself heading in two directions.

One is the content of the book itself.

Over the years, there have been a slew of books with similar tables of contents that describe the various mechanics and mechanisms observed in the Toyota Production System.

The first really comprehensive reference in English was Productivity Press’s translation of Hirano’s JIT Implementation Manual. (Originally a two volume set priced at $900, it appears it is about to be published in a second edition for around $200. I have not seen the second edition.) Back in the early and mid 1980’s, Hirano was about the only comprehensive reference out there. At Boeing we had internal-use reproduction rights, and many of us poured over those volumes, parsing every word.

Kiyoshi Suzuki’s New Manufacturing Challenge (1987) was the book we gave out to all of our suppliers. It, too, provides a pretty good overview of most of the tools and techniques. It is a good basic reference, and I still believe it really takes about three years for a practitioner to outgrow it.

At a more technical level, we have had Toyota Production System: An Integrated Approach to Just-In-Time by Yusuhiro Monden. This book goes into more depth from a system engineering standpoint, and focuses mostly on “Toyota’s production system” vs. a more generic approach.

These three titles are by no means the only ones. A couple of feet of my own bookshelf is occupied with books covering the same basic topics. I only mention these three only because they have been my workhorse references, especially in the days when I was still putting together my own mental models.

Kaizen Express is well at home with this family. It is a solid overview of the tools and techniques that generally characterize “lean manufacturing” and I can quibble with nothing that is in the book.

The presentation itself harks back to the days when all of the decent references came out of Japan. It is a bilingual book, written in Japanese language and graphic style with English translation along side.

On a sidebar note: As a practitioner, dealing with shop floor people and their sensibilities and values, I would rather use a reference that didn’t come across as so foreign. While I fully appreciate that the Japanese vocabulary is a solidly embedded part of Toyota’s culture, that is not the case elsewhere, and some Toyota-trained practitioners would do well to keep that in mind. The concepts are difficult enough to get across without having to overcome language resistance. Add to that the unfortunate truth that many countries, especially in Asia, still have vivid cultural memories of a far more malevolent Japan, and the resistance just increases. I would not give a copy of this book out in China or Korea, for example. There are others which serve the same purpose without bringing up unresolved issues. Memories and emotions run much longer and deeper in Asia than they do in the West.

All of those reservations aside, this book is a welcome review of familiar material.

Now, the second part. I want to go beyond the book itself, and look at its context. This becomes not so much a review of the book, but one person’s opinion (mine, to be sure) of the state of our communities understanding of the Toyota Production System itself.

The TPS is somewhat unique among all of the various “management systems” in the popular business press today in that it grew organically rather than being explicitly designed. Thus, rather than consult standard documents to learn about it, knowledge comes from research.

In the early days, through the late 1980’s, the topic of “JIT” or “Japanese manufacturing techniques” was a quiet, esoteric backwater of consultants and a few committed practitioners. We knew about Harley Davidson, and some of the other early adopters. Danaher was just getting started, and some of the household name early leaders were starting to gain meaningful experience and reputations. The knowledge base came from practitioners trying to make it work, rather than professional academics who are in the business of developing and testing rigorous theory.

In late 1990, everything changed. The Machine That Changed the World by Womack, Jones and Roos published the results of good, solid research from MIT and became a hot seller. It broke out of the practitioner’s technical corral, got the attention of mainline executives and managers, and introduced the buzzwords “lean production” (which later morphed into “lean manufacturing”) into the lexicon of everyday business.

This was followed by Lean Thinking which profiled a number of these companies and put Shingijutsu on everyone’s radar.

The Lean Enterprise Institute was founded shortly thereafter, and in the late 1990’s published Learning to See and introduced everyone to value stream mapping. This was the first of a series of workbooks designed to take the practitioner through the mechanics of implementing various aspects of the basic elements of modern manufacturing techniques.

These workbooks were something new. Rather than the encyclopedic approach of a single book devoting short chapters to descriptions of the various tools, these workbooks went into much more depth on a single topic, such as materials distribution, creating a work cell, the basics of heijunka or mentoring someone through solving a problem.

In the background of all of this, “lean manufacturing” became the hot topic. Writers, consultants, managers were all talking about how to “get lean” and to “lean out” a business. Hundreds of books were published on the topic, a few of them good, many of them re-hashing old stuff in new ways, a few just using the buzzwords to sell bad information.

This explosion resulted in a lot of noise pollution. What had started as peer-reviewed academic research of the automobile industry turned into the “lean industry” – a crowded, bustling bazaar with everyone hawking and touting their “solutions.” This, by the way, included a mountain of junk academic research.

But there was also some really exceptional academic research, especially out of Harvard. While everyone was busy implementing the tools of lean – the things in the tables of contents of all of those books, the success rate was a far cry from the promise. I have experienced this myself a couple of times. But Steven Spear made it the topic of his 1999 groundbreaking PhD thesis at Harvard. Let me quote, and offer my interpretation, of a few key sentences from the abstract of his dissertation.

Researchers have established that Toyota enjoys advantages in cost, quality, lead-time, and flexibility when compared to its competitors in automotive assembly.

There is no doubt here. It’s why we are all reading this stuff in the first place! And while there was considerable anecdotal evidence before that, The Machine That Changed the World offered up a solid base of good research to confirm what everybody was thinking.

Differences in generating value have been attributed to differences between the Toyota Production System (“TPS”) and alternative management systems. Distinctive tools and practices have been associated with TPS.

Those “tools and practices” are what are covered in the classic books I cited earlier. They are also what is covered in Kaizen Express if not by industry in general, certainly by the community of experts.

However, evidence suggests that merely copying these [tools and practices] does not generate the performance advantages enjoyed by Toyota. This has prompted several questions … [including] … why is it so difficult to imitate?

So we (the community of experts) were happily out the there doing the stuff that was in the books, teaching the basics, trying to implement them, and finding it generally difficult to get a lot of traction once the initial novelty wears off.

Meanwhile, the noisy bazaar continued to churn out more and more “solutions” aimed at the “gaps in lean manufacturing.”

“Lean looks at waste, but doesn’t address variation…” so “Sigma” was spliced in. Yet Toyota obsesses on stability and eliminating variation at levels we cannot even fathom.

“We need someone to implement quality in our lean company.” Hello? How can you leave out quality? Yet in our efforts to implement flow and reduce inventory, we did it all of the time!

We try to bring kaizen into administrative and creative process flows – well enough, but upon finding that the “tools and techniques” need to be adjusted somewhat, people draw the conclusion that there is more to it.

All of these things, over the last ten or fifteen years seemed to make things very complex indeed.

So we go back to the basics.

I agree with the principle. But we need to discuss exactly what the basics are.

The second paragraph of Steven Spear’s abstract is pretty clear:

… the tools and practices that have received attention are not fundamental to TPS.

(emphasis added)

Then he brings up things that the rest of us never talk about:

… the … Rules-In-Use promote distinctive organizational features. These are nested, modular [organizational] structure; frequent, finely grained self-diagnostics; and frequent, structured, directed problem solving that is the primary mechanism for training and process improvement.

(emphasis added) (For explanation of what Spear means by “Rules-In-Use” read the dissertation itself, or Decoding the DNA of the Toyota Production System, which is the HBR summary of his conclusions. Personally, I “got it” a lot better from the dissertation, but then he has 465 pages to make his points vs. 10 pages in the article.)

What has all of this got to do with the little green book, Kaizen Express?

I think it is a great book, for 1991.

But this is 2009. So while Kaizen Express is a welcome refresher of the mechanics, those mechanics are, according to the current standing theory, built upon a foundation of something that Kaizen Express, and for that matter, the LEI has not, to date, addressed. What is missing, in my view, is how the tools and practices outlined in Kaizen Express and its predecessors actually drive daily continuous improvement that engages every team member in the process.

Anyone out there is perfectly welcome to refute Spear’s research and make a compelling case that “the fundamentals” are, indeed, the things addressed in Kaizen Express. But to do so means bringing credible peer-reviewed, published research to the table. It means building a compelling case of documented observations that contradict Spear’s theory. Anything else is simply conjecture.

My challenge to the Lean Enterprise Institute: Your organization is unique. It emerged from the world of academia with very solid credentials, with a great mission to carry this message to the non-academic world. Because of its academic origins, LEI has a real opportunity to be the bridge between the cutting-edge understanding coming out of these top-flight research institutions and translate it into practical things the rest of us can put to use. Extend your charter to taking PhD words like “nested modular structure” and “frequent finely grained self-diagnostics” and giving the daily practitioners some workbooks that lay out how to do it.

Kaizen Express is a great little book.

LEI can do better, though, than to re-publish material that has been out there since 1988.

Back to Basics

The Lean Enterprise Institute is taking up a “Back to Basics” theme.

But what, exactly, are “the basics” of the Toyota Production System?

This is critically important. Permit me to cite an analogy.

Look at a house. What do you see? What would you say are “the basics?”

At first glance, all houses have walls, a roof. They have a door. They are divided into rooms for various activities and purposes. A “basic house” is going to have an entry, a living room, a kitchen, a couple of bedrooms, a bathroom. More complex houses will have more rooms, fancier architecture, higher grades of materials, be bigger, but the basics are all there.

OK, that is a basic house.

I make this point because when people talk about the basics of “lean manufacturing” they talk about the things you can see. If I open up Learning to See, and turn to the “Green Tab” the chapter’s title is “What Makes A Value Stream Lean.” That chapter is primarily (right after the talk about waste and overproduction) a list and description of “Characteristics of a Lean Value Stream.”

  1. Produce to your takt time.
  2. Develop continuous flow wherever possible.
  3. Use supermarkets to control production where continuous flow does not extend upstream.
  4. Try to send the customer schedule to only one production process.
  5. Distribute the production of different products over time at the pacemaker process (level the production mix).
  6. Create an “initial pull” by releasing and withdrawing small, consistent increments of work at the pacemaker process. (Level the production volume).
  7. Develop the ability to make “every part every day” (then every shirt, then every hour or pallet or pitch) in fabrication processes upstream of the pacemaker process.

Now I have to say right now that I have always loved this chapter. I cannot count the number of people I have referred to “The Green Tab” as a fundamental primer. It includes all of the basics, just like our house.

In their latest book, Kaizen Express, the LEI has brought out some more detail on these same points, and added a few “rooms” to the house. One critical aspect they add is various topics that add up to quality. (It’s kind of like leaving out the kitchen or the bathroom if you don’t mention that.) They talk about zone control, line stop, and countermeasures to quality problems. (I will do a full review on this book soon.)

Then on page 99 starts four pages on Employee Involvement where they talk about practical kaizen training (PKT), and suggestion programs.

Let’s go back to our house. The things we said were “the basics” were the things you see when you look at it from the street, and go inside and walk around in it. But in an industrialized country, the modern single family residence is a miracle of accumulated knowledge and technology. The basics are the things that keep it from sinking into the ground, from catching on fire, from leaking and rotting. They are the things you can’t see, but unless you understand them, your house may look like the one next door, but it won’t perform like the one next door.

I have been in dozens of factories that had takt time, some semblance of continuous flow, pull systems, supermarkets, all of that stuff. They had run hundreds, maybe thousands, of kaizen events, and had suggestion programs. All of these things were visible just by walking around.

Yet most of them were stuck. They had reached a point when all of their energy was being expended to re-implement the things that had slid back. Three steps forward, three steps back.

They had read Ohno’s book, they knew the history of the Toyota Production System. They understood all of the engineering aspects of the system, and could install very good working examples of all of it.

But something wasn’t there, and that something is the foundation that keeps the house from sinking into the ground. It is the real basics.

Kaizen Express hints at it on pages 99 – 102, it is true employee involvement. And here is a real basic: Employee involvement is created by leader involvement. Not just top leaders, all leaders, at all levels.

To be honest, a lot of technical specialists don’t like that very much for a couple of reasons. First, engaging the leaders, at all levels, is really hard. It is a lot easier to get things done by going straight to the gemba and doing it ourselves – we show people how to do it, we “engage” them in the initial implementation, and everything is wonderful for the Friday report-out.

But I contend that the foundation of the Toyota Production System is the leadership system. It is the system of leadership that holds up all of the walls that we call takt, flow and pull. Those things, in turn, enable the leadership system to function better. The “characteristics of a lean value stream” evolved in response to the leadership system, in order to strengthen it. It is a symbiosis, an ecosystem.

“But it didn’t start out as a leadership system.” No, it did not. The history of how the Toyota Production System evolved is well documented, and the leadership system was less designed than it evolved. But let’s go back to our house analogy.

Primitive houses only have the “basics” I described above. They don’t have sophisticated foundations, some are just built on skids (if that). But because they lack the basics, most of those primitive houses don’t last.

And there is the paradox. When we say “back to the basics” we cannot only refer to the chronological history of how the system developed. We have to take the most successful, most robust example in front of us today, and we have to look at what fundamental thing holds this thing up and lets it grow more robust every day.

So let’s take a look at what Toyota teaches when they teach someone the basics.

The article Learning to Lead at Toyota was written back in 2004, but I still feels it offers a lot of un-captured insight into the contrast between what Toyota thinks are “the basics” and what most others do. I want to encourage everyone to get a copy, and not just read it, but to parse it, study it, and use it as an “ideal condition” or a benchmark. Compare your “lean manufacturing” and your leadership systems to what is described in here. Ask yourself the question:

Do we really understand the basics?

Note: There are now links to my study guides for Learning to Lead at Toyota on the Resources page.

Is Quality Losing to Cost?

Tom posed an interesting question on The Whiteboard.

Has anybody else noticed that quality is taking a back seat lately due to the tough economic conditions? Things are tough everywhere, but I’m seeing more and more evidence of companies taking short cuts (to cut costs) where the end result is poor quality.

I’ll say what I think, but I would also like to invite anyone else to comment as well. This is an important issue.

Background:

First, it is important to understand that the term “quality” carries at least three definitions. There may be more, but here is how I came to understand them.

  1. Grade: The product’s position in the market.
  2. Fitness for use: Whether the product is suitable for the customer’s intended purpose.
  3. Conformance to specification: Whether the product is as the producer intended it.

Some examples.

Grade:

In air travel, there are two (and sometimes three) grades of service offered on a typical flight. Coach is basic transportation. It gets you there quickly and safely. First Class gets you there just as quickly and just as safely as coach. But there are more amenities offered, the seats are bigger, in general it is more comfortable. First Class is a higher grade of product.

In the automobile market, we have expensive luxury cars, such as top-end BMW or Lexus. We have middle grade cars, we have basic cars. Even within a specific make and model, there are different trim levels that each carry a different “feel” as well as a different price.

Thus, the grade of the product reflects an effort to create higher value by adding features and amenities that probably go above and beyond the basic purpose.

It is important to understand that the grade of the product is set by the producer’s decisions on market position. They are trying to deliver more value in order to command higher prices.

Fitness for Use:

Fitness for use is defined from the perspective of the customer. The product is sold as being suitable for some purpose, and the customer buys it to fill a need. How well it fills that need is ultimately defined by the customer’s experience of the product in use. This is probably the easiest to screw up, as many companies tend to rely on internal experts or the highest-paid-person’s opinion rather than getting their shoes dirty and actually paying attention to what customers do with the product. It is easy to delete or alter a feature which turns out to be very important to the customer. Customers can also surprise you and find uses which were never intended by the original design.

Conformance to Specification:

Once the research is done, and the product designed, some kind of production system must be established to actually produce the product (or actually deliver the service, it is the same issue). Conformance to specification defines how well the product delivery actually matches the design intent. Where a Hilton Hotel may offer a higher grade of room than Motel 6, if both rooms are clean, ready for guests, and meet their respective hotel’s standards, then both conform to specification. The Hilton will have some kind of specification for how they deliver room service. Motel 6 has a Denny’s next door.

One More Example

If I am interested in knowing what time it is, a $35 Timex will do exactly the same job as a $5000 Rolex. With today’s quartz technology, they are both accurate within a second or two per month. So if knowing the time is my intended use, both watches are fit for use.

Clearly, however, there is a difference. The Rolex is a higher grade of product than the Timex. If my purpose is to demonstrate wealth or success, or present an extravagant gift, the Rolex is also more fit for that use.

But if they each work out of the box exactly as intended, have no scratches or other defects, then both watches conform to the specifications of their respective manufacturers. Both companies have excellent reputations for “quality” in that sense.

So now to Tom’s question.

Companies facing dramatically declining sales are under great cost pressure. Very few have limitless sources of cash to burn, and publicly held companies must also maintain the goodwill of their investors. In addition, many companies have credit covenants which require them to maintain certain ratios of debt, liabilities, assets, liquidity, etc, or face issues with their banks.

With that background, let’s look at how these pressures could drive decisions that affect quality.

Deliberate decisions are most likely to affect grade. Cheaper materials may be substituted, amenities or extra services can be cut back. Anyone who flys frequently has seen the steady erosion in previously “free” services and amenities as airlines come under increasing cost pressure. The danger here, of course, is that these decisions also reduce value in the eye of the customer, and with that, can reduce the price they are willing to pay or send them to a competitor. Thus, these “savings” can end up backfiring unless the entire industry is following pretty much the same path.

I think the more dangerous effect of turbulent times, however, is in the area of conformance to specification. But I don’t think this is the result of deliberate shortcuts. Rather, I think it is an unintended consequence at the intersection of a couple of other factors.

First, relatively few companies, be they production and manufacturing or service delivery, have an effective system of assuring that things are done the way they expect. When times are good, and employment is stable, the people develop their own individual feel for what is right and do their very best to do it. The level of quality will reach some kind of tolerable norm which may, or may not, conform to the specification.

Now mix things up. Lay off some of your workers, and move the others around. Different people are doing different jobs. Because the work is not well specified in the first place, and because there is likely no process to transfer “how to do it” (like TWI Job Instruction), people have to learn the hard way – by making mistakes. Add to the mix a perceived time pressure, and people will take shortcuts in a good faith effort to get the job done the way they think they are expected to.

If the “specification” itself is poorly defined as well, then the new “norm” for the organization could very well end up different (and worse) than what it was before. Add to that a management culture of acceptance of “what is, is” (an excused-based culture, more common than you think, especially in large companies), and you get a seeming erosion.

So here’s what I think – if Tom is seeing an erosion of quality, he is likely seeing the effect of the economic turmoil rather than deliberate decisions to cut corners. Further, is impossible to deliberately cut corners if no one has ever defined where the corners are in the first place. And that situation is more normal than not.

What is your view?

Do you see quality eroding?

If so, why do you think it is happening?

Reprise (again) – Know Your Supply Chain

AP IMPACT: Chinese drywall poses potential risks

Although I hate to judge before all the facts are in, it’s beginning to
look like a huge set of customers got burned (once again) by quality problems from China.

Before I go any further, I have to say that I have spent loads of time in China. I have very close Chinese friends. The Chinese are like everyone else in the world – hard working honorable people. But, just like everywhere else in the world, now and then someone takes shortcuts with known technology, or doesn’t understand the “Why?” behind industry standard practices, and rarely, there is a real crook.

The great question, though, is “To what degree are the importers, builders and contractors culpable, and to whom?”

The U.S. arm of the Chinese company is swearing up and down that their product meets U.S. standards. Pretty standard rhetoric for muddling the issue.

I don’t even want to get into the legal issues here. They are going to be very messy.

But if you bought a car, and it turned out that the imported, outsourced seats were emitting noxious fumes, I doubt you would turn to the seat manufacturer to resolve the problem.

OEM’s? Know your suppliers, know your supply chain.

Unfortunately we will end up with a ton more government regulation as a result of industry being unable or unwilling to assure its own quality, and that is going to cost all of us.

Kind of makes the term “toxic assets” more real, doesn’t it?

John Shook: Purpose, Process, People

Like many of us, John Shook has been commenting in his column about GM at a precipice seemingly of its own making. One of the questions he has addressed in a couple of columns is “What did GM learn from NUMMI?” or perhaps more precisely, “Why didn’t GM learn from NUMMI?”

John’s latest column, titled Purpose, Process, People, points out rather bluntly:

My answer to that question remains that GM actually learned far, far more than most people realize about process but didn’t get very far with the people part.

In an earlier column, John raises the possibility that perhaps GM and Toyota each view the world through different lenses of vastly differing purpose (what I could call core values, the things that aren’t written down, they just are within an organization).

Yes, GM wants to survive — hence the humbling appearances on Capitol Hill by Wagoner and the two other Detroit CEOs. Yet had GM been seeking long-term survival a la Toyota, it would have made different decisions all along. GM wants to survive, all right, it wants to survive so it can continue to make money. Toyota on the other hand, wants to make money to survive.

Think about that: Toyota makes money to survive; the Detroit 3 exist (survive) to make money. Those contrasting senses of purpose will take you down very different paths.

This conclusion lines up perfectly with GM’s behavior regarding their NUMMI opportunity.

…  And so it went — Toyota running NUMMI operations, GM selling Novas while dispatching people to NUMMI to learn.

… [by 1994] at least, GM still didn’t know how to make a small car profitably and still didn’t understand TPS. And here we are today. So the question remains: why not?

Why not indeed?

So we have a situation where Toyota is running a GM car plant, building an excellent small car. GM seems to have been treating it as a factory, with an ROI, rather than for what it really was: A learning laboratory for the GM as a whole. Yes, they sent thousands of GM people there “to learn” and then brought them back into their old work environments and what? Somehow expected these smart people to transform the company?

Here is what I think happened.

NUMMI was a factory. So who do you send to a factory?

You send factory managers. You send line managers. You send supervisors. You send people who have jobs in a factory so they can work with their NUMMI counterparts and learn from them. Makes perfect sense, doesn’t it?

And, as a sidebar to all of this, what was Toyota learning? They were learning how to transplant the TPS outside of Japan. They were learning how to teach their system to people who didn’t grow up in it.

Let’s look at the process Steven Spear outlines in Learning to Lead at Toyota. In this case, an experienced, seasoned senior leader comes from a U.S. auto company to Toyota. They need to teach him “how to lead at Toyota” and they need to do it reasonably quickly.

They don’t sit him down to Death By PowerPoint orientations. They don’t have him go through the financial. (at least not right away). They don’t put him in classes. And most importantly, they didn’t have him shadow another factory manager to “learn the job.”

Instead, they send him to the shop floor to, essentially, learn to be a Team Leader – a senior hourly Team Member. He has to un-learn how to provide the answers, and learn how to guide people to their own solutions. He has to learn to let go of the goals and targets and understand that those goals belong to the Team trying to meet them, not the boss. His job is simply to help them push their capabilities.

So what would it have taken for GM to have a chance to “get” what the Toyota System is all about?

Where was Roger Smith? Where were the other executives from Detroit? Ironically, this time period really marked the beginning of GM’s decline. My conjecture was that NUMMI was “a factory” and these senior corporate leaders felt they had nothing to learn there that could not be picked up with a tour and a briefing. It was profitable, they were sending “their people” to learn why. Good ‘nuf.

Actually, this pattern happens in nearly every “lean manufacturing implementation” out there. The senior leadership is “committed” to the point where they are willing to hire the experts and have them teach people how to “be lean.” But, in truth, this is about changing the way the company is run. Very few “lean implementations” succeed without a transition in top leadership. Of those which do succeed, few of them survive the next leadership transition unless that person was carefully developed within the system.

Kaizen is a process of learning, and only people can learn.


4S, 5S, 6S

Staight left an interesting post on The Whiteboard a couple of days ago:

You’ve discussed 5S but Novaces, for example, has a 6S system. I think it would be great if you talked about different consultant companies and their processes.

Novaces, it turns out, is a consultancy apparently based out of New Orleans. In the nature of full disclosure, I have to say that I know nothing about them other than what is on their web site plus they (apparently) teach 6S rather than 5S. I render no opinion either way about their competency or capability.

There are a lot of good consultancies out there. There are a lot of mediocre ones. There are some that are charlatans. I suppose one of the great ironies of the business is that, if you are capable of reliably vetting them on their competency, you probably don’t need them in the first place.

For the sake of the discussion, though, I want to limit myself to the population of really good ones. These are the ones who are primarly there to teach the clients how to engage in the kind of sharp critical thinking that charactarizes high-performance organizations.

The good consultancies will have an approach that applies the same principles. And here is the key point:

As long as the basic principles of the thinking structure get embedded, it really does not matter that much how they do it. If a consultancy wants to differentiate itself by using 6S, or 4S, instead of 5S, there is little difference in the result if they are any good.

Let’s take the different numbers of ‘S’ and really take a look at why this is true.

Though they may have adapted 5S today, originally (a long time ago) Toyota taught 4S. The idea of “self discipline” or “sustaining” didn’t come into it because that was embedded thoroughly in the culture. It was taught elsewhere.  Likewise for safety. It isn’t that they leave it out because they didn’t have it called out as an ‘S’, they just include it somewhere else.

What is the 6th S? I don’t know what Novaces uses, but I have most commonly seen it as Safety. It isn’t a bad thing to include it, but in reality, as long as relentless daily problem solving is applied to safety issues somewhere, somehow, there isn’t a right or wrong way to teach it or do it.

Some consultants claim to “fill in the gaps” of “lean manufacturing.” They add hyphens or create three letter abbreviations to differentiate their product. Because the term “lean manufacturing” originally referred to the observed results of the Toyota Production System, and not the system itself, there is a lot of room to make claims that it leaves things out because the method was never really defined in a holistic way.

“Lean manufacturing” not withstanding, IF you stipulate that “lean manufacturing” is the “Toyota Production System” and then understand that, to Toyota, this is their entire management system – it encompasses everything they do – then to claim “lean manufacturing” has gaps is to claim that Toyota somehow leaves something out. I don’t think so. Sure, they slip up like everyone else, but their management system is pretty thorough.

For example, I have heard things like “we are lean, now we need quality.” Hello? If you aren’t obsessive about quality, if you aren’t applying immediate detection, stop, correction and countermeasure investigation to every quality problem, how can you possibly claim you are “lean?” If you aren’t doing these things, you are just making defective goods very efficiently.

But I also understand that there ARE companies that think they have implemented lean, and have totally left out the quality component. So if it makes sense to them, (the customer) to find a consultant to help them “fill in the gap” then great. They still get there.

And that is the point. Getting there.

One last point. To get there you have to pick a course and stick with it. What trips up a lot of companies is they get to the point where they are “stuck” without examining (in the mirror) the factors that are causing it. Instead, they switch course, and say “AH! It must be Theory of Seven Sigma” that will get us there. But in reality, because all of these approaches require a change in the way everyone thinks, without that fundamental shift, they end up in the same place a little later…

Cause remember, no matter where you go… there you are.