My guest for Episode #530 of the Lean Blog Interviews Podcast is Ken Segel, Co-Founder and Chief Relationship Officer at Value Capture.

Episode page with video and more

With over two decades of experience in healthcare improvement, Ken has been instrumental in guiding Value Capture's mission: helping healthcare organizations pursue habitual excellence by applying principles of safety, transparency, and systems thinking. In this episode, Ken shares lessons drawn from his unique and non-traditional journey--from public policy work in Washington, D.C. to transformative partnerships with industry icon Paul O'Neill and the Pittsburgh Regional Health Initiative.

Ken and I explore why world-class safety, quality, and financial performance can and must co-exist, and how starting with safety unlocks powerful learning across any organization. He reflects on how Paul O'Neill inspired leaders to set seemingly audacious goals like "zero harm"--not to punish failure, but to align people around shared purpose and continuous improvement. We also discuss the importance of creating a comprehensive operating system, one that fully integrates work systems, management systems, and improvement systems--not just Lean tools or events in isolation.

Listeners will learn why Ken believes deeply in the Shingo Principles, and why Value Capture remains the only Shingo Affiliate firm dedicated exclusively to healthcare. He also talks about the recent leadership transition at Value Capture, passing the CEO baton to longtime colleague Shanna Padgett. Whether you're a Lean healthcare leader or someone passionate about values-based leadership, this conversation offers rich insights into guiding with purpose, learning from failure, and building systems that support excellence for all.

Ken previously appeared on My Favorite Mistake (Episode 147), where he shared a powerful story about early-career lessons in leadership and systems thinking that helped shape his path into healthcare improvement.

• Can you share your Lean origin story?
• (How did your unconventional path lead you into this work?)
• What was it like working with Paul O'Neill, and how did he influence your thinking?
• What was the vision and impact of the Pittsburgh Regional Health Initiative?
• Why was setting a goal of zero harm so controversial--and so powerful?
• How did leaders like Dr. Richard Shannon apply these principles to dramatically improve patient safety?
• Where do you see progress--and continued challenges--around transparency and safety sharing in healthcare?
• Why is safety such an effective entry point for broader transformation?
• How do you define a "comprehensive operating system" in a healthcare context?
• What's the difference between a management system and a full operating system?
• How can the Shingo principles support healthcare organizations on their improvement journey?
• What does it mean for Value Capture to be a Shingo Affiliate focused solely on healthcare?
• What advice would you give to a health system leader who thinks they already have a Lean system in place?
• Can you share the recent leadership transition news at Value Capture?

This podcast is part of the #LeanCommunicators network.

My guest for Episode #529 of the Lean Blog Interviews Podcast is Scott Gauvin, CEO of Macresco and co-creator of the Respect for People Roadmap.

Episode page with video, transcript, and more

With 30 years of experience leading operational transformations across sectors including biotech, pharma, agriculture, and manufacturing, Scott brings both a systems mindset and a people-first philosophy to his work. His journey into Lean began with frustration over leadership that blamed people rather than fixing systems—sparking a personal quest to better integrate continuous improvement with what he calls the “practice” of respect for people.

In this episode, Scott shares the evolution of his thinking and how it culminated in the Respect for People Roadmap, a structured learning experience designed to operationalize cultural change through nine actionable behaviors. We explore the difference between “respecting people” as an individual action and “respect for people” as a system-level design principle. Scott also challenges the common notion that respect must be earned, arguing instead that every human being is inherently worthy of it—an idea rooted in his research on Confucian influences within Toyota’s founding culture.

This conversation is a must-listen for anyone struggling to move beyond Lean tools and truly build a culture of continuous improvement grounded in human dignity. We also touch on how these ideas align with the Shingo Model, why so many transformations fail to stick, and how organizations can design systems that scale respect—without waiting for permission from the top. Check the links below to learn more and access Scott’s free “test drive” version of the Roadmap.

• What’s your origin story with Lean and operational excellence?
• What drew you to explore the “respect for people” pillar more deeply?
• How do you distinguish between “respect for people” and “respecting people”?
• Why do so many interpretations of “respect” default to hierarchy or politeness?
• How should leaders approach differences in how individuals define respect?
• Is it a mistake to assume respect must be earned rather than given?
• What are your thoughts on the phrase “better to be respected than liked”?
• How do challenge, kaizen, and respect interrelate in Toyota thinking?
• What did your research uncover about Confucianism’s influence on Lean?
• How does the concept of “respect for people” show up in system design?
• What inspired the creation of the Respect for People Roadmap?
• What are the three key behavioral principles embedded in the Roadmap?
• What makes this program scalable and sustainable across organizations?
• Why was it important that the nine behaviors require no leader permission?
• How do you respond to the idea that “respect for people” should be translated as “respect for humanity”?
• Are you looking to pilot the Roadmap in healthcare settings?
• What would transformation look like if it were truly resilient—not dependent on a single leader

This podcast is part of the #LeanCommunicators network.

My guest for Episode #528 of the Lean Blog Interviews Podcast is Mark Reich, a Senior Lean Coach with the Lean Enterprise Institute and former Toyota leader with over two decades of experience.

Episode page with video, transcript, and more

Mark spent six years working in Japan, including helping launch the Lexus brand and later leading Hoshin Kanri strategy processes during Toyota's rapid growth in North America. He also played a pivotal role at the Toyota Supplier Support Center (TSSC), helping bring the Toyota Production System to manufacturing, healthcare, and nonprofit organizations. In our conversation, we dive into his career journey, his approach to Lean leadership, and the practical lessons behind his new book, Managing on Purpose: Using Hoshin Kanri to Develop Strategy, Align Teams, Grow Leaders, and Innovate Your Enterprise.

You can get a 25% discount on the book via LEI using the code LBIPODCAST25.

Mark shares compelling stories from his early days at Toyota, including working on the front lines of assembly, learning by doing, and his first experience pulling the andon cord. These moments shaped his appreciation for Toyota's deep respect for frontline work and its commitment to developing people. He reflects on how Toyota embeds learning and support into problem solving, where pulling the cord is seen as a learning opportunity, not a failure. That mindset became foundational for his later work, especially when managing enterprise-wide strategy through Hoshin Kanri.

We also explore what Hoshin Kanri really is--and what it isn't. Mark challenges the overemphasis on tools like the X-matrix and instead advocates for focusing on purpose, alignment, and leadership behavior. He explains how strategy deployment at Toyota was never a one-way cascade, but a dialogue grounded in humility, curiosity, and shared responsibility. Whether you're new to Hoshin or struggling to sustain it, Mark offers insights that can help any leader make strategy a living, breathing part of organizational culture.

• How did you end up working for Toyota, and what led you to Japan?
• What was your educational background, and did you already speak Japanese before moving there?
• What was your initial role at Toyota, and how did it relate to their global expansion?
• Did you meet or work with John Shook during your time in Japan?
• How did Toyota develop you into an industrial engineer despite your background in English writing?
• What was it like working in a Toyota plant, and what did you learn from that experience?
• Did you experience any early mistakes or learning moments while working the line?
• How did your role evolve after leaving Japan, and how did you get involved with Hoshin Kanri in North America?
• What challenges was Toyota North America facing that made Hoshin Kanri so essential?
• How did you facilitate alignment and catchball between Toyota's plants and leadership teams?
• How do you define Hoshin, strategy, and Hoshin Kanri?
• Why do you prefer not to use the term "strategy deployment," and what's the issue with top-down-only thinking?
• How do you coach executives to embrace catchball and bottom-up engagement?
• How do you balance executive direction with frontline input in strategy development?
• What role does psychological safety play in making Hoshin Kanri work?
• How does A3 problem solving fit into the Hoshin process, and how does it help build capability?
• Why is it important for executives to practice PDCA and engage in direct problem solving?
• What's the difference between long-cycle and short-cycle PDCA, and how should leaders manage both?
• Why does it take most organizations a couple of years to fully embed Hoshin Kanri?
• What lessons do companies learn when they start with too many strategic initiatives?
• Why did you choose not to include the X-matrix in your book, and what are your thoughts on its use?
• What business problems does Hoshin Kanri best help organizations solve?
• How can Hoshin Kanri help clarify the distinction between daily management and long-term strategic work

This podcast is part of the #LeanCommunicators network.