WLEI - Lean Enterprise Institute’s Podcast

TPS Taken to Companies across the UK

Simon Rowley and Julian Ball join Josh Howell, LEI President, and Mark Reich, LEI Chief Engineer Strategy, and continue this month’s discussion about the role of continuous improvement (CI) groups in lean management. Simon is Senior Manager at the Toyota Lean Management Centre (TLMC) in the UK, and Julian is Section Manager. TLMC was started by Toyota Motor Manufacturing UK in 2009 to support companies in the UK interested in implementing the Toyota Production System (TPS). 

The two TLMC executives describe the startup of the center and how it initially enabled Toyota UK to employ and improve staff during a financial downturn. “They saw this as an opportunity for development of their own people, going out to clients and helping them and coaching them in TPS and the Toyota Way, develop them to then go rotate back into the business and make our business stronger,” says Julian. The best way to get better at TPS, adds Simon, is to practice, and TLMC offers team members opportunities to practice with diverse industries, people, problems, and environments. 

On the podcast Simon and Julian also talk about: 

• Training programs they bring to clients in the UK, including Rolls Royce, and their work in industries beyond manufacturing, such as healthcare, pharmaceuticals, and high tech. “The thinking way can be implemented into all of these sectors,” says Julian. 

• The approach of TLMC team members with clients compared to staff at Toyota’s internal CI group, the Operations Management Development Division (OMDD): “When we’re here at Toyota and having a discussion about TPS, it’s OK to assume that everyone has some level of knowledge and you can start using terms and think of activities you’re going to do and everybody is kind of on the same page,” notes Simon. “If you go to an external enterprise, first of all you have to change the way you communicate to people.” 

• Advice for companies new to TPS and wanting to get started with improvements: get at least some advice from a lean expert, don’t get too ambitious when starting with lean, begin small in an area and with people who have expressed an interest in lean improvements, make sure of who needs to be on board to make it work, and don’t worry about getting it wrong. 

• People development and TPS: “Unless you’re developing your people in your organization, you’ll never maximize the potential of TPS, you’ll get just little bits of improvement,” says Simon. 

• The importance of standardized work: “Standardized work allows us to build high-quality vehicles safely every single cycle,” say Julian. “The other part of that is it’s the members’ safety net. We’ll train you how to do something and, of course, if you do it this way every single time you will stay safe and you will build that quality vehicle. We’re avoiding any of these conflicts of who did it wrong and why didn’t you do it like this. We just follow the standardized work... If I work this way, I can’t do anything wrong.” 

Want to take these ideas further?  

Go beyond the page and see lean leadership in action. The Lean Leadership Learning Tour (Nov. 10–13, 2025) takes you inside Toyota, GE Appliances, and Summit Polymers to witness real-world problem-solving, leadership development, and transformation at scale. Bring a colleague, align your vision, and return ready to accelerate change.  

Learn more » 

A Toyota Take on Taking TPS to Others

Josh Howell and Mark Reich, LEI President and Chief Engineer Strategy, respectively, speak with Jamie Bonini, President of the Toyota Production System Support Center (TSSC), a not-for-profit corporation affiliated with Toyota Motor North America. Since 1992, TSSC has shared Toyota know-how with more than 500 small- to mid-sized companies, government entities, and non-profits.  

This week’s discussion kicks off a month of The Management Brief content around the role of continuous improvement (CI) groups in lean management. As the leader of TSSC, Jamie interacts with many organizations’ CI groups as they apply basic concepts of the Toyota Production System (TPS) and helps others develop CI groups for that objective.  

Prior to Toyota, Jamie worked at Chrysler and DaimlerChrysler, spending a decade applying TPS there and believing he understood it well. “I was absolutely stunned and amazed by how much more there was to TPS than I was able to learn by reading externally and even working with former Toyota people that were helping us when I was at Chrysler and DaimlerChrysler.” While at TSSC he’s found there is often a similar big gap in what those outside of Toyota think of TPS — frequently narrower than the Toyota approach of developing “a culture of highly engaged people that are solving problems and innovating to drive performance.”  

On the podcast Jamie discusses: 

• Toyota’s internal CI group: Operations Management Development Division (OMDD) works with plants, suppliers, logistics, dealers, and other entities connected to Toyota for TPS support work and to develop people (“TPS is 80% hands-on learn by doing, experiential learning, it’s learning through practice,” says Jamie). OMDD also will be involved by adding resources needed for quick-hit plant changes as well as new plant design and layout. 

• Differences between OMDD and TSSC: OMMD focuses mostly, but not exclusively, on the technical tools and practices of TPS because the Toyota Way philosophy and the managerial roles and structures are regularly reinforced throughout the automaker and its partners. Outside of Toyota, TSSC must address not only the technical side but the philosophy and managerial aspects (design of the organization) of TPS. 

• Perspective of CI groups: When Jamie started with Chrysler, just as TPS and lean was becoming known, most organizations did not have CI groups. Today most have established some form of CI group, and “now the need for that function is recognized and staffed.” The CI groups today, however, typically are a training and coaching support function (needed and helpful), “but, in most cases, I think more can be done.” There is an overemphasis on “tools to be installed” and not enough emphasis on a building a culture of highly engaged people to solve problems and working with very senior leaders to solve problems.  

• Building capability in leaders and managers: As TSSC works on a nine- to 12-month pilot project with an organization to achieve a specific business result, it’s also developing leaders who can then sustain and spread TPS. During that time senior executives undergo a three- to four-day workshop where they solve actual problems on the frontline and learn how to coach problem solving. “Almost all the time we get the same feedback, which is, ‘Wow. We have a lot more problems out there than I had realized that can be solved. There’s a lot more improvement tension than I realized. This problem-solving method is pretty simple ... but the actual practice is difficult. If we want our people to be able do this type of problem solving on a regular basis, we’re really going to have to provide management that is going to support and develop them in that.” 

Innovation as a Core Capability: Sebastian Fixson on Why Leaders Need Lean Product and Process Development

In this episode of the WLEI Podcast, we speak with Sebastian Fixson, PhD, of Babson College, on mentoring the next generation of leaders in lean product and process development (LPPD). Sebastian is the founding faculty director of the doctor of business administration) program and professor of innovation and design, at Babson, where he focuses on helping people and organizations build innovation capabilities. 

Jim Morgan, senior advisor on LPPDat LEI, joins Sebastian and me for this wide-ranging conversation in which we discuss: 

• How to get emerging product leaders to slow down and leverage LPPD to build stronger teams and better businesses 

• How engineers can use LPPD to become more effective business leaders by understanding how the larger business works  

• Sebastian’s advice to product leaders on how to understand both the physical and digital side of the business (as well as how LPPD supports this effort) 

• How to build “process thinkers”, not just product development leaders 
• Where Sebastian sees hope for innovative product development processes, organizations, and/or new ways of working to solve global challenges 

 

Get Started with Lean Product & Process Development  

Improving how you develop and deliver products doesn’t require a full transformation to start—it begins with learning to see problems clearly, involve your team, and improve how work gets done.  

Explore your next step:  

• Read Designing the Future or The Power of Process  

• Take the 60-minute Lean Product and Process Development Overview course  

• Join the coach-led online Designing the Future Workshop for hands-on practice, and the in-person Introduction to Lean Process Development course Oct 7  

• Bring a coach into your organization for customized support  

Let’s take the first step—together. Learn more at lean.org/LPPD » 

Learnings of a Lean Pioneer

Jim Lancaster, Owner and CEO of Lantech, talks with Josh Howell, LEI President, and Mark Reich, LEI Chief Engineer Strategy, about his lean journey and the decades-long transformation at his packaging-solutions company. Lantech, a lean pioneer, was highlighted in Jim Womack’s and Daniel Jones’ 1996 book Lean Thinking, and has steadily improved, growing the business 75% since 2020 despite economic and market factors that have derailed other companies.  

Jim, author of The Work of Management, started at Lantech in high school when his father, Pat, was CEO. After college he worked in the financial industry, and then came back to Louisville to help run the family business. “I was very involved [as a participant] in the very first part of the lean transformation that we made back with Shingjutsu and consulting firm TBM way back in the early 90s... I grew up in the sales side of our business for the first four or five years before taking over and running the company in 1995, which is when I really started leading the charge on lean as opposed to just participating in the workshops... I’ve been around [lean] since the early 90s, for a really long time through its various terms and various epics. The core principles have not changed, and the value has not changed.” 

In this frank, engaging conversation, the trio discuss: 

• Jim’s growth as a lean leader and how important it is to bring others along in their learning, giving them the confidence to make change, especially as Lantech grew and he could no longer be personally involved with every process and problem.
• The need to accumulate incremental improvements and prevent successes from deteriorating so that each “chunk” of improvement adds to what has already been accomplished.
• Lantech’s management system, which consists of a problem-escalation process; 90-day rolling averages for quality, cost, delivery, and safety, with performances compared daily to trigger problem-solving; and process improvements using A3s and key task monitoring.
• The power of experiential learning, especially as changes fail and individuals “stub their toe” and cope with difficulties, and, as a leader, the need to patiently let them face their frustrations and work to “see the problem differently.” 
• How the company survived the pandemic and had to reteach many lean principles to get over the necessary workarounds that were put in place to get through COVID. 

Tech Founder Mari Zumbro on Building High Trust Online Communities and AI in Product Development

In this episode of the WLEI Podcast, we continue our series on AI in product development with an interview with Mari Zumbro, Co-Founder and COO of the tech startup Filament. An active participant in the open-source community, Filament describes itself as a new communication platform with the goal of accelerating global innovation with leaders who are thinking deeply about “how different communities and organizations can mutually benefit and look for arrangements that benefit the public good.” 

In this conversation, we discuss:  

• How to build high-performing product development teams that effectively leverage AI to achieve exceptional results. 

• What it takes to create work cultures where teams feel “safe to create.” 

• Why “product development is a team sport.”  

• The larger benefits and hidden problems of AI, including its impact on the environment. 

• Leadership behaviors and practices that keep teams in a generative space, putting people before AI and keeping them at the center of work design. 

Transforming as a Problem-Solver

Josh Howell and Mark Reich, LEI President and Chief Engineer Strategy, respectively, speak with Scott Heydon, former VP of Global Strategy at Starbucks, McKinsey & Co. consultant, and a Senior Lean Coach with LEI since 2014. They discuss Scott’s efforts to transform Starbucks with lean thinking, learning lean methods and new ways of problem-solving along the way, and how he’s taken that knowledge to other organizations.  

 

Scott says at Starbucks he evolved his own problem-solving from that of a top-down, MBA-style focused on financials and strategic analysis to include a recognition of problems from the bottom up and a need to develop the capability of others to incrementally improve and problem-solve at the local level to “get better every day.” His work at Starbucks included a four-store lean experiment, which involved then Starbucks colleague Josh and was eventually expanded across the coffeehouse chain. The effort was revised midcourse, says Scott, as his programmatic approach shifted to a better understanding of the processes and problems that need to be solved specific to individual stores and asking store leaders, “What problem are you trying to solve?” 

 

Scott offers two pieces of advice for those in leadership positions progressing with their own lean learning and working to develop and support others who are learning with them: 

• “Spend more time where the work happens. That can be challenging as a leader because people will operate differently” and the perspective viewed may not always be authentic. Scott worked in a local store as a barista for a few hours each week, and told people on the line he was trying to learn and was not there to judge. It also helped that he had an idea of what to look for, a key skill learned from LEI coach Jeff Smith while at Starbucks.  

• Turn off the problem-solving in your brain as you talk to someone, and instead ask questions to learn from them about what they are doing and ask questions that can help them become a better problem-solver. “To develop that capability in others and to create improvement by supporting others is a really important capability for leaders.” 

 

AI to Empower People: Fabrice Bernhard on Using AI to Improve Product Development

In this episode of The Design Brief, we speak with Fabrice Bernhard. Fabrice is cofounder and chief technology officer of Theodo, a leading tech consultancy in Europe, and coauthor of The Lean Tech Manifesto. Fabrice discusses what it takes to create great digital products, how high-performing teams can use AI with care, and how LPPD (lean product and process development) thinking works with generative AI to strengthen businesses and teams. 

The conversation explores:  

• What intentional use of AI in product development looks like (while keeping human beings at the center) 

• Where Fabrice and his team have focused their energies helping companies make the digital transformation 

• How AI helps teams practice the LPPD principle of “building in learning and knowledge reuse” to create better products 

• How business leaders can use AI to “translate” legacy systems into the modern systems we need to do value-creating work now 

• Common pitfalls leaders run into when experimenting with AI in product development 

Get Started with Lean Product & Process Development 

Improving how you develop and deliver products doesn’t require a full transformation to start—it begins with learning to see problems clearly, involve your team, and improve how work gets done. 

At the Lean Enterprise Institute, we help organizations: 

• Focus on customer-defined value 

• Reduce delays and rework 

• Build learning into the development process 

• Align people, processes, and purpose 

Whether you're exploring Lean for the first time or want to improve your development system, we’ll meet you where you are. 

Explore your next step: 

• Read Designing the Future or The Power of Process 

• Take the 60-minute Lean Product and Process Development Overview course 

• Join the Designing the Future Workshop for hands-on practice 

• Bring a coach into your organization for customized support 

Let’s take the first step—together. Learn more at lean.org/LPPD » 

The Toyota Triangle and Problem-Solving

Josh Howell, LEI President, and Mark Reich, LEI Chief Engineer Strategy, join Olivier Larue, President of Ydatum, and discuss the Toyota Production System (TPS), the three elements embedded within TPS that make it more than just a production system, and the ability of TPS to foster problem-solving and creativity. Olivier worked with Mark at the Toyota Supplier Support Center (TSSC) in the late 1990s and has led Ydatum since 2000, assisting companies in implementing its version of TPS. Olivier recently authored the first of three volumes of The Toyota Economic System, which will present the three elements of the “Toyota triangle” — philosophical, technical, and managerial — and their necessity in making TPS an economic system for growth. 

TPS has enabled mass production to accommodate customization, which had been minimized in the pursuit of lower costs for large quantities of standardized goods, says Olivier. TPS allows companies to “build a product affordably and very much customized to the desires of the customer, one without compromising the other.” Yet when attempting to apply TPS it remains difficult for many organizations to simultaneously achieve the primary goals of TPS — highest quality, lowest cost, and shortest lead time.  

Josh and Mark explore with Olivier the importance of the Toyota triangle in achieving TPS goals, especially longer-term goals, and examine the relationship of the triangle to the better known TPS “house” (the roof of three goals, supported by jidoka and just-in-time columns, etc.). The house embodies philosophical, technical, and managerial elements throughout, notes Olivier, but they are not specifically called out in the house. Human development, also not shown in the house, is at the center of the Toyota triangle. Olivier says human development is critical because despite advances in artificial intelligence, currently only people can solve complex problems, human problems. “TPS at the end of the day is trying to solve a human problem using people through the human creativity and the human intelligence.” 

Olivier also discusses the organizational problems he encounters with problem-solving. For example, he often sees people gravitating toward problems they know how to solve instead of solving the right problem. This occurs because it’s not always safe to solve the right problem and individuals don’t have the courage to take them on. “It’s very important for companies to realize that if they don’t provide an environment where it’s safe to solve problems, two things are going to happen: problems are not going to get solved, or if some problem gets solved it will be the wrong one... As management and leaders, you have to be able to encourage the people to solve difficult problems without fear of having negative consequences if they fail.”

Learn more about TPS and lean leadership at lean.org

A Personal Pursuit of Problem-Solving

Josh Howell and Mark Reich, LEI President and Chief Engineer Strategy, respectively, talk with Sal Sanchez, a Toyota veteran and TPS coach with LEI. Sal’s Toyota career began at New United Motor Manufacturing Inc. (NUMMI), the GM/Toyota joint venture and Toyota’s first automotive footprint in the United States, and continued with roles at Toyota North American headquarters and TSSC (Toyota Supplier Support Center, where he worked with Mark in the late-1990s) as well as Dana Corp. Across his career he’s learned from Toyota leaders and other notable lean mentors, including Gary Convis, which has, in turn, enabled him to help many organizations apply the Toyota Production System (TPS) and TPS fundamentals such as problem-solving and daily management. 

Sal describes his pursuit of all things problem-solving while rising up through Toyota, including his role as a team leader supporting others with problem-solving issues that surfaced throughout the day, especially when an andon cord was pulled and solutions needed to be developed and applied quickly. Sal counters some misconceptions regarding andon pulls, noting that it does not necessarily stop a line; it does, however, create urgency for team leaders to quickly assist and, in many instances, gives team members a brief window of opportunity to solve the problem on their own. Sal says the andon was frequently pulled where he worked, which was a good thing, and reminds Mark that most companies don’t focus on problems until they get big while at Toyota many little problems are being addressed “minute to minute and day to day so that they don’t become big problems.” 

While a team leader, Sal also sought to more deeply understand the problems team members were going through and learned this by doing the jobs they did and experiencing what they went through, earning respect of team members along the way. He carried that approach beyond Toyota and has supplemented it with additional ideas to engage and empower team members, including basic problem-solving skills for frontline associates and giving team members trend charts and templates to support their problem-solving. As Sal works today with companies trying to apply TPS, he continues to encourage a focus on culture and developing people and frontline leaders — “invest in your people.” 

Learn more about lean thinking and practice and lean.org.

Management System Surfaces Problems

Josh Howell, LEI President, talks about the relationship of problem-solving and daily management with Jill Miller, Manager for Global Learning and Development at MillerKnoll, a maker of office furniture, equipment, and home furnishings. Jill supports the development, use, and expansion of the MillerKnoll Performance System (MKPS), which she says is designed to meet customers’ needs by engaging and developing people to daily surface and solve problems. “At its heart, it’s really about building capability across the organization.”  

Josh and Jill describe their experiences with how an effective daily management system makes it easy and straightforward for organizations to know what problems they should be solving. “One of the most powerful things about MKPS is that it helps make problems visible every day, right where the work is happening,” says Jill. “So when people ask, ‘What problem do we need to solve?’ the system actually helps answer that by revealing the problems that might otherwise go unnoticed. I think at that point, the problems are plentiful. There’s no shortage of problems.” 

MKPS intentionally sets up both the system and culture to support daily problem-solving by: 

• Designing work to clearly show abnormalities and make them visible in real time,  
• Making it easy and safe for individuals to quickly highlight problems (people are not blamed or ignored),  
• Providing a prompt, supportive reaction to an associate’s call for help (an “andon call”), and 
• Ensuring the problems that are surfaced actually get solved; team leaders (called “facilitators” at MillerKnoll) are developed to be skilled in practical problem-solving, identifying root causes, and eliminating problems in ways that keep them from recurring.  

The two also discuss the development of ongoing MKPS expertise within MillerKnoll: building capability in a way that is standardized so that MKPS is effectively executed in a consistent manner. This involves a partnership between the MKPS leadership team, operations leaders, and the human resources group that supports operations for selecting individuals to train (“students”), creating alignment based on behaviors and characteristics, and reflecting on the learning process and its effectiveness. Jill says students have called the development program “life changing” — who they are as a person, how they think, how they see their roles, how they interact with people, and how they approach their careers within the company.