Jerry Dolinsky is the CEO of Dozuki, a leading connected worker solution for enterprise-level manufacturing companies.
I was standing on a remote, muddy drilling rig along the Gulf Coast when I saw a young field technician do something that completely changed how I think about operations.
He was servicing a massive, high-pressure manifold. Right before tightening a critical connection, he made a clever, rapid adjustment with a custom-rigged spacer. It took him about twenty seconds, bypassed a known machinery pinch-point hazard and easily saved twenty minutes of frustrating struggle.
I asked him if that trick was in the official service manual.
He laughed. “Of course not,” he said. “If we followed the corporate manual word for word, we’d be three days behind schedule and I’d probably have lost a finger by now!”
That interaction highlighted a painful reality that many industrial executives choose to ignore: There is a massive, dangerous gulf between “work-as-imagined” by corporate engineers sitting in comfortable offices and “work-as-done” by the people sweating in the dirt.
The Cost Of Silent Frontlines
Manufacturing executives often assume that when field procedures weren’t followed, it was a discipline or training problem. The solution was to push for more oversight, stricter audits and heavier policing.
The turning point for me came during a conversation with a senior operations executive at a $20 billion global energy services giant. He shared a brutal lesson from his own career that completely shattered my perspective on frontline compliance.
His division had suffered a catastrophic downhole tool failure on an offshore rig. The incident cost the company hundreds of thousands of dollars in non-productive time, expensive repairs and severe contract penalties with a major oil and gas client.
When his team ran the post-mortem investigation, they discovered something shocking: the field crews had actually known about the tool’s engineering vulnerability for over six months. In fact, they had even developed their own local, unwritten workarounds on the shop floor to keep the machinery from failing.
But when the executive asked why these crucial insights were never sent up the chain to engineering, the answer proved to be a wake-up call. To submit a simple process correction, a technician had to download a PDF, fill out three pages of technical justifications, obtain physical signatures from multiple regional managers and email it to a corporate quality alias.
The feedback went straight into a bureaucratic black hole. After weeks of silence, the techs simply stopped trying.
By making the process so incredibly difficult, the company had effectively silenced its most valuable asset. They paid a massive financial penalty for treating their operators like passive machines rather than problem solvers.
The High-Velocity Feedback Blueprint
Here’s a brand-name use case. Toyota institutionalized frontline ownership decades ago through its famous Andon system. Any worker on the assembly line is empowered to stop production when they identify a quality or safety issue. Rather than treating deviations as worker failures, Toyota treats them as opportunities for organizational learning. The resulting feedback loop has become a foundational element of the Toyota Production System and is widely credited with improving both product quality and operational reliability.
Industrial organizations can apply the same principle with these three practical operating practices.
1. Embed Feedback At The Point Of Use
Never ask a field technician to log into a separate “Continuous Improvement” portal at the end of a grueling 12-hour shift. If feedback requires extra steps, it will not happen.
Instead, build feedback mechanisms directly into the mobile workflow they use to execute the job. If an operator is on step four of a valve calibration and notices a safety risk, they should be able to snap a photo, add a quick text annotation and attach it to that exact step in real time, even if they are completely offline on a remote platform.
2. Establish A Strict 48-Hour Response SLA
Frontline engagement dies the moment workers feel ignored. If a tech submits a process improvement and hears nothing, they will never submit another.
Your regional quality and engineering managers must operate under a strict Service Level Agreement (SLA) to triage comments within 48 hours. Even if the answer is, “We cannot change this step because of regulatory compliance, but we appreciate the input,” that quick confirmation keeps the feedback loop alive.
3. Build A Global Broadcast Mechanism
When an operator in District A solves a safety issue or discovers a massive efficiency hack, you cannot rely on monthly newsletters or quarterly meetings to share it.
You need an operational highway that allows quality leads to review a field suggestion, approve it and instantly broadcast the updated procedure across all global districts. If you can push a process update to 30 operating regions in five minutes instead of five weeks, you prevent the same mistake from happening twice.
The Payoff Of Frontline Ownership
When the energy giant implemented this co-authorship model, the operational impact was staggering.
Once they transitioned to interactive digital standards and empowered their field techs to capture visual evidence of compliance as they worked, the audit time collapsed from three days to just five minutes. Because the technicians felt respected and engaged, they didn’t just follow the digital standards; they optimized them, logging over 6,000 active comments and process improvements in the first eight months alone.
Give your technicians a voice in how the work is designed, and they will show you exactly how to run a flawless operation.
Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?
