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!

Comments

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group .   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

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 th