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 non-physical 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 US 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? rbrenlUyCnQsQnoVFmgNYner@ChacAdQqEraYoebNUqYHoCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

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.

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:

Something from Abraham, from Mark and from HennyAbraham, Mark, and Henny
Our plans, products, and processes are often awkward, bulky, and complex. They lack a certain spiritual quality that some might call elegance. Yet we all recognize elegance when we see it. Why do we make things so complicated?
A cup of coffeeHow to Procrastinate
You probably know many techniques for procrastinating, and use them regularly, but vociferously deny doing so. That's what makes this such a delicate subject that I've been delaying writing this article. Well, those days are over.
A dwarf apple tree typical of modern commercial varietiesWacky Words of Wisdom
Words of wisdom are so often helpful that many of them have solidified into easily remembered capsules. We do tend to over-generalize them, though, and when we do, trouble follows. Here are a few of the more dangerous ones.
U.S. Air Force Staff Sgt. Christa Quam holds her puppyBe With the Real
When the stream of unimportant events and concerns reaches a high enough tempo, we can become so transfixed that we lose awareness of the real and the important. Here are some suggestions for being with the Real.
World global temperature departuresConfirmation Bias: Workplace Consequences Part I
We continue our exploration of confirmation bias, paying special attention to the consequences it causes in the workplace. In this part, we explore its effects on our thinking.

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

Forthcoming issues of Point Lookout

kudzu enveloping a Mississippi landscapeComing April 5: Listening to Ramblers
Ramblers are people who can't get to the point. They ramble, they get lost in detail, and listeners can't follow their logic, if there is any. How can you deal with ramblers while maintaining civility and decorum? Available here and by RSS on April 5.
Ruth Bader Ginsburg in 2016And on April 12: How to Listen to Someone Who's Dead Wrong
Sometimes we must listen attentively to someone with whom we strongly disagree. The urge to interrupt can be overpowering. How can we maintain enough self-control to really listen? Available here and by RSS on April 12.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenMYJQqvmhbrRqQVjzner@ChacfzwyisuqtrvLXeqeoCanyon.com or (617) 491-6289, 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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

Changing How We Change: The Essence of Agility
MasteChanging How We Change: The Essence of Agilityry of the ability to adapt to unpredictable and changing circumstances is one way of understanding the success of Agile methodologies for product development. Applying the principles of Change Mastery, we can provide the analogous benefits in a larger arena. By exploring strategies and tactics for enhancing both the resilience and adaptability of projects and portfolios, we show why agile methodologies are so powerful, and how to extend them beyond product development to efforts of all kinds. Read more about this program. Here's an upcoming date for this program:

Creating High Performance Virtual Teams
Many Creating High Performance Virtual Teamspeople experience virtual teams as awkward, slow, and sometimes frustrating. Even when most team members hail from the same nation or culture, and even when they all speak the same language, geographic dispersion or the presence of employees from multiple enterprises is often enough to exclude all possibility of high performance. The problem is that we lead, manage, and support virtual teams in ways that are too much like the way we lead, manage, and support co-located teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance. Read more about this program. Here's an upcoming date for this program:

The Race to the South Pole: Ten Lessons for Project Managers
On 14The Race to the Pole: Ten Lessons for Project Managers December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough, but to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ 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.
21st Century Business TravelAre your business trips long chains of stressful misadventures? Have you ever wondered if there's a better way to get from here to there relaxed and refreshed? First class travel is one alternative, but you can do almost as well (without the high costs) if you know the tricks of the masters of 21st-century e-enabled business travel…
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.