Winchester BODGIT (Andy Wilson)

885 views
823 views

Published on

Slides created by Dr Andy Wilson (University of Loughborough) for an end-of project Workshop at the University of Winchester. 1st February 2011

Published in: Entertainment & Humor
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
885
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Winchester BODGIT (Andy Wilson)

  1. 1. Change and IT Projects<br /> Dr Andy Wilson<br />Director of Capability Enhancement<br />Loughborough University<br />
  2. 2. Purposes<br />To share some thoughts on change...<br />...and on change wrt IT projects<br />To invite your reactions<br />To identify some recommendations.<br />
  3. 3. Comment<br />I am currently Project Manager of Loughborough’s move from 3 faculties and 20 departments to 10 schools<br />I’ll offer some comments on this experience!<br />
  4. 4. Change concepts<br />The “burning platform”<br />Dilbert and Senge on change<br />Change and loss<br />PESTLE and MORTAR<br />The DICE model<br />What managers can do to help.<br />
  5. 5. The “burning platform”<br />
  6. 6. The “burning platform” 2<br />Sometimes proposed as a way of encouraging change<br />Refers to Piper Alpha disaster 1988<br />Gas platform in the North Sea<br />167 people died<br />The 59 survivors jumped 200 feet into the water<br />This is not how you encourage change.<br />
  7. 7. Dilbert on change<br />Change is good.<br />You go first.<br />
  8. 8. Senge on change<br />People don’t resist change. <br />They resist being changed.<br />Peter Senge<br />
  9. 9. Change and loss<br />Elisabeth Kübler-Ross, On Death and Dying (1969)<br />Often applied to change, sometimes in a rather simplistic way, but…<br />People don’t neatly followthe model<br />The downs and ups arenot straightforward<br />But loss is often a part of even “good” change.<br />
  10. 10. The stages ~ DABDA(M)<br />Denial ~ They can’t do that! <br />Anger ~ They can’t do that to me!<br />Bargaining ~ Well, if they’re going to do that then I want…<br />Depression ~ It’s awful and I feel miserable<br />Acceptance ~ OK, it’s going to happen<br />Moving on ~ Well it’s not so bad, I can deal with this.<br />
  11. 11. On Death and Dying<br />
  12. 12. PESTLE …and MORTAR<br />
  13. 13. The ABCD of Drivers<br />Altruism ~ lip service, maybe<br />Business case ~ benefits to...?<br />Compliance ~ they do it – reluctantly<br />Desperation ~ they do something…<br />
  14. 14. The Hard Side…<br />…of Change Management<br />“Companies must pay as much attention to the hard side of change management as they do to the soft aspects. By rigorously focusing on four critical elements, they can stack the odds in favor of success.”<br />by Harold L. Sirkin, Perry Keenan, and Alan Jackson<br />Harvard Business Review Online, 2005.<br />
  15. 15. DICE Model of Change<br />Duration<br />Integrity<br />Commitment<br />Effort<br />Get these right, and change is much more likely to be successful.<br />
  16. 16. DICE 2<br />Duration = the amount of time between reviews (or the duration of change programme)<br />Integrity = the ability of the team to deliver what is required<br />CommitmentC1=commitment to change of top managementC2=commitment to change of employees affected by change <br />Effort = the perceived effort over and above normal workload that the change initiative demands.<br />
  17. 17. DICE Score<br />1 - 4 (low is good), fractions OK<br />D + 2I + 2C1 + C2 + E<br /><15 Win<br />15 – 17 Worry<br />>17 Woe<br />Double weighting for:<br />Integrity = the ability of the team to deliver what is required <br />Commitment C1=commitment to change of top management.<br />
  18. 18. Loughborough and DICE<br />
  19. 19. What managers can do<br />With all that as a starting point…<br />If you were going through a significant change, what would you want from your manager?<br />
  20. 20. We’d want them to...<br />Give us time<br />Listen<br />Acknowledge our feelings<br />Encourage the expression of feelings<br />Describe reality<br />Explain the drivers<br />Explore options<br />Nudge us forwards<br />Discuss the consequences<br />Ask difficult questions<br />Help us to imagine how it could be<br />Analyse risks <br />Rehearse behaviours<br />Feed back on our mood<br />Celebrate successes.<br />
  21. 21. IT aspects of change<br />WIIFM?<br />The impact of IT change<br />Group think<br />The computer says, “No”.<br />
  22. 22. WIIFM?<br />What’s in it for me?<br />Institutional-level benefits may not look like benefits from the individual’s perspective<br />With IT change some of the institutional benefits may seem fairly obscure…<br />…and some of the personal impacts may seem substantial.<br />
  23. 23. The impact of IT change<br />Consider the “worlds” of different staff groups<br />The academic world...?<br />The support staff world...?<br />And the degree of control people have over their worlds<br />Then think about the impactof IT change.<br />
  24. 24. Group think<br />The tendency for members of a cohesive group to reach decisions without weighing all the facts, especially those contradicting the majority opinion.<br />allpsych.com/dictionary/dictionary2.html<br />Technical expertise – or the lack of it – can reinforce boundaries.<br />
  25. 25. The computer says, “No”.<br />
  26. 26. The computer says, “No”.<br />Remember Senge<br />IT change may seem less negotiable.<br />
  27. 27. Stakeholder analysis<br />I’m seeing stakeholders as those people who have an interest in – or can have an impact on – your change project<br />If you don’t understand who your stakeholders are – and how they feel – then successful implementation will be very hard<br />This tool helps you with this<br />Please agree a project from within your group that you’re going to work on.<br />
  28. 28. Stakeholder straplines<br />
  29. 29. Stakeholder straplines 2<br />In the top part of the circle write the name of the stakeholder or stakeholder group<br />Then, for each stakeholder, try to identify a pithy phrase or strapline that captures their view of the project<br />Here are some examples from the Loughborough project...<br />
  30. 30. Stakeholder straplines 3<br />Depart-mental admin staff<br />Academic staff<br />Senior managers<br />It’s the second envelope!<br />Will I be made redundant?<br />This must happen<br />
  31. 31. Stakeholder straplines 4<br />Your straplines?<br />Do they tell you anything about what you need to do to make your project work?<br />
  32. 32. People and Technology...<br />...your recommendations<br />It’s not rocket science<br /><ul><li>People do tend to get forgotten
  33. 33. Especially teams
  34. 34. What recommendations would you offer concerning IT-related change?</li></li></ul><li>
  35. 35. Stakeholder straplines?<br />Academic staff<br />IT staff<br />Senior managers<br />So what am I not going to do?<br />You should have asked us about it beforehand<br />So now it will just happen<br />
  36. 36. Traffic lights<br />
  37. 37. Fundamentals<br />Establish the case for change<br />Visualise how the new world will be better<br />Establish a set of shared values<br />Resource the change initiative appropriately<br />Lead by example<br />Assess capability and capacity<br />Engage the team in the change process<br />Communicate the change in a timely and sensitive way<br />Ensure senior management commitment is visible.<br />
  38. 38. Dealing with negativity<br />
  39. 39. Another project and DICE<br />

×