Skip to main content

Reasoning for Problem Management

When it comes to Problem Management two things should come to mind: Root Cause Analysis (RCA) and finding a permanent resolution. How often have you thought about what it takes to conduct these aspects of Problem Management? An important underlying aspect of conducting a Root Cause Analysis and finding the permanent resolution are the reasoning approaches used.

Three types of basic reasoning approaches are:
  • Inductive: Reasoning from specific examples to general rules
  • Deductive: Reasoning from general rules to specific examples
  • Abductive: Reasoning to the most likely answer
Each has its own uses and can be applied to problem solving and Problem Management at different times and for different reasons. However, when performing the Problem Management process we should be open to using all three reasoning approaches. They all complement each other with Inductive and Deductive reasoning forming two ends of a spectrum while Abductive thought looks for the balance between the other two approaches.

Let's take a look at some ways we can use these reasoning methods to help us with Problem Management.

Using an Inductive approach we should begin by looking at specific Event or Incident data. Turn this data into information by sorting and categorizing it into meaningful groups. You can do this by looking for commonalities or trends among the data or facts. Once you have grouped the data into information, ask yourself: “What is this information trying to tell me?” By answering this question you will produce knowledge which will lead to identifying root cause or help to identify a proper permanent resolution.

Using the Deductive approach we would begin by establishing a general set of characteristics against which we will then compare data or facts to see if it matches. This allows us to begin with knowledge and decompose (deduce) it into information and then into data or facts. Then ask yourself the question “Do these facts, data and examples still fit the rule?” Once we have specific examples that fit our general rules or criteria we can then turn again to Induction for validation!

Using an Abductive approach would allow us to start with the data, information, knowledge and most important, wisdom, at hand. From our personal and professional experiences we can draw conclusions that would help us eliminate unlikely causes or ineffective fixes and thus save ourselves from going down dead ends of problem solving. Ask the question “Are the proposed root causes or fix recommendations likely, plausible or even possible?” We must be careful with abductive thought because we can often throw out what might in the end turn out to be an unlikely but actual root cause or identified fix.

When attempting to perform the Problem Management process we should see these reasoning methods as three parts of a triangle that should be used altogether and in an iterative fashion. Look at your problem from multiple sides and use different tools and approaches to understand the problem. This varied approach will allow for more effective and efficient efforts at Problem Management!


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 …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…