Christopher Reep | LEAN Culture Advisory

  2. Why "High Utilization" is an Operations Trap It Creates the Ultimate Waste: Overproduction Overproduction is the "mother of all wastes" because it breeds and hides every other operational failure. When you run machines just to keep utilization metrics high, you create excess inventory. The Cost: That inventory requires warehouse space, material handlers, forklifts, and tracking software. The Risk: It risks obsolescence, damage, and engineering change reworks. It Blinds You to Real Capacity When a plant is choked with Work-in-Progress (WIP) inventory caused by over-utilization, lead times skyrocket. Workers spend half their day moving parts out of the way just to find the parts they actually need. High utilization creates an illusion of a busy, high-capacity plant, when in reality, the plant is drowning in its own excess. It Destroys Flexibility and Responsiveness If a machine is booked $100\%$ of the time with long production runs to achieve "economies ...

  1. The Core Paradox: Local Efficiency vs. Global Flow Traditional operations focus on Local Efficiency —making sure every individual machine, department, or worker is running at maximum capacity ( $100\%$ utilization). Lean focuses on Global Flow —the speed at which a customer order transforms into cash. When you maximize local efficiency without regarding downstream demand, you create a system-wide traffic jam. If Station A keeps running at 100% capacity just to look efficient, it doesn't help the company sell more products. It simply burns cash on raw materials and creates material handling chaos. The throughput of the entire system is dictated solely by the bottleneck.

  Stop blaming the tools for a leadership defect. Whenever a Lean deployment craters or a Hoshin Kanri strategy stalls out, the corporate post-mortem always looks the same: "The X-Matrix was too complicated." "The frontline didn't buy in." "We chose the wrong tracking software." Let’s stop making excuses. The tools didn't fail. Management behavior did. For decades, executives have treated Lean like an administrative toolkit—a quick-fix Swiss Army knife for short-term cost-cutting, headcount reduction, and quarter-end window dressing. They demand standard work from the floor but refuse to practice Leader Standard Work themselves. They want operators to surface process variances transparently, but they respond with defensive, KPI-driven anger when a dashboard turns red. That isn't operational excellence. That is an expensive management performance. Lean and Hoshin Kanri are not a set of binders or a series of compliance checklists. They repres...

  Operational Architecture isn't just a set of tools—it’s an engine. From Root Cause Analysis to Hoshin Kanri Strategic Alignment, every loop must connect. When OODA feeds DMAIC, and PDCA drives Kaizen, your "True North" culture becomes unstoppable. Scale your execution. Lean into the framework. 🎯 #LeanCulture #HoshinKanri #SixSigma #OODALoop #OperationalExcellence

  10. Pursue Perfection (Daily Kaizen) Perfection is the "True North" that you never quite reach, but constantly approach. The Mechanics: Establish Daily Huddles (Tier 1 meetings) where the team reviews their metrics and identifies small improvements. The Deep Dive: This turns every employee into a scientist. By applying the PDCA cycle to even the smallest frustrations, you build an organization that is "Antifragile"—it gets better under stress.

  9. Management at the Gemba Leaders must transition from "Directors" to "Coaches." The Mechanics: Schedule regular Gemba Walks . Don't go with a checklist to find faults; go with an open mind to find "pain points." The Deep Dive: Use the Humble Inquiry method. Instead of telling a worker what to do, ask: "What is the standard?", "How is it performing today?", and "What is preventing you from hitting the goal?"

  8. Build Quality at the Source (Jidoka) In Lean, quality is not a department; it is a responsibility. The Mechanics: Use Poka-Yoke (error-proofing devices) like sensors or physical guides that make it impossible to assemble a part incorrectly. The Deep Dive: Implement the Andon system . If a defect is found, the operator pulls a cord to stop the line. The goal is to "Fix the process, not just the part."

  7. Implement a Pull System (Kanban) Pull ensures you only produce what the customer wants, when they want it. The Mechanics: Use Kanban cards or bins as visual signals. When a "Downstream" process consumes an item, the signal goes "Upstream" to authorize the production of a replacement. The Deep Dive: This eliminates the need for complex scheduling software and prevents "Mura" (Unevenness) by smoothing out the production volume.

 6. Create Continuous Flow Flow is the state where a product never stops moving. The Mechanics: Rearrange equipment into Work Cells (often U-shaped) to minimize walking distance and transportation. The Deep Dive: Focus on "One-Piece Flow." By processing one unit at a time, you catch defects immediately, whereas in "Batch" processing, you might produce 1,000 defects before realizing the machine is out of alignment.

5. Standardize the Work Standard Work is the foundation for the "Check" part of PDCA. Without it, every employee does the job differently, leading to unpredictable quality. The Mechanics: Use three elements: Takt Time (the pace of demand), Work Sequence, and Standard Inventory (WIP). The Deep Dive: Standards must be created by the people doing the work, not by engineers in an office. They are "living documents" meant to be challenged and improved. rt of PDCA. Without it, every employee does the job differently, leading to unpredictable quality. • The Mechanics: Use three elements: Takt Time (the pace of demand), Work Sequence, and Standard Inventory (WIP). • The Deep Dive: Standards must be created by the people doing the work, not by engineers in an office. They are "living documents" meant to be challenged and improved.

  4. Stability through 5S 5S is not about "cleaning up"; it is about visual control . A stable environment is a prerequisite for any improvement. The Mechanics: Sort (remove the junk), Set in Order (place for everything), Shine (inspect through cleaning), Standardize (rules for the first 3), and Sustain (self-discipline). The Deep Dive: The "Shine" step is actually a form of preventative maintenance. When an operator cleans a machine, they are looking for leaks, loose bolts, or cracks before they cause a breakdown.

  3. Map the Value Stream (Current State) You cannot fix what you cannot see. Value Stream Mapping (VSM) provides a bird's-eye view of both material and information flow. The Mechanics: Draw the flow from "Cradle to Grave." Include data like Cycle Time (C/T), Changeover Time (C/O), and Uptime. The Deep Dive: Focus heavily on the "information" arrows. Often, the bottleneck isn't the machine; it's the paperwork or the digital approval process sitting in someone's inbox.

  2. Define Value from the Customer’s Eyes Value is only what the customer is willing to pay for. Everything else is Muda (Waste). The Mechanics: Categorize every action into three buckets: Value-Added (VA), Non-Value-Added but Necessary (NVAN), and Non-Value-Added (NVA). The Deep Dive: Use the "Voice of the Customer" (VOC) to define specific metrics like lead time, quality ppm, and cost targets. If the process doesn't transform the fit, form, or function of the product, it’s a target for elimination.

  1. Identify the "True North" (Strategy Deployment) Lean is a journey, and you can't navigate without a compass. Hoshin Kanri is the method used to ensure that the "Vertical" (Executive) goals match the "Horizontal" (Frontline) capabilities. The Mechanics: Create an X-Matrix to link long-term breakthroughs to annual objectives and specific improvement projects. The Deep Dive: It’s about "Catchball"—the back-and-forth negotiation between levels of management to ensure goals are realistic and resourced.

  Cultural Sustenance: Keeping it Alive Daily Huddles These are the heartbeat of a Lean organization. They are short, focused, and held in front of visual boards. The Goal: Rapid alignment. Instead of long weekly meetings, daily huddles address "What did we do yesterday?", "What are we doing today?", and "What are our roadblocks?" Kaizen Mindset Kaizen means "change for the better." While big "Blitz" events are useful, the real power of Lean is the thousands of tiny improvements made by employees every day. The Goal: To make improvement part of the job, not something "extra" that happens once a quarter. Respect for People In Lean, respect means more than being "nice." It means not wasting people's time with bad processes and not "overburdening" ( Muri ) them with unrealistic expectations that lead to burnout. The Goal: Designing work that is sustainable, safe, and fulfilling, allowing people to use t...

  People & Problem Solving: The Human Element Psychological Safety Lean requires people to admit when things go wrong. If employees fear they will be punished for a mistake, they will hide waste. The Goal: Creating a culture where "no problem is a problem." When a defect occurs, the response from management should be, "Thank you for making that visible; how can the system be improved so this doesn't happen again?" Structured Problem Solving (PDCA) Without a structure like PDCA or A3 thinking, teams tend to jump to solutions before they understand the root cause. The Goal: To build "muscle memory" for scientific thinking. Plan (Observe and analyze), Do (Trial a countermeasure), Check (Verify results), Act (Standardize or pivot). Frontline Empowerment The person doing the work every day knows where the waste is better than any consultant. Empowerment in Lean isn't just "giving permission"; it’s providing the tools and time for wor...

Leadership & Strategy: Setting the Foundation Hoshin Kanri Alignment Traditional strategy often gets lost between the boardroom and the shop floor. Hoshin Kanri (Policy Deployment) uses a "catchball" process—a back-and-forth dialogue between levels of management—to ensure that high-level goals are translated into local, actionable projects. The Goal: When an operator is asked why they are doing a specific task, they should be able to trace it directly back to the company's "True North." Leader Standard Work (LSW) If the frontline has standard work, leadership must have it too. LSW is a documented set of daily, weekly, and monthly behaviors that move a manager from "firefighter" to "process auditor." The Goal: Ensuring that the Lean system is being followed and that the "Check" part of PDCA is actually happening. It shifts the focus from "Did we hit the numbers?" to "Did we follow the process that produces the nu...

  Cultural Sustenance: Keeping it Alive Daily Huddles These are the heartbeat of a Lean organization. They are short, focused, and held in front of visual boards. The Goal: Rapid alignment. Instead of long weekly meetings, daily huddles address "What did we do yesterday?", "What are we doing today?", and "What are our roadblocks?" Kaizen Mindset Kaizen means "change for the better." While big "Blitz" events are useful, the real power of Lean is the thousands of tiny improvements made by employees every day. The Goal: To make improvement part of the job, not something "extra" that happens once a quarter. Respect for People In Lean, respect means more than being "nice." It means not wasting people's time with bad processes and not "overburdening" ( Muri ) them with unrealistic expectations that lead to burnout. The Goal: Designing work that is sustainable, safe, and fulfilling, allowing people to use t...

  People & Problem Solving: The Human Element Psychological Safety Lean requires people to admit when things go wrong. If employees fear they will be punished for a mistake, they will hide waste. The Goal: Creating a culture where "no problem is a problem." When a defect occurs, the response from management should be, "Thank you for making that visible; how can the system be improved so this doesn't happen again?" Structured Problem Solving (PDCA) Without a structure like PDCA or A3 thinking, teams tend to jump to solutions before they understand the root cause. The Goal: To build "muscle memory" for scientific thinking. Plan (Observe and analyze), Do (Trial a countermeasure), Check (Verify results), Act (Standardize or pivot). Frontline Empowerment The person doing the work every day knows where the waste is better than any consultant. Empowerment in Lean isn't just "giving permission"; it’s providing the tools and time for wor...

  Leadership & Strategy: Setting the Foundation Hoshin Kanri Alignment Traditional strategy often gets lost between the boardroom and the shop floor. Hoshin Kanri (Policy Deployment) uses a "catchball" process—a back-and-forth dialogue between levels of management—to ensure that high-level goals are translated into local, actionable projects. The Goal: When an operator is asked why they are doing a specific task, they should be able to trace it directly back to the company's "True North." Leader Standard Work (LSW) If the frontline has standard work, leadership must have it too. LSW is a documented set of daily, weekly, and monthly behaviors that move a manager from "firefighter" to "process auditor." The Goal: Ensuring that the Lean system is being followed and that the "Check" part of PDCA is actually happening. It shifts the focus from "Did we hit the numbers?" to "Did we follow the process that produces the ...

​ 5. Seek Perfection (Kaizen) Lean is not a one-time event but a culture of continuous improvement. This requires a feedback loop where employees are empowered to suggest changes. • The PDCA Cycle: • Plan: Identify an opportunity and plan a change. • Do: Implement the change on a small scale. • Check: Analyze the results. • Act: If successful, implement it on a wider scale and standardize it.

  4. Establish Pull In a Lean system, nothing is produced until there is demand. This prevents overproduction—the most significant of the "Seven Wastes." Tool: Implement a Kanban system to signal when new work should begin based on actual consumption rather than forecasts.

  3. Create Flow After removing waste, ensure the remaining steps happen in a smooth, continuous sequence. Interruption-free flow reduces lead times and inventory costs. Technique: Use 5S (Sort, Set in order, Shine, Standardize, Sustain) to organize the physical or digital workspace for maximum efficiency.

  2. Map the Value Stream Once value is defined, map out every step in your current process. This visual representation helps identify where delays, bottlenecks, or redundant steps occur. Tool: Create a Value Stream Map (VSM) to distinguish between value-added and non-value-added activities.

​ 1. Define Value from the Customer Perspective The first step is identifying what the customer is actually willing to pay for. Anything that does not add direct value to the end product or service is considered "Muda" (waste). • Action: Conduct interviews or surveys to define the "Critical to Quality" (CTQ) requirements.