Virima V6.0 will soon be available with an all-new look, enhanced discovery, mapping and vulnerability features and more. Stay tuned!

A Guide to ITIL Incident and Problem Management

Two IT staff attending to an IT Problem using IT Problem Management tools

There are tasks being done that pertain to problem management at every type and size of business. But it turns out many if not most of those tasks fall short of the accepted definition of true, proactive problem management.

IT Problem Management: What It Is and Is Not

The IT Process Wiki says, “Problem Management aims to manage the lifecycle of all problems. The primary objectives of this ITIL process are to prevent incidents from happening, and to minimize the impact of incidents that cannot be prevented. Proactive problem management’ analyzes incident records, and uses data collected by other IT service management processes to identify trends or significant problems.”

(See, “Our take on making modifications to the ITIL® v4”)

Unfortunately, at too many organizations, there’s insufficient clarity about the things that distinguish problems from incidents. This confusion has been a challenge to IT managers and support providers since before there was an ITIL. According to the folks at leading IT training provider Global Knowledge, the distinction remains challenging today. Here’s how they attempt to sort it out.

Incident

According to ITIL 4, the latest version of the ITIL best practices guidelines, an incident “is an unplanned interruption to a service, or reduction in the quality of a service. In layman’s terms, an incident is the representation of an outage.

Problem

A problem, as defined in ITIL 4, “is a cause, or potential cause, of one or more incidents. In layman’s terms, a problem is the representation of the cause or potential cause of one or more outages.”

In other words, incident management is to problem management what firefighting is to fireproofing. Closing an incident is no more problem management than putting out a fire is fireproofing a building. 

The goal of management, especially proactive problem management, is not just to resolve an incident. It is instead to identify and resolve each incident’s root cause, and to learn from the experience to reduce occurrence and recurrence of incidents and problems.

Proactive Problem Management: An Elusive Goal

Clearly, every IT estate can benefit from truly proactive management of problems. However, achieving that goal can be daunting, if not impossible for some IT teams. For any of a multitude of reasons, you and your team may just be too busy putting out fires to devote efforts and resources to fireproofing your environment. 

Common obstacles can include a shortage or lack of skilled, experienced people, broken processes, inadequate or improperly implemented technologies, or combinations or any or all of these.

Ironically, the more difficult proactive management of problems is to achieve and maintain, the more needed it is likely to be. If your team is consumed by reactively dealing with incidents and problems, proactive problem management may seem unattainable. 

Fortunately, there are specific things you and your team can do to move closer to that important goal, starting as soon as today.

Virima participated in a webinar titled “The problems with your IT problem management – and how to solve them” where this topic was discussed in more detail. Follow the link to the webinar and learn how to ensure your IT people, processes, and technologies are adequately prepared to deliver proactive problem management.

Virima: Your Partner for Comprehensive IT Management

Virima can help to improve IT incident and problem management, as well as IT Asset Management (ITAM), IT Service Management (ITSM), and IT Operations Management (ITOM), across your organization’s entire IT estate. 

Virima solutions can automatically discover and map your critical IT resources and the interconnections that link them to one another, your applications and services, and your users. They also produce useful, actionable reports about your IT environment, reports that can help you identify and resolve incidents before they become disruptive problems. 

Virima is here to help. To get started, contact us today to schedule a demo and explore the possibilities!

Subscribe to Our Newsletter

More to Explore

Table of contentsWhat is CMDB, and why is it important for your cloud initiatives?CMDBs and change managementCMDBs and incident managementCMDBs and problem managementCompliance reporting made easy with CMDBsImpact analysis with CMDBs and cloud assetsMake better, fact-based decisions with Virima for…

Table of contentsHow does asset discovery work?What types of IT assets can you discover?NetworksServersPCs, laptops, and mobile devicesBenefits of IT asset discoveryLess time spent on cataloging IT assetsBetter and detailed IT reportsStreamlined IT asset acquisitionEnsuring compliance with security policies A single…

Table of contentsWhy stakeholder communications are importantHow to prepare for incident communicationIncident management best practicesCommunication plan High-quality major incident management communication plan Using visualizations in stakeholder communicationsIncident mitigation with visualizations Virima can help you with incident management Incidents are a part of business,…

Table of contentsAsset managementTracking and labeling assets’ locations and states through an asset register Tracking and managing software licenses Managing end-user devicesKeeping tabs and handling decommissioned assetsConfiguration managementIdentifying configuration items in the CMS Controlling  and managing all changes made to assets Understanding impact on…

Some people think that an IT service desk is the same thing as an IT help desk. It isn’t and we’re  going to explain the difference between service desk and help desk. Sure, there are some similarities, but there are…

Table of contentsA CMDB tool can maintain all other tools What is CMDB in ServiceNow?What are ServiceNow CMDB best practices?A few ServiceNow CMDB best practices include:Defining your goalsForming a configuration management teamEstablishing a governance structureUnderstanding configuration item designIntegrating with key business…

Table of contentsStep 1. Determine business objectivesStep 2. CMDB discovery toolsStep 3. ITSM system integrationStep 4. Equip data owners/data stewards with the right toolsStep 5. Data management and retention planStep 6. CMDB: data visualizationLearn more about these steps by watching…

Incident management is crucial while dealing with major incidents. They are the crises that have widespread impacts on your employees, disrupt your operations, and impact your ability to deliver on customer expectations.  While you may assume your company is prepared…

Table of contentsUnderstanding business service mappingA modern approach to business service dependency mappingDiscovery planning processUse casesVirima simplifies service mapping and IT discovery Business service mapping is the area of configuration management that perplexes so many IT professionals. Yet, it provides…

Understanding the Configuration Management Database (CMDB) and its core functions is a critical aspect of service management. The CMDB forms the hub of numerous service management practices and provides a means of correlation needed to deliver business services successfully.   The…

IT asset management (ITAM) and inventory management are both useful practices that can benefit any organization using IT. Inventory management can exist without IT asset management, and in fact, it does in many organizations as it has been in existence…