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.

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.

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.

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.

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...

• (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

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.

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.

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.

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.

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:

• (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

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.

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.

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.

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.

Mark Graban is an internationally recognized author, speaker, consultant, and entrepreneur who works with leaders to improve qual...

• (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