The systems “X” mentioned earlier is a long run preestablished system implemented before I work there, so I don’t know much about the pre-implementation change management. However, the system is underused nowadays. It supports options that helpful for both operational and decisional. The system supports, for instance, medical coding, a location identifier, messaging system, expenditure log, but none of these is is used. Usage of the system must be redesigned by bringing all stakeholder discussing on what they want from the system and what the system can help them work. Considering the ADKAR for the executed system; all have already been awarded about the system, and there is no resistance, so we may skip the “Awareness” and “Desire” as they are already mandated to their jobs and jumping into the “Knowledge” by giving all operational agent a formal training and coaching on how the system work and what it can contribute to work. The “Ability” maybe only to catch up on options of the system that not regularly use but vital. After the usage has been re-implemented, we must have to measure some critical or bottleneck step and correct the inappropriate usage as the “Reinforcement”.
- This reply was modified 4 years ago by Ameen.