The reasons system implementation fails

Full Answer Section There are a number of different change models that can be used during system implementation. Some of the most common change models include:

• The Lewin Change Model: This model is based on the idea that change occurs in three stages: unfreezing, moving, and refreezing. The unfreezing stage involves creating a sense of dissatisfaction with the current state of affairs. The moving stage involves implementing the new system. The refreezing stage involves stabilizing the new system and preventing backsliding.
• The Kotter Change Model: This model is based on the idea that change requires eight steps: creating a sense of urgency, forming a guiding coalition, developing a vision, communicating the vision, empowering others, removing obstacles, celebrating short-term wins, and anchoring the changes in the culture.
• The ADKAR Change Model: This model is based on the idea that change requires five things: awareness, desire, knowledge, ability, and reinforcement. Awareness is the first step, and it involves understanding the need for change. Desire is the second step, and it involves wanting to change. Knowledge is the third step, and it involves understanding how to change. Ability is the fourth step, and it involves having the skills and resources to change. Reinforcement is the fifth step, and it involves maintaining the change over time.

The best change model to use during system implementation will vary depending on the specific circumstances. However, the Lewin Change Model and the Kotter Change Model are two of the most common and effective change models. If I were to select a change model to use during system implementation, I would choose the Lewin Change Model. This is because I believe that it is a comprehensive and effective model that can help to ensure a successful implementation. I would use the Lewin Change Model by following the three stages of unfreezing, moving, and refreezing. In the unfreezing stage, I would create a sense of dissatisfaction with the current state of affairs by highlighting the problems with the old system and the benefits of the new system. I would also involve the right stakeholders in the planning process and communicate effectively with users. In the moving stage, I would implement the new system. This would involve training users on the new system, providing support, and troubleshooting any problems. In the refreezing stage, I would stabilize the new system and prevent backsliding. This would involve monitoring the system and making adjustments as needed. I believe that the Lewin Change Model is the best choice for system implementation because it is comprehensive and effective. It takes into account the different stages of change and provides a framework for ensuring a successful implementation. The following are some of the steps that should be included to ensure that the change model is effective:

• Planning: The change model should be carefully planned and communicated to all stakeholders.
• Communication: Effective communication is essential for a successful change implementation.
• Training: Users should be trained on the new system and provided with support.
• Troubleshooting: Any problems that arise should be troubleshooted and resolved quickly.
• Monitoring: The system should be monitored to ensure that it is working properly and that users are satisfied.

By following these steps, you can increase the likelihood of a successful system implementation.

Sample Answer System implementation failures can occur for a variety of reasons, including:

• Poor planning and communication: If the system implementation is not properly planned and communicated, it is more likely to fail. This includes not having a clear understanding of the goals of the implementation, not involving the right stakeholders, and not communicating effectively with users.
• Technical problems: Technical problems can also lead to system implementation failures. This can include problems with the hardware, software, or network.
• User resistance: User resistance is another common reason for system implementation failures. This can occur if users are not properly trained on the new system, if they do not see the need for the new system, or if they are afraid of change.