KB of Everything
  • Knowledge Base of Theory
  • Azure Services
    • Quick Overview
  • 70-533: IMPLEMENTING AZURE INFRASTRUCTURE SOLUTIONS
    • Azure Virtual Machines - Introduction
    • Azure Virtual Machines - Availability
    • Azure Virtual Machine - Storage
    • Azure Virtual Machine - Operations
    • Azure Automating Virtual Machine Configuration
  • DevOps
    • Cloud
    • SDLC
    • DevOps
    • CI\CD
    • Microsoft SQL Availability
  • Powershell
    • Powershel interview questions
    • Understanding a Windows PowerShell Module
    • Functions
    • Understanding and using objects in PowerShell
    • PowerShell Basics: Custom Objects
    • Parallel processing with PowerShell
  • Monitoring
    • Short Guide
  • ITIL
    • ITIL CORE
    • Service Operation
    • Service Operation: Event Management
    • Service Operation: Incident Management
    • Service Operation: Problem Management
    • Service Operation: Request Fulfillment
    • Service Operation: Access Management
    • Change Management
    • Release/deployment management
  • Methodologies
    • Agile Methodology
    • Scrum Methodology
    • Waterfall Methodology
    • Kanban
    • Agile vs Scrum
    • Kanban vs Scrum
    • Agile vs Waterfall
    • Kanban vs Agile
  • EPAM
  • Testing
    • Fake Stube Mocking
    • Types of Software Testing: Different Testing Types with Details
Powered by GitBook
On this page
  • What is ITIL Problem Management?
  • The Value of Problem Management to the Business
  • Problem Management Process Flow
  • Problem Management Key Performance Indicators (KPIs)

Was this helpful?

  1. ITIL

Service Operation: Problem Management

PreviousService Operation: Incident ManagementNextService Operation: Request Fulfillment

Last updated 6 years ago

Was this helpful?

What is ITIL Problem Management?

Problem management is the process responsible for managing the lifecycle of all problems that happen or could happen in an IT service. The primary objectives of problem management are to prevent problems and resulting incidents from happening, to eliminate recurring incidents, and to minimize the impact of incidents that cannot be prevented. The defines a problem as the cause of one or more .

The IT Infrastructure Library (ITIL) provides the following definitions for usage within this process:

  • Problem: “The cause of one or more Incidents. The cause is not usually known at the time a Problem record is created"

  • Error: “A design flaw or malfunction that causes a failure of one or more IT services or other configuration items”

  • Known Error: “A Problem that has a documented root cause and workaround”

  • Root Cause: “The underlying or original cause of an incident or problem”.

Proactive vs. Reactive Problem Management

Problem Management can be either reactive or proactive.

  • Reactive Problem Management is the Problem solving reaction that occurs when one or more Incidents arise.

  • Proactive Problem Management deals with identifying and solving Problems before any Incidents have occurred. This activity is associated with Continual Service Improvement (CSI).

That's a tough question but thankfully, our team is on it. Please bear with us while we're investigating.

The Value of Problem Management to the Business

The Problem Management process works in conjunction with Incident and Change Management to provide value to the business in a variety of ways. The primary goal of Problem Management is to minimize the impact of Problems on the business and prevent recurrence. When successful, downtime and disruptions are reduced. Additional benefits include:

  • Increased service availability

  • Improved service quality

  • Decreased Problem resolution time

  • Reduction of the number of Incidents

  • Increased productivity

  • Reduced costs

  • Improved customer satisfaction

Problem Management Process Flow

  • Problem Detection

  • Problem Logging

  • Investigation and Diagnosis

  • Workaround

  • Create Known Error Record

  • Resolution

  • Closure

Problem Management Key Performance Indicators (KPIs)

  • Problems reported by (category, organizational unit, person, etc.)

  • Problems resolved within SLA targets

  • Percentage of Problems exceeding SLA targets

  • Trends associated with Problem backlog

  • Average cost of managing a Problem

  • Root Cause Analysis (RCA) report

Information Technology Infrastructure Library
incidents