In Part 1 we covered the areas to investigate when you have been engaged to 'fix' a change that has gone awry! 

So now let's see what actions to take, and who should take them if you have areas to 'fix' and fast.

Revisiting Scope: When it comes to reviewing scope the question to ask is was what was left out of the scope that should have been addressed? Many times the scope missed out on one of these elements which impacts the change. This sits with the Project or Program Manager.

Be sure the program scope covers the following:

Policy or procedure changes necessary

Process changes

People changes if needed

Technology change, as well as addressing possible migrations and transitions from old to new.

If there is a change strategy you need to be clear as to the Change scope. Does it include change and communications interventions and any Capability uplift deliverables.

If this is a large change it is worth comparing both the program and change plans to make sure all scope items are...

'It's just a change of reporting line' he said. 'Here we go again,' I thought. So I took my time walking through the changes, the impacts and what would need to be done. Luckily by the end I also got the response I had hoped for 'I get it now'. Every now and then, the outcome is different. I get the first comment and no matter what I cover, the impacts won't be acknowledged. There is sometimes a preference to play down the change. And without doubt as the change process takes place, there is a reaction to the emotional push back and its intensity that is experienced. My comment in these instances is - well this change isn't about you, and people don't react how you would react, they react based on how they feel. The only hope I can have in those cases, is that when it happens again the same leader will pay more mind to their people.

When Leaders have a case of the 'Dory's'

Remember Dory from Finding Nemo? She had a very bad memory and this can also be case of many leaders when they...