Lean Coffee Chat Summary: October 2025

The scent of coffee, or perhaps a celebratory German beer for our host facilitating from overseas, signaled the start of our monthly Lean Coffee. This gathering of continuous improvement professionals is less a formal meeting and more a collaborative workshop, dedicated to forging a living definition of “lean” from the diverse experiences of our community. This month, our conversation orbited around the critical theme of adaptability—how we must continually adjust our teaching methods, our strategic tools, and even our documentation to meet our audience and context exactly where they are.

The Craft of the Lean Teacher

Our first discussion dove into the craft of becoming a better lean teacher. The resounding consensus was that credibility flows not from theoretical knowledge, but from constant, tangible practice. One perspective cautioned against “academic lean,” arguing that true teaching means explaining concepts in practical, digestible, and relatable ways.

The conversation quickly pivoted to the how of teaching:

• The Mindset Shift: A great teacher doesn’t just give answers, but asks provocative questions, famously summarized as, “Do you ask questions or do you give answers?”.
• Know Your Audience: Effectiveness is rooted in the ability to understand different learning styles and personality types , and tailoring the teaching method (e.g., live events vs. self-paced online materials) to the audience’s needs.
• Show, Don’t Tell: Teachers should prioritize concrete examples over abstract concepts, and be able to identify and leverage past, unnamed improvements that were “lean” without being called “lean”.
• Embrace Failure: This self-improvement requires receiving constant feedback from participants (“add, change, delete”) to ensure the facilitation techniques are responsive. This dedication to listening and adapting even extends to dramatic failures—one participant shared an example of a training game that failed spectacularly but resulted in a “more meaningful discussion” simply by asking the audience what they had learned.

Strategy Deployment: When OKRs Meet Lean

This thread of adaptation carried us into a nuanced debate on strategy deployment: Do Objectives and Key Results (OKRs) work within a Lean Management System?. For many in our community, lean transformation is a clear architecture: Strategy identifies Value Streams, which define Kaizen Events. The question is whether OKRs—a system popularized by Google —uphold this architecture.

A powerful insight was that OKRs can be extremely useful, but only if they are designed to support and be incorporated into an actual strategy, rather than being treated as a separate, individualistic HR tool. The primary challenge, many noted, lies in the “vertical cascade”: defining measurable Key Results that an individual contributor at the lowest level has control over, without them becoming “loosey goosey”.

This is where the systems must connect. One surprising example revealed success in a state government which practices a full Lean Management System (with daily management, tiered metrics, and huddles) and adopted OKRs as a minimum strategic baseline for less-mature agencies. This proved they are not mutually exclusive; the key takeaway is that OKRs and the more traditional Hoshin Kanri can actually “meld together really nicely” if the deployment is designed top-down.

Process Documentation: The RACI-Swim Lane Hybrid

The final topic brought us to the architecture of process documentation itself: the swim lane RACI hybrid model. RACI (Responsible, Accountable, Consulted, Informed) is typically a project management tool for non-repeatable tasks, while a swim lane map is for repeatable process flow.

The discussion immediately focused on the tension: combining them risks creating a visual “absolute mess,” yet there is immense value in clarifying the choreography of “who’s doing what and when”. The practical solution, shared by one professional, suggests the two tools are best used in sequence: first, use a RACI matrix to clarify ownership and accountability for parts of a system, and then translate that clarity into a visual workflow that resembles a swim lane structure. The RACI acts as the essential pre-work to ensure the visual process map is accurate and effective.

Defining Lean: The Continuous Act of Contextual Adaptation

Each of this month’s discussions—from teaching methods to strategy deployment and process mapping—underscores the same truth: Lean is not a rigid doctrine, but a flexible philosophy.

To build a better lean teacher, you must adapt to the student’s needs. To create effective strategy, you must adapt your tools (OKRs, Hoshin) to the organization’s culture and management system. And to map a process, you must adapt your documentation (RACI/Swim Lane) to clarify the workflow’s purpose. Our collective knowledge base defines lean as the continuous act of contextual adaptation, where the goal is always clarity, credibility, and connection to the people doing the work.