Problem? … What a Big Word
In every single minute of our life we encounter problem/s. But as noted by elders, every problem has its own solution, but you just have to figure it out. Some problems can be solve quickly and others even took a lifetime, if your problem is your face. Kidding aside, in the business world, how and when the problems should be answered and solved should measurable and solution should be definite. And if we ask why, it’s because we are dealing with highly demanding customers, and just a minute if we will not be able to respond them it might be the end of our company.
To address the aggressive demand of our customers (i.e. internal and external), every organization must be able to identify, manage and resolve problems especially those that would affect service quality and efficiency. It even requires an organization to research the problem and be able to have a definite solution. As defined during one of our discussion with Prof. Dela Rosa, problem describes an undesirable, indicating the unknown root cause of one of more existing or potential incidents. Thus, to be able to untangle the unknown at the same time preventing it to happen again, it requires the organization to have a structured and comprehensive process to ensure that problems are properly identified and symptoms are scrutinized deeper to be able to address not only the issue but the root cause of the problem.
The main difference of problem management from incident management is the former deals more on the detection of the underlying causes of an incident and their subsequent resolution and prevention. Unlike, incident management where the aim is to restore the service to the customer as quickly as possible, often through what we call temporary fixes or work-around, rather than through the determination of a permanent solution. In this respect, therefore the speed with which a resolution is found is only of secondary importance.
The challenge of problem management is it usually involves a thorough investigation which requires ample time and oftentimes results to the delay of the restoration of service, causing downtime and complaints. However, the good side of it is its long-term benefit which is to prevent the problem from recurring again.
To be able to reap the benefits of having problem management, every organization should have the following at the minimum:
1) There should be a single problem management process, which is separate and distinct from the incident management process. All problems and their resolutions will be logged in a common problem management system which will be made available to Service Desk/Help Desk as commonly term and Incident Management staff.
2) There should be clear linkages between Incident records, Problem records, Known Errors and Requests for Change leveraging existing data systems wherever feasible and practical. Additional interfaces will build upon and interface with existing data sources.
3) There should be a definitive and maintained record of the "Known and trusted state" of the infrastructure
4) The Problem Management process facilitates Root Cause Analysis on incidents (and incident trends or service failures referred to Problem Management by Service Managers, key technical resources and Client representatives). Analysis on the data collected in the Incident Management System database as well as other sources will undergo periodic trend analyses by Problem Management in close consultation with Incident Management staff.
5) The Problem Management function is responsible for acting as the service provider for the Knowledge/Known error database and for providing information concerning problems and proposed solutions. Problem Management owns the quality of the knowledge database, and its usability (though they may not responsible for the integrity of the content).
6) Incidents referred to Problem Management for Root Cause Analysis will have outcomes documented.
7) The Problem Manager will determine appropriate Metrics to be collected to measure the effectiveness and efficiency of the Problem Management process. Performance expectations will be described in Service Catalogue and/or Service Level Agreements.