« escape | Main | Tui thriving in Wellington »

Leading Effective Business Change

Jim Donovan has some good advice on how the project team should be drawn from the best people in the organisation, and on how to lead and generate effective business change generally. His advice is given as '10 rules' (emphasis mine):

1. The project team should be drawn from the best people in the organisation, the ones who will drive the new way, and will likely hold leadership roles in it. Don’t staff projects with your third-rate cast-offs. Don’t rely on contractors for roles that should be held by business experts.
2. The naval officer on site in the dockyard overseeing the construction of a new ship is ideally the officer who will be its first captain. The best person to lead a change project is the person who will run the new process afterwards. Failing that, get someone even more qualified and powerful, not less, to be your change agent. Sitting on a governance committee is not enough.
3. The change leader and the change team must have been indoctrinated into the new way of thinking, and be passionate, effective advocates as well as good at their jobs.
4. Don’t treat change as an IT project, even if largely based around new IT systems. It’s a business project. The best businesses train their business managers in smart project management, process design and change management. These are not IT skills, they are business skills. Having said that, good business-savvy IT people can make great business change people if you also follow rules 1, 2 and 3.
5. Be ambitious but realistic about what you can achieve with the money, time, resources and ownership support you have available to you. Despite knowing this, I too have sometimes fooled myself or been pressured into going ahead on over-ambitious projects without adequate resources, with predictable results. Heroism, hope and luck are not reliable ingredients for success.
6. Give the change leader the power to decide, as far as possible, and have fast access to higher decision-makers when necessary. There is no value-add and much cost from constantly briefing and waiting on uninvolved decision-makers.
7. Like any major change proposal, nothing will happen unless you dedicate resources (people, time, money) to make the change happen. Expecting people to design and implement a major change while doing their day jobs rarely works, especially when their core process is broken. Put your best operational people onto the change project; here’s where you can usefully deploy contractors - to fill in for them in the operational teams.
8. Avoid highly structured project management methodologies. I recommend a much more agile, lo-tech approach. Don’t try to specify everything before you start. Have a high level “architectural” concept to guide you, but get going!
9. Keep the alligators at bay, but focus on the swamp draining. Don’t worry about dealing with the current stream of problems - that’s the job of the operational teams. Put in place some holding plan, but concentrate your best resources on creating the new model that will work. Get it working, put all new customers, and new transactions onto it, transfer all customers without problems onto it, and then, last, not first, deal with the problem backlog.
10. Notwithstanding rule 9, try to deliver value quickly, in chunks, rather than going for the big bang. Incremental success builds support.
11. Bonus rule: communicate, communicate, communicate; up, down, across, inward, outward.

This is great advice Jim, which lines up with my experience as a project manager bringing about business change, often enabled by IT.


References (1)

References allow you to track sources for this article, as well as articles that were written in response to this article.
  • Response
    Response: http://www.bbb.org
    Gavin Knight .com - Blog - Leading Effective Business Change

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>