Implementing systems in healthcare organizations has been a central part of my career, spanning from department-specific solutions to enterprise-wide applications that impact every employee within the organization. Throughout this journey, I\u2019ve learned many valuable lessons, but the most important one is user adoption. No matter how well-designed or architected a system may be, the user\u2019s engagement with it can make or break its intended benefits.
My most memorable and rewarding experience with user adoption was also my first system implementation, impacting several departments. It took place in the 1990s, when my manager negotiated a deal with our primary supplier, marking our first steps toward what would become a \u201cjust in time\u201d supply chain system. Once that was in place, we quickly moved towards implementing an ERP system. At the heart of this initiative was the challenge of transitioning our buyers from electric typewriters to the very early versions of PCs. While setting up the EDI transaction systems was straightforward, convincing the staff that PCs would reduce overhead and improve efficiency was a task in itself.
The biggest challenge wasn\u2019t the technology\u2014it was overcoming the resistance from the employees. Many were reluctant to use PCs due to fear of the unknown: they worried about their ability to master the technology and, more importantly, about the risk of losing their jobs. To address these concerns, I engaged with the staff directly, holding multiple sessions to understand their workflow and identify bottlenecks. We discovered that communication breakdowns, missing forms, and pricing discrepancies were creating operational inefficiencies. I walked them through how the new systems could address these issues and improve the overall flow.
Next, I tackled the fear of technology. To help the staff become comfortable with PCs, I made sure they had fun with the learning process. I encouraged them to play Solitaire, using the mouse and navigating the system. By the time they were hooked on the game, they had already mastered basic PC functions. What started as a tool for entertainment soon became a gateway for learning\u2014and those sticky notes that once cluttered their screens were replaced with productive use of the PCs.
The next step was to build an application that mimicked the old typewriter system and forms. Using a basic forms package, I created a system that not only allowed them to complete their tasks without manually mailing or typing documents but also automatically routed the documents to the appropriate departments, making them available for printing on demand. This transformation was met with excitement, as employees saw how much easier and faster the system made their work.
The next phase of the project focused on taking it one step further. I introduced the idea that with the new system, we could directly communicate with the vendor, place orders, receive status updates, and confirm pricing\u2014automatically. This concept thrilled the team and opened the door to further system enhancements.
While I won\u2019t claim that everything went perfectly\u2014there were certainly challenges and a bit of luck involved\u2014I can confidently say that the project was a success. There were things I would have done differently, and improvements to be made. Nonetheless, this experience provided invaluable lessons on user adoption, system implementation, and overcoming resistance to change. In my next article, I\u2019ll dive into the next giant leap: transitioning from faxing to EDI and implementing an enterprise-wide ERP system.
","image":"/home/gpeag8ru79y1/api.enrickramlakhan.net/static/uploads/download_4.png","slug":"introducing-systems-to-operational-employees-a-journey-of-transformation","title":"Introducing Systems to Operational Employees: A Journey of Transformation "}