| October 3, 2007 | Volume 7, Issue 40 |
| Recommend this issue to a friend Join the Friends of Point Lookout HTML to link to this article… |
Archive: By Topic
By Date
Links to Related Articles Sign Up for A Tip A Day! |
| Create a perpetual bookmark to the current issue
| |
by Rick Brenner
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?
oot 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.

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!
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.
See also Personal, Team and Organizational Effectiveness and Critical Thinking for more related articles.
Available in early 2009: 2007-2008.
Ever wonder if there isn't a better way to travel? Travel is essential, but the hassles of travel aren't. Read 202 Tips for Business Travel to learn how to convert business travel from a time-wasting hassle to a breeze. Revised and updated for 2008 with 101 new tips! Check it out!
Projects never go quite as planned. We expect that, but we don't expect disaster. How can we get better at spotting disaster when there's still time to prevent it? How to Spot a Troubled Project Before the Trouble Starts is filled with tips for executives, senior managers, managers of project managers, and sponsors of projects in project-oriented organizations. Check it out!
add value to your Web sites quickly and easily. Pick up the HTML to link to this article in a choice of formats.
Are you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt? Read 101 Tips for Managing Change to learn how to plan and execute your change efforts to inspire real, passionate support. Check it out!
A Tip a Day arrives by email each business day. It's 20 to 30 words at most, and gives you a new perspective on the hassles and rewards of work life. Most tips also contain links to related articles. Free!