There are quite a few stories out there about project failure caused by poor Organizational Change Management (OCM) or complete lack of OCM. What about successful Organizational Change Management? I have always felt like fashioning Change Management after a marketing campaign was a very good way to go. I was working on a huge worldwide program for a very large pharmaceutical company that had the best OCM I have ever seen. All of the leaders supported the change. This involved a good deal of their time as they had several events to help the users understand the importance of the change and rally around it. They communicated very frequently and in many different forms. The program leaders made sure that they were getting requirements from all locations participating. Obviously the leaders of the organization were willing to spend money to handle the people side of change as they could see there would be a return. We all know that huge worldwide programs can be the riskiest so the company did all in its power to try to ensure success.
And then there was the time I was brought into an organization to bring a great deal of change. The CIO wanted change. The PMO Director wanted change. Everyone wanted change! They just didn’t agree on what this change looked like! But they agreed it needed to be done yesterday (they really did as they had been looking for a resource to lead this for quite some time). This caused a great deal of resistance from the people who had to do the work to get the projects completed. And then there were the various businesses under the corporation who needed to come together to help develop the requirements that would work for all. I worked with the sponsors to ensure they stood behind the changes required from the program. I built targeted communications for all the various areas of the organization and communicated frequently. I didn’t have the luxury of a big budget and many resources to ensure OCM success for the program but I was a big fan of the solution so my enthusiasm kept me going. And as I said most of the people in the organization realized that several things needed to change as things weren’t going so well before the program was implemented.
When I was researching for a keynote speech I was to present, I came across a very inspiring story of a project success. The two hour house. One of the major elements of the very successful project was people working together because they really believed in the project. This project wasn’t about change in an organization but it was about people really believing in what they were doing. And that is what you want on OCM – for people to believe in the benefit to result from the project. For that particular project the “benefit” was proving they could build the house per a 2 hour schedule. In the end they were proving out the major elements they felt must be in place for success of the project (very detailed planning, risk management, only dedicated believers on the team, contingency planning etc.).
I was just reading a study of Project Failures which got me thinking about the warning signs. The following are true warning signs and issues I have had or witnessed in my Project Management career.
You know your project is in trouble when:
1. The project team was just assigned but the customer wanted this 6 months ago. And the deadline isn’t changing from the original.
2. Your project team is very unhappy because the project has this overly aggressive schedule.
3. You have some team members that don’t like each other – to the point they are acting like 5 year olds asking you to remove the other team member. Time to provide a lecture on being a good team member (and acting like a grownup).
4. Your sponsor is nowhere to be seen – has completely dropped his or her sponsorship of the project.
5. One of the team members has developed a mantra: “I will have that done tomorrow”. This task was due last month!
6. The project contract has a specification that is tighter than the spec your team felt they could meet.
7. Your designer has kept a secret from you: that he doesn’t have a clue how to design the solution.
8. Your stakeholders selected the software – very thorough analysis of alternatives involving tons of people and tons of hours. They selected the application that will work much better than any alternatives. Unfortunately, that is not the application you are implementing. At the last minute an executive informed you that you were to buy one of the alternatives. He claimed that, as a company, we only purchase from this major software vendor.
9. Stakeholders are not happy about this change but they are happy to tell you they don’t want this change.
10. You day-dream a good deal about changing careers.
Some ideas around these project issues:
• Good risk management is important. At the beginning of the project work to determine what can go wrong and what you will do about each risk. This is not just for the PM to do but the entire project team will be valuable in working on this.
• Thorough stakeholder analysis and management will help avoid users that don’t want to use the new system or process.
• Research has shown that a project with no sponsor is more likely to fail that a project with a strong sponsor.
• Communication, communication, communication – with the project team, the sponsors, the stakeholders
o This includes communicating problems – along with what needs to be done to solve the problems.
• If faced with aggressive schedules make sure this is included in your list of risks. This is a difficult issue. The customer always wants it asap and meeting all goals and high quality and in budget. That is a daunting task!
What signs of project trouble have you had? And what did you do about it?
I hear this question often so I have come up with ideas to help those of us who believe in Change Management convince others of the value.
Most projects involve people changing. They have to use new technology or they have to use a new process or maybe take on a whole new role because of a reorganization. There are many scenarios and we all know that change takes us out of our comfort zone. You may even have change saturation in the organization.
Why do we need change management? That is touchy feely stuff!
For a new process or technology project, or both, the ROI is generally based on the assumption that users will adopt to the change at go live and will be proficient. What if the people aren’t ready or are resistant to change? Your return will be pushed out and will not be what you expected.
Loss of productivity is an issue whenever you upset the status quo. When people are anxious about a change or resistant to the change, productivity goes down. By working with people to understand the root cause of the resistance, you can minimize this negative impact by helping people understand the business value and personal benefit of the change.
Ultimately projects can fail when change is not handled properly. People can revert to the old way of doing things. There are many business cases out there about major losses caused by failure to pay attention to the people side of the project and properly bring the individuals of the organization through the change.
In summary, Organizational Change Management enables transition to achieve and sustain the desired business strategy and drives ROI through:
– Accelerating the Adoption Curve
– Ensuring Proficiency
– Minimizing the dip in Productivity
– Increasing project success
Let me know if you have other ideas for “selling” change management to those who don’t get it.
The other day I was thinking I could get a 3 year old to eat something he had not tried before. My husband just laughed and reminded me that the child’s favorite word is no and trying new things has never been a priority for kids. He was right. Little kids are very change resistant, especially when it comes to food that looks healthy.
We don’t get any better about change when we grow up. We all like our comfort zone.
But we all know that change is constant and usually targeted at improvement. So we need to be like surfers, not 3 year olds. When I was on vacation this year we stayed on the beach. When we got up the surfers were already out there waiting for waves. And all day they were out there ready and waiting for the big change (a big wave) to come along. Of course we don’t really want to wait for change, we need to make positive change happen. I think there is great power in having an organizational culture that understands the dynamics of change and how best to implement change successfully. To ensure this, the organization needs competency in Change Management and buy-in for change at all levels of the organization. It works, I have seen it happen. I have also seen big losses caused by ignoring change management.
So we don’t want to be like 3 year olds and we don’t want to be patient surfers just waiting for change. Like people who turn houses, we need to always be making things better.
Projects are about improving or fixing things. So it should be easy to get people excited about the change that comes from the completion of a project, right? Not really. People don’t change. Status quo is easier. Here are the top reasons people are resistant to change.
1. Preparing for the change requires a lot of work. We have to learn new processes, systems, and new ways of doing things. This causes anxiety – what if I can’t do my job as well after the process changes? What if the new system is impossible to use?
2. There are uncertainties around change. We really don’t know how things are going to go after the changes are put in place. Uncertainty is scary!
3. The organization usually tells us why this is good for the business, or sometimes not. But what does it do for me? We don’t always get that message and lets face it, what’s in it for me matters. We have to take time out of our very busy schedules to get ready for the change so it helps to have strong motivation. Sometimes leaders don’t provide that motivation.
4. Many of the C levels in organizations didn’t get to the top by worrying about people’s feelings. They are not the touchy-feely type (I didn’t say everyone). They do know how to network and they can be friendly but the CFO doesn’t need to be expert in HR. So worrying about whether the people of the organization have concerns about the major changes in progress often isn’t at the top of the Executive to do list. Unfortunately, you can’t ignore that the people of the organization have to change and there are going to be some negative opinions about almost any change. This has to be taken into consideration and dealt with. Managers have to talk to their reports to understand concerns!
5. It could be that the people really understand and want the change. However, if major changes often fail in the organization, there is no trust that this project is going to succeed or even be completed. And one thing we all don’t like is feeling like we are doing a lot of work for something that might be abandoned or just won’t work.
So most Change Management theories say you must win the people of the organization over that the change is great, will be successful and will improve the lives of the members of the organization. Promoting the change as a marketing campaign (with the organization as the audience) can work wonders.
“Lean” organizations are so common today. Doing more with less is such a popular slogan. While the Portfolio of projects, initiatives and tasks is “super-sized”, the staff to complete all of this work is not big enough to get it all done. If resource demand is much higher than capacity, some things just aren’t going to get done, projects will fail, mistakes will be made and people are going to be very unhappy. This is a sure way to lose the best people.
Your organization will always have tons of ideas for improving business, improving processes or buying the latest technology. But you can’t do it all! However, you can stick to a very solid corporate strategy and prioritize what gets done based on the strategy.
Right-sizing the Portfolio of Projects and Initiatives:
1. Develop a clear, solid Strategy based on your organization’s core competency.
2. Communicate the strategy so that everyone knows how to translate the strategy into what gets done.
3. Develop a method to determine value of projects and initiatives (relate to strategy and other benefits to be realized).
4. Prioritize the portfolio of projects and match resource capacity and demand.
While your organization certainly is made up of superstars, they aren’t super human. There really are only 24 hours in a day and you really do have finite resources.