Leading the Change: Why Adoption Fails and What to Do About It

Bob worked his way through the maze of round tables towards the door, cellphone in hand. Once in the hallway, with the music from the wedding band distant enough for him to hear himself talk, he answered. 

The name on the phone was Carlo, the manager from the 3-11 shift. He could already guess the conversation he was about to have.

“Sorry to bother you Bob. How’s the wedding?” Carlo said once Bob answered

“Going fine, Carlo. What’s up?”

“We’ve got another failure on line three. This time it’s one of the feeder pumps.”

Bob felt his blood pressure rising. The feeder pumps were hard to access, and that meant trouble. “How long?”

“We’ve got to get one of the lifts, so it will be a few hours at least. But we’ve got plenty of spares so that’s good.”

Carlo talked about the spares like it was a positive, but all Bob could think of was the grilling he’d gotten from finance at the last order for spare parts. They were over budget already, but the team kept buying more, afraid they’d be caught short if something broke, like they had a few months back.  

“Did we have any warning?” He asked.

There was a pause. “It’s been a few weeks since we’d looked at that one,” Carlos said. “We’re behind on our routes since Marcy retired.”

Bob rubbed his temples. “Isn’t that one of the machines we’re covering with the new predictive monitoring system?”

A longer pause this time. “It is. I know what you’ll say. We’d gotten an alarm the other day saying there might be an issue, but the team decided to wait until they could do a manual review to see if anything was really wrong.”

“So they ignored the alarm?"

“They say they’re just too busy to tear down a machine just because a light went off on some new system, Bob. They wanted more proof.”

Bob sighed but decided now wasn’t the time for another fight. After that major failure in January had brought the line down for three days while they waited for a motor to be air freighted in,  he’d freed up budget to buy a digital system that could monitor the machines every hour and give the team warning when a failure might be coming. But the team was refusing to accept the new solution. Tony, the Vibration Analyst who covered the plant, refused to trust the alerts that the system provided and insisted on keeping the route based approach they’d used for months. The technicians didn’t like having a system ‘tell them what to do’ and kept saying they were too busy just keeping the line running to mess with something new. After that major failure the team simply increased the volume of spares they kept on hand and doubled down on their preventive maintenance routines- which was driving up costs but hadn’t prevented three smaller but impactful failures in the weeks since January.

Bob finished the call with Carlo and made his way back into the reception hall, but his mind was still lost in the issues at the plant. He knew the new technology he’d invested in could make a big difference. He’s shown his team the references and even had the vendor do a workshop with them. But the rollout was met with resistance at every turn, and even with the system up and running his teams refused to use it the way he knew they could. He kept chiding them and running the report to show them the issues the system was raising but they refused to respond. He was spending more money on parts and maintenance than ever, but getting less for it.

He sat down with a scowl on his face, trying to figure out what had gone so wrong.

What did go wrong? We’ve all been there: seeing a new process or new technology that we knew could have a big impact on the business, only to see it fall short for all the wrong reasons. Adoption goes too slow. Old habits don’t change. The teams stay too busy ‘firefighting’ to learn the new systems. The very issues that the new solution could address become the reasons it never gets adopted.

But sometimes it can be different. The change does happen. Productivity goes up. Stress goes down. Weddings don’t get missed and the plant runs better than ever. What makes the difference between success and failure? 

That’s what we’ll explore in this blog series.  Based on our experiences across literally hundreds of rollouts of our machine health solution across different industries, geographies and company sizes, we’ve seen the patterns that can lead to shining success or frustrating failure. We’ve identified the fundamental challenges and tactics that can help ensure success for any technology rollout or new process change, and we’ll share them with you to help you make the kinds of impacts we know you want to have on your team and your business.

Be sure to check out all the Lead the Change posts!

Tagged:

Comments

  • Brian, great example and topic overall. I look forward to reading (and responding) to your upcoming posts.

    I too have seen the good, bad and ugly when it comes to both, digital tool performance and the adoption of digitial tools in general. While every organization, culture and roll out is different, where adoption is concerned I have found ways to overcome many of the barriers. Too often organizational leaders tend to treat these initiatives as one-off's or limited reach. This is especially true in the area of machine health as mechanical equipment and components are treated only as discreet assets and maybe only the maintenance personnel need to be involved.

    What could be wrong in not including mfg ops or production? What could be wrong in not including Procurement, MRO/storeroom, Continuous Improvement/Reliability or the E&I/Controls organizations? What could be wrong with depending solely upon a maintenance discipline that is expended due to constant fire-fighting, devoid of FMEA, after-action reviews or other reliability disciplines, who (due to no fault of their own) may be the most biased of the mfg orgs and working in "hero-mode" at the same time? I say it often that the best adoption enablers are process health exploiters. See the big picture, include everyone and don't treat equipment/assets as discreet components when they impact the process mission.

  • thanks Scott: keep the great insights coming. Full adoption of new technology is the hardest thing to achieve quickly - everyone who has led these kinds of projects has experienced the highs (and lows) of this.