Managing change in your organisation is a real challenge - lets talk about it, develop ideas, and rant and rave. Let's remember that change in people's business lives affects their real lives too.

Showing posts with label change programme. Show all posts
Showing posts with label change programme. Show all posts

Thursday, 14 June 2007

Change fatigue, kissing frogs and eating elephants

You have to kiss a lot of frogs to find your prince (why is it never princess?). This is the same with change in a lot of organisations - you have to make a lot of changes to get to your optimal position, some will be successful and others won't. Sad really that we continually flog ourselves in our business lives to get to a position of 'optimality', but achieving this is often a meandering slog.

And worse, we're never sure when we've kissed enough frogs and found enough princes/princesses to achieve our goal - perhaps you can never have enough, perhaps we don't know what our goal is, or someone keeps moving the goalposts?

That's enough about frogs. The real point of this note is to try to write down the reasons why organisations experience perpetual change, and what can be done to minimise change if appropriate. I hope readers have their own ideas to add.

Change fatigue is experienced by most of us at points in our professional (and personal) lives. You can see it in other people when they roll their eyes, slump their shoulders, drag their feet, gossip and whinge etc upon announcement of another change - somewhat unexpectedly the small changes to things like organisational design often get the same reactions as more significant changes (shock, anger, etc). People are people - they have egos and personalities and whatever is changing around them they're looking at the following questions;
  • what's in it for me?
  • was I asked?
  • when and how?
  • how does it really affect the things I care about?
  • why is it happening yet again?
Let's look at why perpetual change happens;
  • because it can. Cynically it gives managers something to do. I don't really think this is common in the real world though, it is often about 'eating the elephant' - lots of changes ('bites') need to be made to enable the ultimate goal ('eating the whole elephant') to be achieved.
  • Using the elephant analogy further, do we really know what the scale of the elephant is? Is there a corporate strategy that elaborates the desired end-state, and what the journey is to get there in terms of underlying operational strategies ? If this isn't clear, then there may be false starts, and false end, leading to the perception of piecemeal change and hence change fatigue.
  • Will the elephant stand still? Clearly a lot of changes are foisted upon organisations by regulators, governments, local authorities, professional bodies etc, and these cannot always be planned for. Some of these changes will be planned, others will not. There are a number of other external factors that cause organisations to have to implement unscheduled change, such as competitive pressures, new products, business opportunities, M&A and the like.
  • How many elephants do we have? Nursing a herd is harder than just one, particularly when the want to move at different rates, go off on diversions, sleep and eat at different times.... The elephants will always need a different degree of nursing too - how much management time does each project require, and can they be managed collectively?

I'm sure that I could continue talking about elephants further, but the point is that there are good and meaningful reasons often why there is perpetual change (sometimes there is not), and I'll list the things that can be done to minimise the change fatigue.

  • Ensure that you have a strategy and a lucid desired end-state. And communicate it so that everyone knows where they are going and can learn to deal with it, and participate! If you tell a group of people that their roles are to be outsourced, then tell them everything (as far as you can), get them to meet their counterparts, understand the implications, get involved in the transaction and transition etc, as there will be a huge number of things that have to happen before the final transfer happens. It is in everyone's best interest that the change is a success.
  • Have detailed operational plans and strategies that map into corporate level strategy. Makes sure that the managers responsible stick to agreed plans.
  • Manage all change in one place - you should aim to get one view of all change across your organisation, and manage it as a cohesive whole at a macro-level. If anyone wants to change their plans, make an announcement or accelerate/decelerate, there is then a means of governance and ensuring that the implications of any adjustment are considered. This is a programme management or change director role.
  • Ensure that there is clarity of sponsorship - knowing that there is a senior sponsor (or the Board for significant change programmes) overseeing what is happening helps calm nerves. But sponsorship must be earnest and visible, otherwise it will not help.
  • Continue to communicate to all stakeholders throughout - once you've set along a path, keep coming back and telling stakeholders what is going on, and ensuring that there is two-way communication, websites, announcement plans and so on. This stops a lot of the worry, angst, gossip and wasted effort. If plans change, then communicate to people as soon as you can. If new things need to happen, communicate as soon as you can. You need to ensure that all key relationships are managed explicitly - if relationships fail, then you are more likely to fail.
  • Design your plans such that there are 'islands of stability' - periods where nothing new happens, everyone has a rest, focusses on the job. This will pay dividends.

Of course, the list above is just a list of things to do for well-managed change initiatives, but that is what makes them well-managed and what helps prevent change fatigue. It is people that stop change, so if you don't deal with the people aspects of change there is the real risk that your change programme will fail.

Wednesday, 17 January 2007

Why do we deliver change...to create value

We deliver change to create value - that's it. I've written on this subject before but given one or two discussions I've had recently thought it worth reiterating the point.

Change is a difficult thing. But it must always have an ultimate goal - in corporate life we deliver change because it creates shareholder value (it is difficult to see any other reason), and in the social and governmental sectors we might go through a change programme to establish some social or environmental improvement. Why would you go through potentially gut-wrenching change for no good reason?

Thursday, 4 January 2007

Project Management and Change Management

There is a debate going on in another forum about the use of structured project management methodologies (eg; Prince 2) versus the management of change. We need to be clear that project management is not the same as change management - managing the project is part of managing the change, but it is a relatively mechanistic process, providing the assurance of technical delivery and to some extent the delivery of the benefits. Change management is about delivering the behavioural change that ensures that the benefits endure, that the technical changes are accepted, and that the expected outcomes are achieved.

Another way of looking at this is that there are many more people involved in delivering the change (the sponsor, Board, managers etc), whereas the project processes can be delivered by the Project Manager (who, if they are enlightened/experienced will be focussed on delivering the change as well as the technical delivery).

One thing that annoys me is where some third party suppliers/partners (in IT particularly) tend to come along after winning a contract and expect that they can simply implement their bit of technology and it will work and be accepted - they often get a shock and then cost overruns etc, and consequently relationships start to fail between supplier and customer....the real world is difficult!

Here's a link to a basic project/change role comparison from the change management learning center if you're interested.

Wednesday, 3 January 2007

Change training and development

I was asked today about change training and development.

I know there are a few public courses around, but in my view bespoke training related to a particular business sector is most helpful - different sectors tend to have different challenges, ways of operating, language etc, and all of these things are important in how people act and react to change. Probably the best course that I've run is a focussed 'advanced' training within the Financial Services sector, based on 'real-life' case studies and a little bit of role playing. This allowed participants to establish an approach to managing through change (at a very high-level inevitably) in a safe environment - and its loads of fun too!

If training can be supported by mentoring, so much the better.

Wednesday, 6 December 2006

Accelerating change

I had an email today about a global company that needed someone to help the finish a programme that had been running for two years - it sounded as if it had faltered and they need change consulting effort to move it to its conclusion.

Two years into the programme and they start worrying about the people impacts!! This reminded me of a great book I've read a couple of times - 'Five frogs on a log' by Mark L Feldman and Michael F Spratt. The book is about acceleration of change, particularly in an post-mergers and acquisitions situation. The title comes from the story about five frogs sitting on a log, one says 'shall we jump', and all agree that they should - of course they don't actually jump because saying you'll do something is differrent to actually doing it.

Back to the point, Feldman and Spratt use a great analogy for change - they liken it to removal of a sticking plaster; remove the plaster slowly and the pain lasts longer than pulling it off quickly - 'rip, sting, gone'.

Not all projects can be completed quickly, but you need to move those affected to an 'acceptance' position as quickly as possible. This is a measured process - in some situations you may not be able to talk to people as soon as you would like (eg; redundancy) - but that doesn't prevent detailed analysis and planning.

Monday, 4 December 2006

What normally happens in a change programme?

People talk to me about what I expect will happen in their change programme...the short answer is 'who knows?', but that isn't terribly professional or practical!

As it is people that stop change, make change happen, embrace change it is not very easy to say that one person, cadre of people, team etc will hold a specific view and will take a particular position. But if nothing is done to get people to support a change then, unremarkably, there is a real chance that nothing will happen. How many times in our professional careers have we seen that an IT system enhancement is delivered, but all the users do is carry on working in the 'old way'? How long did it take some colleagues to use email, rather than secretary-typed memos!

People have egos, issues, personal crises, work ethics, social, political and religious viewpoints, hangovers....they all need nurturing to work through a change. They will go through various stages dependent on their starting point (based on Elisabeth Kubler-Ross' work );
  • denial ('this can't be happening');
  • anger ('why me - I won't let it happen');
  • bargaining ('if I do this, what will it mean for me')
  • depression ('Ok, I suppose that we have to do this')
  • acceptance ('Let's just get on with it')

We can talk about whether these are actually the stages another day, but the principles are appropriate.

The challenges do not stop with an understanding of where individuals are with respect to working through the stages - because teams, unions, 'coffee-machine cliques' all have different views, as do managers, boards, shareholders, customers - every individual stakeholder and stakeholder group will need to be managed through the change - and working out which individual or group can really prevent or delay or change and then dealing with it is really what makes managing change interesting. For some individuals or groups a simple website with a feedback mechanism might be sufficient, others might need weekly briefings and monthly reports, others might reasonably be totally ignored - it is the structured approach to this, with regular monitoring via a 'heatmap' or similar that will help ensure that your change is successful. Alongside all of this, you have to ensure that the practical aspects of the change on a time/cost/quality basis is delivered successfully too!