
Why Shiny Enterprise Tech Kills Continuous Improvement
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
More episodes from "Why They Fail ... and the Simple Key to Success!"



Don't miss an episode of “Why They Fail ... and the Simple Key to Success!” and subscribe to it in the GetPodcast app.








