Basics of the A3 Problem Solving Method
Overview
In this article, let us continue our journey with the A3 Problem Solving Method and see what it takes to define the problem.
Exploring the A3 Problem Solving Method
As discussed in the previous segment of this article series, the A3 Problem Solving Method (referred to as A3 henceforth) originated at Toyota to facilitate the identification of underlying issues and the creation of effective implementation strategies. In essence, the approach follows these key steps:
- Defining the problem
- Identifying potential causes and isolating the root cause
- Generating potential solutions for the root cause and selecting the optimal one
- Devising an actionable plan to implement the chosen solution
To begin the A3 process, you'll need fundamental information to define the problem.
Importance of Capturing Essential Problem Information
In Problem Management, you will deal with lots of disparate data which requires meta data to catelog the information. Metadata refers to data that provides insights into other data. While it's possible to address problems without metadata, its presence streamlines the process of locating issues, assigning them to the correct department and personnel, and categorizing them. This classification enables the evaluation of a cluster of problems, potentially leading to insights in other areas of the organization. In essence, metadata facilitates the creation of metrics-based reports that enhance the utilization of the A3 method and the identification of problems.
Metrics for Enhanced Performance
Metrics rely on structured data. Information stored in unstructured fields, such as free-form text, necessitates analysis for accurate problem classification. Notably, as seen in the capabilities of "Artificial Intelligence", there's potential analyze free-form text for uncovering further avenues of improvement. However, for now, our focus remains on understanding requirements and acquisition strategies.
Before we get ahead of ourselves, lets understand incidents, and problems.
Fundamentals
A problem is the underlying cause of one or more incidents that prompt an in-depth exploration of a process. The problem evaluation starts where an incident ends. Annually, an organization encounters thousands of incidents, and fewer of problems. However, problems give unique opportunities when we can identify and resovlve them to reduce errors in business-critical systems, as opposed to incidents which are too isolated to show a large-scale impact. For example, each incident of a password reset when a user calls the help desk, is an opportunity to improve the customer touch-point and remove friction (the Problem). One password reset call may not give enough information to indicate a larger scale training issue; whereas, a collection of icidents can be categorized using meta-data to indicate multiple areas of improvement.
As each problem is created in the tracking system, initial information to capture includes the affected item (referred to as a Configuration Item or CI in ITSM terminology). This item could be an IT-provided service, a supported application, or an element of the IT infrastructure. Identifying the affected item assists in gauging its impact on the enterprise. For instance, an application utilized by business partners could directly influence their productivity and revenue generation. Conversely, an infrastructure component supporting multiple business units might impede their optimal performance, leading to avoidable administrative expenses. Additional details to capture at this point in the process, include "Opened By" and "State" which can be filled out before proceeding to describe the problem.
Defining the Problem
State the problem summary and description. A concise summary coupled with a detailed description minimizes confusion and keeps the team focused on addressing the actual problem. A word of caution: refrain from prematurely speculating about the problem's cause. Don't even give a hint where the cause might be. At this point, no one can truely know. Given the early stage of problem analysis, insufficient information is available for such determinations. Remember, adhering to this process is vital for its efficacy.
With the start of problem analysis, we can gather and document advanced information.
Progressing Further
Supposing there are multiple problems to fix, the enterpise is limited in how problems can be solved on at a given time due to resource constraints. So, problems should be prioritized. To prioritize the prblem, we need to understand real business impacts, and the appropriateness to fix the problem.
Business Implications of the Problem
Having gained preliminary insights into the problem, it's time to assess its implications for the company. Fully comprehending these implications requires understanding the position of the CI within the business's value chain. CIs can influence either the revenue or expense side of the profit curve. This task, while sounding simple, involves intricate calculations. Certain CIs might wield a more significant impact on the business, while others, although essential, may be distanced from end outcomes, making problem tracing complex. To systematically characterize each problem's impact, we assign an impact value on a scale of 1 to 10, where 1 signifies minimal impact and 10 signifies substantial impact. When making this assessment, factors such as user count, departments, locations, application or service importance, and the company's reliance on the service come into play. If the problem affects expenses, the expense size and the number of impacted individuals should be considered. The impact value, however, doesn't stand alone; it needs to be juxtaposed with the cost of fix.
Assessing Problem Fix Feasibility
The feasibility score quantifies the cost associated with resolving the problem. Similar to impact, feasibility is rated on a scale from 1 to 10, with lower scores indicating a challenging and costly fix, while higher scores signify an easier and less resource-intensive solution. In calculating feasibility, remember to factor in the time required for fixing the problem weighed against the associated risks of fixing it. Will other critical services need to be temporarily shut down? This doesn't imply avoiding a fix but underscores the importance of comprehending the complete cost of resolution. What about the opportunity cost of not fixing the problem? Armed with the impact and feasibility data, we can prioritize the problem resolution.
Problem Resolution Priority
By combining impact and feasibility scores, a relative priority, termed the Prioritization Score, emerges for each problem. It's crucial to note that the organization's resources are finite; thus, decisions must be made regarding business pursuits, equipment acquisitions, and problem-solving endeavors. This Prioritization Score guides a Problem Advisory Board in determining the problem's priority. The advisory board evaluates problems against each other, considering deployable resources in the resolution process – an enterprise problem requires enterprise resources which are often busy with other projects. Once a priority is assigned, we can segue into the problem-solving forensics in the next segment of this article.
Conclusion
In defining problems, we must understand and measure the business impact and the corporate will to fix it. The prioritization score gives governing bodies the leverage to define what is more important to fix in light of other problems and opportunities so that we are focused on the right issue at the right time. Anticipate the upcoming article where we plunge deeper into the A3 methodology, conducting forensic analysis and addressing problems at their core.