Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 7, Issue 40;   October 3, 2007: Some Limits of Root Cause Analysis

Some Limits of Root Cause Analysis

by

Root Cause Analysis uses powerful tools for finding the sources of process problems. The approach has been so successful that it has become a way of thinking about organizational patterns. Yet, resolving organizational problems this way sometimes works — and sometimes fails. Why?

Root Cause Analysis (RCA) was developed to resolve defects in manufacturing. When the error rate of a production process is too high, we use RCA to discover why and fix it. In manufacturing, RCA works pretty well. Sometimes it even works with software development and other processes that generate nonphysical outputs. But when we try to apply RCA to problems among people, trouble appears.

A frost-covered spider web

A frost-covered spider web. Webs are particularly resistant to single-point failures. That's one reason why the Internet performs as well as it does, and why changing just a few elements of a "causality web" is unlikely to have a material effect on the performance of an underperforming organizational process. Indeed, looking at this Web, it's difficult to discern how the spider might have constructed it. Ask yourself, "In what order would I have put in place the various strands of this web?" It's unlikely that the spider used any "jigs" — temporary structures that were later removed. But in organizational webs, existing structures are often the result of structures that are no longer in place. That phenomenon adds to the complexity of any Root Cause Analysis, because the actual root causes of contemporary problems may have disappeared or been buried by a sequence of acquisitions, mergers, RIFs, reorganizations and other organizational changes. Photo "Frosty Spider Web" by John Brandon, for the "Yellowstone Digital Slide File", 1970. Courtesy U.S. National Park Service.

We're usually unaware of RCA thinking. Some indicators are questions and statements like these:

  • Who started this trouble?
  • She's the common factor in all these problems.
  • I did Y, but only because she did X.
  • If we send Jeff to communication training, everything will get better.

Sometimes, RCA thinking does lead to noticeable improvement, but too often, it ends in exasperation or exacerbation.

We can understand why if we remember that RCA makes two critical assumptions. First, it assumes that we'll find causes that have no internal structure. Second, it assumes that these "atomic" causes are independent, adjustable forces. The very term "root cause" captures these two ideas.

In human systems, both assumptions can be invalid, and often are. For instance, consider the assumption of atomic causes. A simple example: our project is late because we keep changing things; so we add resources to speed it up; but adding resources is a change; that change further delays the project.

Because these so-called "causality loops" violate the assumption that we can always find atomic causes, people have extended the method to deal with this situation. But in organizational applications, the term causality loop doesn't quite capture the complexity of the difficulty — causality web is more accurate.

In seeking organizational
improvement, changing just
a few things rarely works
When we encounter causality webs, process repair can entail broad organizational change — a process so daunting that we convince ourselves that changing "just a few things" will do the trick. Often, when we do make changes, the web does break temporarily — until the elements we chose not to address can restore its structure.

Assuming independent, adjustable forces also fails from time to time. For instance, in a business unit troubled by toxic, destructive conflict, an objective application of RCA might find causes such as manipulative management, oppressive schedules, or human resource policies that lead to high turnover. Since such environments rarely allow even discussion of these factors, adjusting them is often precluded.

In many cases, even though these causes are independently adjustable, the structure of organizational power can prevent their adjustment. Unable to deal with what everyone can see and nobody can acknowledge, the organization sometimes falls into "analysis paralysis."

It's useful to remember that we seek not the cause of organizational failures, but their elimination. Confusing the two objectives is a cause — if not a root cause — of the misapplication of root cause analysis. Go to top Top  Next issue: Completism  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!

Your comments are welcome

Would you like to see your comments posted here? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Personal, Team, and Organizational Effectiveness:

Detour SignHow We Avoid Making Decisions
When an important item remains on our To-Do list for a long time, it's possible that we've found ways to avoid facing it. Some of the ways we do this are so clever that we may be unaware of them. Here's a collection of techniques we use to avoid engaging difficult problems.
The piping plover, a threatened species of shore birdUsing the Parking Lot
In meetings, keeping a list we call the "parking lot" is a fairly standard practice. As the discussion unfolds, we "park" there any items that arise that aren't on the agenda, but which we believe could be important someday soon. Here are some tips for making your parking lot process more effective.
A black kite, a species of hawkEmbolalia and Stuff Like That: II
Continuing our exploration of embolalia — filler syllables, filler words, and filler phrases — let us examine the more complex forms. Some of them are so complex that they appear to be actual content, even when what they contain is little more than "um."
Ammi Visnaga, a nile weed that has medicinal valueDown in the Weeds: II
To be "down in the weeds," in one of its senses, is to be lost in discussion at a level of detail inappropriate to the current situation. Here's Part II of our exploration of methods for dealing with this frustrating pattern so common in group discussions.
An example of a Weaver's PathwayStill More Things I've Learned Along the Way
When I have an important insight, or when I'm taught a lesson, I write it down. Here's another batch from my personal collection.

See also Personal, Team, and Organizational Effectiveness and Critical Thinking at Work for more related articles.

Forthcoming issues of Point Lookout

Typing a text message on a smartphoneComing May 15: Should I Write or Should I Call?
After we recognize the need to contact a colleague or colleagues to work out a way to move forward, we next must decide how to make contact. Phone? Videoconference? Text message? There are some simple criteria that can help with such decisions. Available here and by RSS on May 15.
Satrun during equinox — a composite of natural-color images from CassiniAnd on May 22: Rescheduling Collaborative Work
Rescheduling is what we do when the schedule we have now is so desperately unachievable that we must let go of it because when we look at it we can no longer decide whether to laugh or cry. The fear is that the new schedule might come to the same end. Available here and by RSS on May 22.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

Reprinting this article

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at X, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.