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.
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 worksWhen 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. Top Next Issue
Are 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? rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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.
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:
- The Zebra Effect
- If you're feeling overwhelmed by all the items on your To-Do list, and if you start on one only to realize
that you have to tackle three more you didn't know about before you can finish that one, you could be
experiencing the Zebra Effect.
- Should I Keep Bailing or Start Plugging the Leaks?
- When we're flooded with problems, and the rowboat is taking on water, we tend to bail with buckets,
rather than take time out to plug the leaks. Here are some tips for dealing with floods of problems.
- Achieving Goals: Inspiring Passion and Action
- Achieving your goals requires both passion and action. Knowing when to emphasize passion and when to
emphasize action are the keys to managing yourself, or others, toward achievement.
- The Paradox of Confidence
- Most of us interpret a confident manner as evidence of competence, and a hesitant manner as evidence
of lesser ability. Recent research suggests that confidence and competence are inversely correlated.
If so, our assessments of credibility and competence are thrown into question.
- Goodhart's Law and Reification
- Goodhart's Law, applied to organizations, is an observation about managing by metrics. When we make
known the goals for our metrics, we risk having the metrics lose their ability to measure. The risk
is elevated when we try to "measure" abstractions.
See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
- Coming December 11: White Water Rafting as a Metaphor for Group Development
- Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups. Available here and by RSS on December 11.
- And on December 18: Subgrouping and Conway's Law
- When task-oriented work groups address complex tasks, they might form subgroups to address subtasks. The structure of the subgroups and the order in which they form depend on the structure of the group's task and the sequencing of the subtasks. Available here and by RSS on December 18.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
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
Recommend this issue to a friend
Send an email message to a friend
rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed