Embracing Challenges for Success: Lessons in Toyota Culture and Kaizen from Nate Furuta


I have been really enjoying this book, released in 2021, by Kiyoshi “Nate” Furuta, a retired Toyota executive: Welcome Problems, Find Success: Creating Toyota Cultures Around the World. I bought it a year ago and wish I had started reading it sooner!

Furuta is the retired former chair and CEO of Toyota Boshoku America, Inc. — an automotive parts supplier to companies including Toyota and General Motors. As it says on the company's website:

“…we take pride in being a company driven by quality and kaizen (continuous improvement).”

The company was founded by Sakichi Toyoda in 1918. You can also read about their “TB Way.”

Furuta was the first Toyota employee at the NUMMI joint venture between Toyota and GM. He was also the first Toyota employee at the Toyota plant in Georgetown, Kentucky. He has a very unique perspective on “creating Toyota cultures around the world,” as the book's subtitle says.

There are two things in particular that jump out at me enough to share in this post.

A Classic Taiichi Ohno Story

First is a story about the legendary Taiichi Ohno and one of their factories in Japan. Ohno was given data that showed that a long-troubled crankshaft line had some “surprising improvement” after it “repeatedly had problems delivering on time.”

Even though that sounds like great news–what was there to investigate??– Ohno went to the “gemba” to go and see (“genchi genbutsu”). He was looking for facts, not just data. He wanted to know how that improvement had occurred, something that a “management by results” leader might not care to explore. Ohno wanted to know what could be shared elsewhere.

What did he find?

“Carefully examining the line, he realized that a manager had secretly built and hidden excess safety stock to cover up for the line's habitual delivery problems. Mr. Ohno was, of course, furious that inventory was being increased rather than the real problem solved, and decided to take dramatic action.

He ordered employees to bury the excess stock on the plant grounds. After he gave his order and left, the manager persuaded employees to again hide the excess.

It didn't take long for Mr. Ohno to find the excess stock once again, and this time he ordered it destroyed before his eyes.”

Ah, building up safety stock to buffer against production downtime instead of fixing the root causes of that downtime. That's what I lived through during my first year working at a GM engine plant in 1995 (they also made crankshafts and other engine components). Supervisors had old habits of wanting to “buffer” everywhere and anywhere, by pulling parts off of the line any time a machining station went down. This often created awkward, if not dangerous, conditions for production workers. That wasn't showing “respect for people,” in a Toyota way.

I chuckled when I read about Ohno ordering them to bury the parts. I could also understand why the manager and employees wouldn't want to do that. It's pretty hardcore that Ohno later ordered that inventory to be destroyed.

Hear Mark read this post — subscribe to Lean Blog Audio

What I Saw at GM

During my time at GM, having the buffer stocks wasn't generally shameful. But it led to quality problems because sometimes an engine block that had been pulled off the line after “Operation 30” had to be stored somewhere off to the side. It should have been loaded back onto the line before “Operation 40,”… but sometimes people made a mistake and loaded the part onto the conveyor belt before “Operation 50,” which meant the part or parts had now skipped Operation 40… and that was a quality disaster.

The only shame about buffered parts was the holding of scrapped (defective) engine blocks on pallets. Eventually, the cost of that material would have be written off. But managers didn't want the defects to hit the books, so they played a game of hiding the inventory. I don't think anybody ever thought to bury the parts.

Cultivating Trust and Safety at NUMMI

In the book, Furuta writes extensively about creating a problem-solving culture. However, while I was reading, Furuta didn't mention the need to help team members feel safe admitting problems, pointing them out, or sharing them.

It seems like “psychological safety” is something that is a bit taken for granted at this point in Toyota's history, although it was called out specifically by Jeff Liker and Mike Hoseus in their book, Toyota Culture, as I wrote about here:

As Furuta wrote, managers need to not view problems negatively. It's implied that employees won't get in trouble for pointing out a problem or sharing an improvement idea. Furuta writes a lot about “mutual trust and respect,” as covered by Toyota people in other books.

But this story from NUMMI–where they needed to change the old culture from when that building housed the GM Fremont plant–starts to piece it together:

“The new Fremont management trusted members enough to let them pull an andon cord, which quickly illuminated that a problem existed and, not without consequence, stopped the production line (a stopped line can result in thousands of dollars of losses per minute).

Management promised employees they would have the ability to stop the line if they encountered a problem, and management stuck to that promise. We told them that a member was responsible for pulling the andon cord to alert management of a problem, and the line would stop if the problem could not be fixed immediately.

Workers then started trusting their bosses enough to ask for help by pulling the andon cord when there were problems. A team leader, who was a union member, would attempt to fix the problem before the situation warranted the line to stop.”

There we have it:

  • Management trusted the team members…
  • Therefore, team members started trusting management

The team members learned that management wouldn't scream at them for potentially stopping the line (or part of the line).

Psychological Safety and Problem-Solving

Pulling the andon cord requires two things:

  1. Psychological Safety (I won't get in trouble for doing so)
  2. Problem-Solving (I would get discouraged if problems didn't get fixed)

Furuta writes about the need to address culture before teaching a lot of Lean tools. It seems to start with:

  • Mutual trust and respect
  • Psychological safety
  • Problem-solving
  • Then, advanced Lean tools

How many organizations focus on the fancy or exciting Lean tools without first building a culture of PDCA / PDSA problem-solving? And how many companies have spent a lot of time training people on problem-solving without first focusing on psychological safety, to help people feel safe enough to point out problems to begin with.

Read more about Andon cords at Toyota:

As Furuta says often in the book (and ends the book):

“No problem, no kaizen.”

Please check out the book. I'd love to perhaps run an online book club about it.

What do you think? Please scroll down (or click) to post a comment. Or please share the post with your thoughts on LinkedIn – and follow me or connect with me there.

Did you like this post? Make sure you don't miss a post or podcast — Subscribe to get notified about posts via email daily or weekly.

Check out my latest book, The Mistakes That Make Us: Cultivating a Culture of Learning and Innovation:

Get New Posts Sent To You

Select list(s):
Previous articleGE Aerospace CEO Larry Culp on a Finger-Pointing Culture and a Better Alternative
Next articleWebinar Preview: From Lean Theory to Practice in Libraries and Beyond
Mark Graban
Mark Graban is an internationally-recognized consultant, author, and professional speaker, and podcaster with experience in healthcare, manufacturing, and startups. Mark's new book is The Mistakes That Make Us: Cultivating a Culture of Learning and Innovation. He is also the author of Measures of Success: React Less, Lead Better, Improve More, the Shingo Award-winning books Lean Hospitals and Healthcare Kaizen, and the anthology Practicing Lean. Mark is also a Senior Advisor to the technology company KaiNexus.


Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.