“The purpose of the Problem Management practice is to reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents and by managing workarounds and known errors. (ITIL® 4) ” One of the ways that Problem Management reduces the likelihood and impact of incidents is by making changes via the Change Enablement practice. Given the benefits, it’s a wonder more organizations don’t have highly capable and well-integrated Problem Management, Incident Management, and Change Enablement practices in their organizations. One reason could be misconceptions about the Problem Management practice, which we explore in our blog Misunderstood and Misused - A Rant About Problem Management . Another reason could be the inability to support these practices with an integrated toolset that includes a solid Configuration Management System (CMS), as configuration information supports the activities of all these practices. Of course, before we talk about tools,...
I was having a discussion with a learner this morning about the difference between Service Requests and Standard Changes. This learner's organization publishes a list of standard services that users can request via a self-help tool. The Service Request is routed to the Service Desk. The Service Desk reviews the request. If appropriate, the Service Request may be fulfilled by applying a Standard Change that has been pre-authorized by the Change Enablement practice. By definition, a Standard Change is a low-risk, pre-authorized change that is well understood and fully documented, and which can be implemented without needing additional authorization. Standard Changes must be recorded, possibly as a Service Request. However, each individual change does not require operational oversight by a change authority. ‘Pre-authorized’ means that the procedure for making the standard change has undergone a full risk assessment and authorization. These risk assessment and authorization steps w...