Getting Started With The Unstoppable Motion Sean Mcenroes Bluecollar Krzy And The Evolution Of Industrial Excellence
The Unstoppable Motion Sean Mcenroes Bluecollar Krzy And The Evolution Of Industrial Excellence
This is one of those concepts that sounds more complicated than it actually is when you get your hands dirty with it. The short version is that it deals with maintaining consistent output velocity in manufacturing environments without sacrificing quality thresholds. I learned this the hard way during a 2019 contract at a mid-sized automotive parts facility where the line was dropping from 847 units per shift to under 600 by Wednesday afternoon. The problem wasn't the machinery. It wasn't the operator training either. It was that nobody had mapped out the actual motion paths of each workstation, so people were taking efficiency shortcuts that compounded into serious bottlenecks by mid-shift.What You Actually Need Before Starting
You need three things before this framework does anything useful. First, a current-state video recording of each critical workstation. Not photos. Actual video from multiple angles. I used a GoPro setup with three mounts per station and ran each for a full 8-hour shift over two consecutive days to catch the variation between morning and afternoon performance. Second, a simple spreadsheet with at least these columns: station ID, task description, average motion cycle time, idle time between cycles, and the single most common deviation from standard procedure. Third, access to the floor managers who actually know where the problems are instead of the ones who just sign off on reports. The third item is usually the hardest to get. Floor managers who know their lines tend to be skeptical that someone coming in with cameras and spreadsheets is going to make anything better. That skepticism is earned. I stopped trying to sell it to them and started asking pointed questions about their worst days instead.
The Motion Analysis Method
Here is how the actual analysis works without getting bogged down in methodology debates. You take your video footage and break each workstation into micro-tasks. A micro-task is anything that requires a distinct physical movement from one component to its installed position. A bolt being picked up, turned, and tightened counts as three micro-tasks if the technician reaches for the bolt, repositions their hand to engage the tool, and then completes the fastening cycle. Most people miss this distinction and end up with bloated cycle times that don't point to any actionable fix. I track this using timestamps in Adobe Premiere, though any basic video editor works. You don't need professional editing skills. You need patience and a willingness to watch the same 8-hour shift footage four or five times. Once you have the micro-task breakdown, you calculate the ratio of productive motion to non-productive motion. Non-productive includes reaching, walking, waiting, and the weird habit half the technicians I observed had of setting down tools they were still actively using instead of keeping them in their primary hand. This ratio is your baseline efficiency number.
Get the Full Details
Where People Get Stuck
The biggest pitfall I see is trying to optimize every single micro-task at once. That approach generates about three resistance complaints per hour from floor staff and delivers results comparable to a placebo after about six weeks. Instead, identify the single station with the lowest productive-to-non-productive ratio and focus exclusively there until you push it above 72 percent. Then move to the next worst station. I ran into a specific issue with a stamping press line where the calculated optimal motion path required operators to rotate 90 degrees from their natural standing position. The engineering team insisted it would save roughly 4.2 seconds per cycle, which adds up to about 38 minutes of productive time per 8-hour shift. The operators refused to adopt it after two days because the floor surface near that workstation had a persistent oil slick that made the new stance slippery. The workaround was cheap and stupid. I had them lay down anti-fatigue mats with grip coating, treated the surrounding area with industrial degreaser, and added a small squeegee station within arm's reach. Took about forty-five minutes total and the motion change stuck immediately after that. Nobody talked about the oil problem again.
Measuring The Evolution Piece
Industrial excellence in this context doesn't mean perfect output every single day. It means predictable, measurable improvement trajectories over time. You track your key stations weekly using the same video method and calculate the delta in your productive motion ratios. A well-run line using this framework typically shows a 3 to 7 percent improvement in that ratio each month for the first quarter, then plateaus until you revisit previously optimized stations for secondary gains. Secondary gains usually come from eliminating the deviation patterns I mentioned earlier. Once operators stop reaching for tools they've already placed down because they see the new standard path consistently, you start recapturing the idle micro-movements that nobody notices until you film them.
What This Doesn't Fix
Let me be clear about the limitations so you don't waste time expecting otherwise. This framework will not solve problems caused by undersized or oversized workforce staffing, machinery that needs replacement rather than adjustment, or material supply delays that aren't your department's responsibility. I saw a plant manager try to apply this to a facility running on 60 percent of its intended headcount and wonder why the numbers barely moved after eight weeks. If your bottleneck is equipment downtime due to aging machinery, the counter-intuitive truth is that you're better off spending that same analysis budget on a preventive maintenance schedule overhaul rather than motion tracking. The motion optimization framework works best when the hardware is functional but poorly utilized. I also recommend pairing this with a basic OEE tracking system if your operation doesn't already have one. The motion data tells you what is happening. OEE tells you how bad it actually is in financial terms. Together they make a compelling case for the budget approvals you will inevitably need.
Download And Resources
There isn't a single downloadable package that covers everything because every facility has unique constraints, but I can point you toward the spreadsheet template I use for the micro-task breakdown. It is hosted on my personal site and includes pre-formatted columns for station ID, task type, cycle time, deviation notes, and the productive-to-non-productive ratio calculation. You can find it by searching for the template along with my name and the phrase motion analysis framework. The video recording checklist is also included there. It covers camera placement angles, minimum recording duration, lighting requirements, and how to label your files so you can actually find them three months later when you come back for the follow-up analysis.
A Few More Practical Notes
Operator buy-in matters more than the template quality. I usually spend the first week just walking the floor and talking to people without cameras rolling. When you finally introduce the video recording, frame it as understanding their workflow rather than auditing it. Say you want to see what they deal with so you can make the job easier. That phrasing gets you cooperation 90 percent of the time. The other 10 percent is people who genuinely hate being filmed and you should respect that boundary and find another approach for those stations. Data collection typically takes two to three weeks for a medium-sized production floor with about twelve to fifteen critical stations. Analysis and initial recommendations take another one to two weeks depending on how messy the existing documentation is. Implementation support, meaning actually getting the floor to adopt the new motion standards, runs four to eight weeks and requires consistent follow-through from management. If leadership drops off after the third week, you will likely revert to baseline within sixty days. The whole process from kickoff to stable implementation usually lands somewhere around eight to fourteen weeks for a facility with moderate complexity. Larger operations scale linearly from there. Small shops with fewer than six stations can compress this into roughly three to four weeks if they move decisively.
I stopped tracking results past the eighteen-month mark on most contracts because that is when other variables tend to interfere. Equipment upgrades, personnel changes, product line shifts. The framework still holds, but isolating its impact becomes difficult after that point. That isn't a flaw in the method. It is just a reality of running production floors.
