Why They Fail ... and the Simple Key to Success!

Why Shiny Enterprise Tech Kills Continuous Improvement A twenty-seven step process does not improve when you automate it. It simply runs the same waste faster, and now that waste is locked into code. However, leaders keep reaching for enterprise platforms and AI before fixing the workflow underneath. Consequently, they automate broken processes and call it transformation. In this episode of the Why They Fail Podcast, Kevin Clay sits down with John Q. Todd, Senior Business Consultant and Product Researcher at Total Resource Management. Together, they explore why 96% of continuous improvement initiatives collapse within eighteen months, and why buying technology first accelerates that failure. WHY LEADERS RUSH TO AUTOMATE BROKEN PROCESSES Leaders often treat enterprise platforms like an easy button. When a team faces a messy twenty-seven step workflow, management tries to automate it rather than do the harder work of simplifying it. Therefore, the software gets customized around an inefficient operation, and that inefficiency becomes permanent. Furthermore, this fails on the floor as well as on paper. Complex systems generate constant automated notifications. As a result, technicians stop reading them, which is alarm fatigue in plain terms. Eventually, people build rogue Excel sheets and offline databases just to finish their shift. THE HIERARCHY THAT STOPS YOU AUTOMATING BROKEN PROCESSES To avoid that trap, John lays out a disciplined order of operations. First, simplify the existing workflow. In his experience, the overwhelming majority of process problems disappear by stripping out wasted steps rather than reprogramming anything. Second, innovate. Re-engineer the layout and remove the wait time sitting between functional departments. Finally, once the workflow is lean and predictable, consider automation. In other words, software should support a clean process rather than rescue a broken one. CASCADING KPIS DOWN TO THE SHOP FLOOR Sustainable control also needs frontline visibility. When metrics stay locked in executive dashboards, floor technicians cannot see how their work connects to business performance. Consequently, they have no reason to care about the number. However, when targets cascade down to the cell and machine level, that changes. Technicians gain real ownership of process health. Moreover, real-time data lets teams spot variation as it happens, address root causes objectively, and protect the return on the project. When you refuse to automate broken processes prematurely, the solution actually lasts. KEY TAKEAWAYS Above all, these lessons separate a digital transformation that sticks from one that quietly becomes shelfware. First, automating a messy twenty-seven step process accelerates waste and creates system-wide failure. Second, successful projects scope tightly and focus on the critical twenty percent of issues. Third, f... Chapters (00:00:00) - Introduction and Guest Background(00:02:16) - John's Career Journey(00:03:27) - Why Leadership Commitment Breaks Down(00:04:25) - The Power of Scope and Focus(00:06:16) - Agile Approaches to Process Improvement(00:07:29) - Automating Messy Processes Before Fixing Them(00:11:40) - The Simplify, Innovate, Automate Hierarchy(00:13:11) - Alarm Fatigue and Workarounds(00:14:37) - Getting Frontline Buy-In on New Systems(00:17:07) - Understanding KPIs at the Floor Level(00:19:51) - Root Cause Analysis and Facilitation(00:22:31) - Control Phase: Sustaining Improvements(00:24:57) - The What and Why Tool(00:25:45) - Prioritizing Projects by Real KPI Impact(00:29:50) - Closing Thoughts and Show Wrap-Up

Pencil Whipping Maintenance: The Lie Killing Plants Your CMMS says 100% compliance. Zero overdue checks. Every dashboard green. However, the bearings are singing and nobody has opened that panel in months. That gap has a name. Pencil whipping maintenance is a quiet epidemic in modern plants, and it destroys facilities that look perfectly healthy on paper. In this episode of the Why They Fail Podcast, Kevin Clay sits down with maintenance leader John Echols. Together, they unpack why technicians close work orders they never actually performed, and what it takes to stop it. WHY FACILITIES RESORT TO PENCIL WHIPPING MAINTENANCE Most plants do not start out dishonest. However, when schedules are rigid, stopping a line for a twenty-minute inspection looks like lost revenue. Therefore, operations begins treating maintenance as an obstacle rather than a partner. Meanwhile, technicians still have compliance numbers to hit. So they click through the checklist in seconds. As a result, the CMMS shows a perfect score while the equipment quietly degrades underneath. Furthermore, the damage compounds. A vibrating bearing, a hot drive motor, a misaligned conveyor. Each one is a fifteen-minute fix early on. Later, the same issue becomes days of unplanned downtime and thousands in lost throughput. SHINY TECH CANNOT FIX BROKEN DISCIPLINE Many organizations respond to breakdowns by buying predictive sensors and new CMMS platforms. Nevertheless, technology cannot compensate for a culture that ignores it. If nobody has time to act on an alert, the alert is worthless. In contrast, older plants running legacy equipment often post better uptime. The reason is simple. They do basic preventive work consistently instead of chasing digital solutions. Consequently, their machines last longer than the ones surrounded by sensors. ELIMINATING PENCIL WHIPPING MAINTENANCE WITH ROOT CAUSE CI Ending pencil whipping maintenance means tying continuous improvement to the KPIs the business actually cares about. Instead of running operations and maintenance as separate silos, strong plants deploy autonomous maintenance so operators own routine upkeep themselves. Additionally, leaders have to make honesty safe. If a technician admits a check was skipped and gets punished for it, the next skipped check simply gets hidden better. Therefore, the fix is cultural before it is technical. Shift the plant from reactive firefighting to disciplined fire prevention, and the pressure to fake the data disappears on its own. KEY TAKEAWAYS Above all, these lessons separate a plant that runs on real data from one running on a comfortable fiction. First, chasing short-term output while skipping planned maintenance guarantees catastrophic downtime later. Second, high-pressure KPIs push technicians to pencil whip checklists just to keep dashboards green. Third, predictive sensors and expensive CMMS tools fail when teams lack the time or culture... Chapters (00:00:00) - Introduction and Guest Background(00:02:08) - Maintenance vs Production: Natural Tensions(00:04:32) - Short-Term Thinking and Downtime Consequences(00:07:34) - Pencil Whipping and the Collapse of CI Programs(00:12:31) - Autonomous Maintenance and Department Silos(00:13:11) - Shiny New Tech vs Basic Equipment Maintenance(00:16:03) - When Alerts Go Unanswered: Neutering Predictive Systems(00:17:15) - Boards Without Buy-In: Lean Theater(00:19:33) - Old Machines, Good Maintenance vs New Tech Failures(00:21:50) - Understanding the Why Before Implementing Change(00:23:52) - Building KPI Infrastructure for Real Improvement(00:27:45) - From Firefighting to Coaching: Building Trust(00:31:09) - Closing Thoughts and Call to Action

The Fix Worked, Culture Didn't: A VA Door to Doc Story Five minutes for one doctor. Over 400 minutes for another. Same emergency room, same shifts. That is the scale of door to doc variation one Lean Six Sigma team found inside a Veterans Affairs hospital. However, the real story is what happened next. They fixed it, and then the fix died the moment the team walked away. In this episode of the Why They Fail Podcast, Kevin Clay sits down with Lacee Koerner (MSN, RN, CEN), an emergency room and quality nurse. Together, they walk through an honest account of a project that worked on paper but failed in practice. TACKLING DOOR TO DOC VARIATION IN THE EMERGENCY ROOM At first, Lacee and her team set out to reduce Left Without Being Seen rates. However, during their early Gemba walks, they found something uncomfortable. The numbers leadership trusted were easy to bend through simple workarounds. Therefore, the team changed direction. Instead of chasing a metric staff could shape, they moved to door to doc variation. As a result, they captured what was really happening rather than what the reports claimed. Next, they ran a careful Measurement System Analysis and applied statistical process control. Consequently, the swings became visible. One doctor answered in five minutes. Another took more than 400. Once they found those outliers and set up controls, response times dropped in a way the data could prove. WHY GREAT PROCESS FIXES GO DEAD ON ARRIVAL So the fix worked. Nevertheless, it did not last. In this candid talk, Lacee explains why the project went dead on arrival once her team stepped back. Because there was no supervisor buy-in, no steady backing from leaders, and no daily support system, the gains faded fast. Within weeks, the department drifted back to old habits. In other words, nothing held the change in place. Furthermore, the staff were hearing two messages at once. On one hand, leaders asked for strict compliance. On the other hand, they asked nurses to speak up and own the work. Therefore, this episode lands on a hard truth. Data and tools can solve the technical problem. Only leaders and culture can keep it solved. KEY TAKEAWAYS Above all, these lessons separate a fix that holds from one that quietly slips away. First, uncontrolled door to doc variation hurts patient flow and care quality. Second, a careful measurement system analysis stops teams from trusting numbers that have been shaped. Third, top-down orders without supervisor buy-in create pushback, and eventually the project falls apart. Fourth, even a proven win will go dead on arrival unless something is built to hold it. Finally, lasting improvement happens when leaders match what they ask for with how they actually behave. FREE BOOK Over 90% of continuous improvement programs fail within eighteen months. In his book, Kevin explains exactly why, and what to do instead. Therefore, if your last project slipped back, this is a good place to start. Get a free copy of "Why They Fail and the Simple Key to Success" here: Chapters (00:00:00) - Intro and Framing the Contradiction(00:01:15) - Meet Lacey Kerner and Her CI Journey(00:04:03) - Does VA Culture Embrace Data?(00:05:36) - Bureaucracy and Data Access Struggles(00:07:22) - Frontline Nurses' Resistance to the Project(00:09:31) - Lack of Infrastructure and Sustainment Challenges(00:11:43) - Cutting Through Red Tape for Data(00:13:57) - Executive Sponsorship and Leadership Buy-in(00:16:07) - Top-Down vs Frontline Empowerment Paradox(00:18:47) - Did the Improvements Stick?(00:19:34) - Defining the Door-to-Doc Project(00:22:58) - Data Analysis Errors and Discovering Variability(00:25:13) - Wild West Variation and Finding Focus(00:26:37) - Closing Thoughts and Show Wrap-up

Stop Blaming Workers: Fix Broken Systems and Bad Metrics Fire the employee who made the mistake and the next person in that seat will make the exact same mistake. That is the uncomfortable truth behind most operational failures. Leaders who want real improvement must stop blaming workers for mistakes and start diagnosing the systems that produce them. In this episode of the Why They Fail Podcast, Kevin Clay sits down with continuous improvement expert and author Mark Graban. Together, they explore Dr. W. Edwards Deming's management philosophy, the stark contrast between command-and-control leadership and the Toyota Production System, and why treating Lean as a cost-cutting gimmick always fails. WHY LEADERS MUST STOP BLAMING WORKERS FOR MISTAKES When organizations operate under a culture of fear, employees learn one lesson quickly. Transparency leads to punishment. Consequently, workers begin hiding defects, delaying communication, and smoothing over metric variation just to protect themselves. Dr. Deming demonstrated that roughly 94% of all workplace problems are built directly into the system. High-level decisions about suppliers, equipment maintenance, staffing levels, and management expectations dictate performance far more than individual effort ever could. Therefore, firing an employee without fixing the broken workflow accomplishes nothing. The role stays the same. The process stays the same. The failure repeats. Moving forward requires leaders to stop blaming workers for mistakes and build genuine psychological safety at every level of the organization. LESSONS FROM GM, NUMMI, AND THE RED BEAD GAME Mark Graban reflects on his early career at General Motors, where toxic management practices produced catastrophic quality issues and dismal morale. However, GM's joint venture with Toyota at the NUMMI plant told a completely different story. The same workforce, under a collaborative management system, achieved world-class results. The famous Deming Red Bead Game illustrates this vividly. When the system itself forces defects, no amount of slogans, targets, or yelling will change the outcome. Instead of reacting emotionally to daily metric fluctuations, effective leaders use process behavior charts. As a result, they can distinguish normal system noise from genuine statistical signals worth acting on. BUILDING A TRUE LEAN MANAGEMENT CULTURE Lean is not a toolbox for short-term headcount reduction. When executives reduce it to cost-cutting, they sacrifice employee engagement, product quality, and workplace safety in the process. True operational excellence pairs Lean problem-solving with data-driven Six Sigma analytics. Together, they eliminate unnecessary complexity and remove waste at the root. Furthermore, when leaders listen to the process instead of blaming people, they unlock sustainable capacity, higher quality, and lasting organizational success. ABOUT THE GUEST: MARK GRABAN Mark Graban is an internationally recognized author, speaker, consultant, and entrepreneur who works with leaders to improve qual... Chapters (00:00:00) - Why They Fail(00:00:53) - Why They Fail: The Lean Startup(00:09:38) - The Toyota Way: A Culture of Excellence(00:13:20) - GM's 'command and control' culture(00:19:03) - GM's 'Lean' Program(00:23:59) - Does Lean Matter?(00:31:10) - How to Prevent and Learn From Mistakes?(00:36:38) - Control Charts for Process Behavior Charts(00:43:10) - Why They Fail

Surgical Pressure Cooker: Stop Wasting Capacity in ASCs Fifteen minutes between cases does not sound like much. However, across a standard daily schedule it compounds into 150 minutes of lost room capacity. That translates to an annual revenue bleed between $1.3 million and $2.2 million. Eliminating operational friction in surgery centers is one of the fastest margin recoveries available to any ASC leadership team. In this episode of the Why They Fail Podcast, Kevin Clay sits down with Sylvie Fortier, an operations leader whose career began during the foundational rollout of Six Sigma across Motorola's global enterprise. Together, they examine how hidden delays between cases quietly drain both revenue and organizational culture. UNDERSTANDING OPERATIONAL FRICTION IN SURGERY CENTERS Ambulatory surgery centers function like high-stakes pressure cookers. Top surgeons operate with extreme clinical precision every single day. However, the true bottleneck is rarely the surgical procedure itself. Instead, uncoordinated turnover minutes cost facilities thousands of dollars daily. The gap sits between patient discharge, terminal cleaning, and sterile pack setup. Consequently, a delay of just 15 minutes per case costs a typical facility between $5,500 and $9,000 every day. Furthermore, the root cause is usually information asymmetry rather than individual performance. Scheduling, anesthesia, and materials management often operate with different information at different times. Therefore, the friction is architectural, not personal. WHY MORE DATA IS NOT THE SOLUTION When surgical turnarounds lag, leadership often responds by tracking more variables. They purchase new dashboard software and add more metrics to the reporting stack. However, adding data to an already overwhelmed environment creates decision paralysis rather than operational control. Execution rarely stalls because of missing data or missing standard operating procedures. Instead, processes break down because leadership lacks the filters needed to separate actionable signals from background noise. As a result, teams see everything and act on nothing. ALIGNING LEADERSHIP WITH HOSHIN KANRI Most operational breakdowns stem from human and strategic misalignment rather than simple process errors. In healthcare specifically, clinical founders focus on case complexity and patient outcomes. Meanwhile, financial partners prioritize fiscal margins and throughput. Therefore, bridging that gap requires a visual strategy tool. Hoshin Kanri and the single-page X Matrix map strategic goals, tactical projects, and resource ownership onto one agreed document. When leadership can see all three on a single page, cross-departmental friction drops sharply. Consequently, teams establish genuine operational sovereignty over their own outcomes. ABOUT THE GUEST: SYLVIE FORTIER Sylvie Fortier is the founder of Phoenix Praxis, where her work centers on a single idea: making the invisible visible. She helps ambulatory surgery centers and complex organizations surface the operational friction that neve... Chapters (00:00:00) - Why They Fail(00:01:14) - Why They Fail: Six Sigma and Continuous Improvement(00:06:01) - How to Build a Continuous Improvement Culture(00:07:10) - Operational Friction Points in Ambulatory Surgery Centers(00:12:27) - How to Get the Leadership Group On the Same Page(00:18:30) - Healthcare Operational Data Overwhelm(00:21:44) - The Importance of Outside Perspectives(00:22:51) - Choosing a food with a clean label(00:26:47) - How to Eliminate Operational Friction in Surgery Centers