This is an oversimplification of this point. So if a change management process is taking to long or is an arduous process then we know we have it wrong. Yes, this would have to be my personal number one bug bear with some change management processes.īut as we mentioned earlier ITIL tells us the change management should “Provide value by promptly evaluating and delivering the changes….” However, as we will see, there is no need for Change management to be as complex as people think it will be. Not sure where to startĬhange management can be a big beast and can get people all bent out of shape knowing they will have to follow some sort of formalized process. Having the business behind a push for better change management will enable you to wipe the slate clean and build something less complex and more targeted to the business. Getting buy in from the entire business is important. Either because of a failed attempt to get change management implemented or just a complicated system that has always existed.Īnd as we know many systems are just maintained because “That’s the way it’s always been done”. Many people fail before they even start because they are buried in a mess created before they arrived. Here are three of the main challenges that I see when discussing Change Management with clients: Stuck with someone else’s mess There are some common challenges that people have when looking at Change Management for the first time, or looking at improving their Change Management processes.
Some of the key words that we should all keep a focus on are “Promptly” evaluating, “Minimizing” disruption to end users and also “Minimizing Rework” that is required when a change fails. ITIL also tells us that “ Change Management provides value by promptly evaluating and delivering the changes required by the business, and by minimizing the disruption and rework caused by failed changes.” ( ITIL v3 Foundation Handbook. Why should we restrict the amazing work we are doing to just IT? Now I would make one slight modification to this statement and replace IT Services with Business Services. “A change is defined by ITIL as the Addition, Modification or Removal of anything that could have an effect on IT services.” ( ITIL v3 Foundation Handbook. To kick off, I think it is important that we have a clear idea of what a change is and why change management is important. This post will be focusing on Change Management and where to start with it, what are best practices and how do we make it easier on ourselves. This post will be talking about the IT Service Management life-cycle and most importantly delivering services to our end users, or customers, that are successful and have little to no negative impact on business continuity during its deployment and also reduce business risk wherever possible. In the last week I’ve been doing a couple of presentations on Change Management and where to start for businesses.
0 kommentar(er)
