Consider the case in the callout. While reading it, think about what might be wrong with that way of measuring problem management.
Problem Management
Be proactive like a true pro
Some organizations consider proactive problem management to be the work of resolving problems when they are not currently causing any incidents. This understanding is in direct conflict with an alternative interpretation, wherein proactive problem management concerns the identification and resolution of problems before they have caused any incidents at all.
The Sinking of the Sewol and “Root Cause” Analysis
O why why why why why? Ohno Taiichi provides an oft-quoted example of using the five whys to perform root cause analysis. His neat little scenario of making durable improvements in the operation of an industrial machine gives a misleading view of the reality of understanding the causes of problems. An analysis of the sinking […]
Problem Workarounds and Incident Resolutions
The Scope of this Discussion When a problem is identified reactively, it means that one or more incidents have occurredand it has been decided to take note of and perhaps investigate their underlying causes. I exclude from this discussion both the proactively identified problems—the problems identified before any related incidents have occurred—and those organizations that […]
What is a problem?
Although troubleshooting and the definitive elimination of faults has a long history, the particular innovation of ITIL® 2 was to recommend treating problems and incidents as two separate entities, each with its own life-cycle. This advice had led to a series of confusions and ambiguities, many of which have still not been resolved among the […]
What is meant by severity?
Some practitioners appear to use the term severity interchangeably with other attributes of events and incidents, such as impact or priority. I propose here a simple way of distinguishing severity from impact, one that is loosely derived from ITIL®