Root Cause Analysis Techniques

Beyond Firefighting: The Goal of Root Cause Analysis

In many fast-paced operational or project management roles, the focus is often on "firefighting"—quickly implementing a fix to keep things moving. While necessary in the short term, this approach often leads to dealing with the same issues over and over again. Root cause analysis (RCA) is the more strategic approach. It takes extra time upfront to investigate the origins of a problem to ensure that the eventual solution is permanent.

To understand this distinction and the different levels of solutions, let's watch a short video.

As you can see, a Business Analyst's objective isn't just to find any solution. It's to find a solution that leads to a permanent or preventive action. This is how you create lasting business value.

Technique 1: The 5 Whys

The 5 Whys is a simple yet powerful technique for drilling down into a single chain of cause and effect. It's a straightforward, linear method that helps you move past surface-level explanations to find a process or system-level failure.

The 5 Whys in Action

The key is to keep asking "Why?" until you arrive at a fundamental cause that, if addressed, would prevent the entire chain of events from reoccurring. Let's watch a classic, memorable example.

Applying the 5 Whys to an AdTech Scenario

Let's ground this in your AdTech background.
Problem Statement: The monthly client advertising report was sent 48 hours late, violating our Service Level Agreement (SLA).

1. Why was the report late?
   • Because the data from the primary advertising platform was not available on time.
2. Why was the data not available?
   • Because the automated data export script failed to run overnight.
3. Why did the script fail?
   • The script's access token had expired, so it couldn't authenticate with the platform's API.
4. Why had the token expired?
   • The new security policy requires tokens to be refreshed every 30 days, but no one was assigned to do it for this script.
5. Why was no one assigned to do it?
   • The script was built by a developer who has since left the company, and its ownership was never formally transferred during the offboarding process.

Root Cause: A process failure. The company lacks a formal process for transferring ownership of automated tools and scripts during employee offboarding.

Notice the final "why" identifies a process issue, not a person to blame. The solution isn't to scold someone; it's to fix the offboarding process.

Technique 2: The Fishbone (Ishikawa) Diagram

While the 5 Whys technique is great for single-cause problems, many business issues are more complex, with multiple contributing factors. The Fishbone Diagram (also called a Cause-and-Effect or Ishikawa Diagram) is a visual brainstorming tool used to explore and categorize a wide range of potential causes.

To get a comprehensive understanding of how to build and use one, we'll turn to a detailed video guide.

Tailoring Categories for Your Domain

As the video mentioned, the categories (the "bones" of the fish) are flexible. While "Man, Machine, Method" are common in manufacturing, you can adapt them to your context. For your work in AdTech and marketing, a highly effective set of categories comes from an article on RCA in performance marketing.

Using these four levers makes the analysis immediately relevant. If the problem is "Customer Acquisition Cost (CPA) increased by 30%," you can structure your team's brainstorming like this:

• Audience: Did our targeting change? Did a competitor start targeting our audience more aggressively?
• Creative: Are our ads suffering from creative fatigue? Did we launch new ads that are underperforming?
• Bids: Did platform auction prices increase? Did we change our bidding strategy?
• Budget: Did we shift the budget away from high-performing campaigns?

Choosing Your Tool: 5 Whys vs. Fishbone

So, when do you use each tool? It's about matching the tool to the complexity of the problem.

Often, the most effective approach is to use them together. This is a common practice for professional BAs.

1. Start with the Fishbone Diagram: Use it in a workshop with stakeholders to brainstorm all possible causes for a complex problem. This gives you a comprehensive map of the problem space.
2. Prioritize and Drill Down with 5 Whys: Once the diagram is complete, have the team vote on the 1-3 most likely causes. Then, use the 5 Whys technique on each of those high-priority causes to find their respective root causes.

This hybrid method combines the breadth of the Fishbone with the depth of the 5 Whys, giving you a structured and thorough analysis.

Conclusion

You now have two essential techniques for moving beyond symptoms to discover the true source of business problems. Mastering root cause analysis will make your solutions more effective and is a key differentiator for a high-performing Business Analyst.

Key Takeaways:

• Think Like a Detective: Your goal is to find the underlying cause, not just patch the immediate symptom. Aim for permanent and preventive solutions.
• Use 5 Whys for Depth: When you suspect a single cause or need to drill down into a specific issue, the 5 Whys provides a simple, linear path to the root.
• Use Fishbone for Breadth: For complex problems with many potential factors, the Fishbone Diagram is an excellent collaborative tool for brainstorming and categorizing possibilities.
• Combine for Power: Use the Fishbone diagram to explore the landscape of potential issues, then use 5 Whys to dig deep into the most likely culprits.

Preview of the Next Lesson:
We've now defined our problem and diagnosed its root causes. This gives us a very clear picture of the current state. The next logical step is to define where we want to be—the desired state. In the next lesson, we will learn how to conduct gap analysis to compare current and desired business states, bridging the gap between problem and solution.