Skip to main content

Incident vs Problem

In a recent conversation I was asked about the difference between an Incident and a Problem.

This is one of the most often confused points in all of IT Service Management and ITIL. Part of the confusion comes from the fact that both words are used (at least in the English language) to express similar ideas. Each reference some kind of issue occurring that potentially could lead to human action. However, in ITIL words are more clearly defined and have particular contexts for usage.

Incident: Any unplanned event that causes, or may cause, a disruption or interruption to service delivery or quality

Problem: The cause of one or more incidents, events, alerts or situations

While Incidents have to do with disruption of delivery or quality, problems have to do with causes. From these distinct definitions we can see that not every incident would result in a problem, and not every problem even needs to be related to an incident. Keep in mind that “Incidents never grow up to be Problems.” The difficulty arises when we  want a nice quantitative way of determining when to begin the Problem Management process. We look for some formula, algorithm, quantity or structure that acts as a clear objective indicator to begin the Problem Management process. Unfortunately this may not be the right approach to take.

What figures into when we should use a problem has to do with our desire to find the root cause of an occurrence. The trigger for starting the problem process, or even for determining if you have a problem, is the basic question of “Why?” Anytime anyone asks the question “why?” you have moved into the Problem Management process. The question could be generated from one incident, one event, a series or trend of incidents or events, a major incident, or even no incidents or events. The last situation results in proactive Problem Management. A desire to investigate our current delivery and quality capabilities may lead someone to ask “why?” and begin the process of determining root cause and a permanent fix.

Problem Management is much more subjective and qualitative in its nature than Incident Management, which is more objective and quantifiable. This is what leads to the confusion between the two. They should be seen as two sides of the same coin or two ends of a spectrum. They are complements to each other and should be done in parallel based on the need to understand situations from both an objective (Incident) and subjective (Problem) perspective.

Comments

Andy said…
A good explanation...
Ashok NR said…
Very nice, and crisply explained. Thanks a lot.
Ashok NR said…
Very nice and crisply explained. Thanks a lot.

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

ITIL 4 – Mapping the Customer Journey

All service providers are in the business of customer and user experience. It is not enough to compete on products and services, how services are delivered is as important as what is delivered.

The customer journey is the complete end-to-end experience customers have with one or more service providers and/or their products through the touchpoints and service interactions with those providers. In order to focus on the outcomes and on the customer/user experience, service providers are seeking to master the art of mapping their customer journey. Doing so allows them to maximize stakeholder value through co-creation of value throughout the entire value chain.

The customer journey begins by understanding the overall macro-level of steps or groups of activities that generate the need for interaction between the customer and the service provider. These activities begin at “Explore” and end with “Realize” where the value is actually being consumed by the end-users.
The Band of Visibility