change management horror stories

In a manufacturing company, a change in the production process was made. The new process required different machinery, but the old machines were not removed right away. Workers were constantly switching between the old and new ways, which was very inefficient. There were also safety concerns as some workers were not fully trained on the new machinery. Eventually, there were several small accidents that could have been avoided with better change management. This shows that when making changes, it's crucial to have a clear - cut plan and ensure all aspects are considered before implementation.

Lack of communication is a big one. When employees are not informed about the change, they get confused and resist it.

Surprise is a key element. For example, when employees come up with unexpected ways to react to change like the guy with the beach umbrella in the open - plan office story. It's the unexpectedness that makes it funny.

Employee involvement matters a great deal. In many success stories, employees are involved in the planning and implementation of the change. They can provide valuable insights and also feel more ownership of the change. A software company that let its developers be part of the new software architecture change had a smooth transition.

There was a case where the property management didn't maintain the common areas. The hallways were dirty, the lights were out in some areas, and the elevators were constantly breaking down. They kept saying they were short - staffed but did nothing to improve the situation. Tenants were unhappy and some even considered moving out.

There was a restaurant that had a rodent problem. The manager tried to keep it quiet, but eventually, customers started seeing mice running around. It was a nightmare for the reputation of the place. The health department got involved, and the restaurant had to close for a while to fix the problem. They lost a lot of business during that time, and it took ages to regain customers' trust.

One horror story is when a project manager didn't communicate well with the team. He just gave orders without explaining the overall goals. As a result, the team members were all working in different directions. They wasted a lot of time and resources on tasks that were not really relevant to the final outcome.

Clear communication is key. In successful ITIL change management, all stakeholders are informed about the changes in advance. For example, in a software company, they send out detailed change notifications to all relevant departments. Another important element is proper risk assessment. A hospital that implemented ITIL change management carefully evaluated the risks of each change to their patient care systems. If the risk was too high, they would postpone or modify the change.

There was a software company that was changing its project management methodology. The new system required everyone to use a new set of software tools. One developer, instead of following the training, tried to use the old software in a creative way to mimic the new functions. For example, he used the old bug - tracking system to create 'fake' tasks that looked like the new ones in the new system. When the managers found out, they couldn't help but laugh and then provided more one - on - one training to him.

A tech startup had a successful change management when they shifted their business model. They first analyzed the market trends thoroughly. Then, they engaged with their investors and employees in open discussions. By gradually introducing the new model and providing continuous support, they not only survived but thrived in the competitive market.