10 REASONS WHY CHANGE PROGRAMMES DEPENDENT ON IT FAIL – REASONS 1 TO 3

Project Management Lifecycle

10 REASONS WHY CHANGE PROGRAMMES DEPENDENT ON IT FAIL – REASONS 1 TO 3

There is a long history of change programmes dependent on IT failing.  At the very least they usually carry a high level of risk!  But you can avoid the pit-falls.

This series of posts is based loosely around the UK Government’s “Common Causes of Project Failure” (NAO/OGC) but the interpretation is mine.

Lack of a clear link between the programme and the organisation’s strategic goals

IT Implementations in particular can take a long time, meanwhile the world moves on and markets and technology can change.  Sometimes, surprisingly, aims were not aligned in the first place and the programme carries on in its own sweet way until it founders on a corporate sand-bank – usually the board asking embarrassing questions.

The organisation may have invested a huge amount of resource reaching a place it doesn’t now want to be and/or with a technology that no longer fits.

Most people dislike writing or refreshing business cases because of the sheer hard work   but they does pay dividends.  Refresh your business case at regular intervals to make sure that the programme still makes business sense and will re-pay the investment – which at end of the day is what a business case is all about!

Have agreed measures of success

If you haven’t agreed what success looks like then how will you, much less anyone else including the boss, know when you have it!  Make sure you have clear and agreed Critical Success Factors.  Make sure everyone knows just what you are building in terms of capability and what business benefits will be delivered.

If you think you are delivering five benefits, and the Chief Executive thinks you are delivering ten, you have a problem!  You will still have the problem even when you think you have done a fantastic job!

Lack of clear top/senior management ownership and leadership

You need clear commitment and support from those leading the organisation if you are to succeed.  You will need resources, responsibility and authority to ensure the change is embedded and the business benefits are delivered.

People are more likely to engage if they are getting a clear message from those they regard as leaders that the change has to be made. You may need need decisions from senior management quickly and decisively.  You will get none of these things if they are not on board with what you are doing and prepared to give it their own leadership through you.

Six more reasons

Change Management: Story War
The "problem" with stakeholders! (Photo credit: daveelf)

to go –   the next post tackles  stakeholder engagement and communications, project and risk management skills and avoiding the Big Bang.

I would love to hear what you think about this – do you agree or disagree and do you have examples to quote please.

Wendy Mason is a Life and Career Coach.  She helps people have the confidence they need to be successful at work and to change career while maintaining a good work/life balance. You can email her at wendymason@wisewolfcoaching.com

Other articles you might like

10 REASONS WHY CHANGE PROGRAMMES DEPENDENT ON IT FAIL – REASONS 4 to 6 

10 REASONS WHY CHANGE PROGRAMMES DEPENDENT ON IT FAIL – REASONS 7 to 10 →

3 Replies to “10 REASONS WHY CHANGE PROGRAMMES DEPENDENT ON IT FAIL – REASONS 1 TO 3”

  1. I am always arguing for small scale tests and pilots of possibilities at an early stage – often the users already have a better alternative on their desk top!

  2. Pingback: 10 REASONS WHY CHANGE PROGRAMMES DEPENDENT ON IT FAIL – REASONS 4 to 6 « Wisewolf Talking - resources for those managing or going through change!
  3. Pingback: 10 REASONS WHY CHANGE PROGRAMMES DEPENDENT ON IT FAIL – REASONS 7 to 10 | WiseWolf Talking – the Wisewolf Coaching Blog

Leave a Reply

Your email address will not be published. Required fields are marked *