Point Lookout An email newsletter from Chaco Canyon Consulting
Point Lookout, a free weekly email newsletter from Chaco Canyon Consulting
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 Bookmark and Share
Tweet this! | Follow @RickBrenner Random Article

Some Limits of Root Cause Analysis

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?

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 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
Bookmark and Share


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? Send 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:
Submitting a status reportStatus-Report as a Second Language
Sometimes, the clichés the losing team's players feed to sports reporters can have hidden meaning. So it is with Project Status Reports, especially for projects in trouble.

A hiker in the La Primavera calderaCommitment Makes It Easier
When you face obstacles, sometimes the path around or through them is difficult. Committing yourself to the path lets you focus all your energy on the path you've chosen.

Budget and ScheduleGames for Meetings: Part IV
We spend a lot of time and emotional energy in meetings, much of it engaged in any of dozens of ritualized games. Here's Part IV of a little catalog of some of our favorites, and what we could do about them.

A pyramidEmail Antics: Part II
Nearly everyone complains that email is a time waster. Yet much of the problem results from our own actions. Here's Part II of a little catalog of things we do that help waste our time.

Mars as seen by Hubble Space TelescopeWho Would You Take With You to Mars?
What makes a great team? What traits do you value in teammates? Project teams can learn a lot from the latest thinking about designing teams for extended space exploration.

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

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact me for details at rbrenner@ChacoCanyon.com or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.

Get the e-book!

Past issues of Point Lookout are available in five e-books:
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

Person-to-Person Communication for Project Managers
When Person-to-Person Communicationswe talk, listen, send or read emails, read or write memos, or when we leave or listen to voice mail messages, we're communicating person-to-person. And whenever we communicate person-to-person, we risk being misunderstood, offending others, feeling hurt, and being confused. There are so many ways for things to go wrong that we could never learn how to fix all the problems. A more effective approach avoids problems altogether, or at least minimizes their occurrence. In this very interactive program you'll learn a model of inter-personal communications that can help you stay out of the ditch. In those moments of intense involvement, when we're most likely to slip, you'll have a new tool to use to keep things constructive. Read more about this program. Here are some upcoming dates for this program:

The Race to the South Pole: The Power of Agile Development
On 14The Race to the Pole: An Application of Agile Development 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. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's an upcoming date for this program:

Human-Centered Risk Management
Most Human-Centered Risk Managementof us can assess technological risks, but risks related to human behavior tend to resist our best efforts. This session provides a framework for evaluating risks related to the behavior of individuals, teams, organizations and people generally. Human-centered risk differs from technological or market risk, because objective evaluation requires acknowledging personal and organizational limitations and failures. Since some of those limitations and failures might apply to the people assessing the risks, or to their superiors, there's a tendency to deny them or to explain them away. Our approach examines capability, organization, context, risk mitigation, and workplace politics. It has tools for guiding the assessment and management of human-centered risk, and we show how to extend these tools to suit your situation. You'll learn how to identify sources of risk in human behavior; recognize systemic and individual barriers to acknowledging risk; assess the effects of organizational turbulence; determine the risk associated with inappropriate internal risk transfer; estimate the effects of team dysfunction, toxic conflict and turnover; and measure the impact of workplace politics. 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 project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:

Project Management in Fluid Environments
Most Managing in Fluid Environmentspeople now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know what's coming next. In such environments, managing — teams, projects, groups, departments, or the enterprise — often entails moving from surprise to surprise while somehow staying almost on track. It's a nerve-wracking existence. This program provides numerous tools that help project managers who work in fluid environments. Read more about this program. Here's an upcoming date for this program:

The Politics of Meetings for People Who Hate Politics
ThereThe Politics of Meetings for People Who Hate Politics's a lot more to running an effective meeting than having the right room, the right equipment, and the right people. With meetings, the whole really is more than the sum of its parts. How the parts interact with each other and with external elements is as important as the parts themselves. And those interactions are the essence of politics for meetings. This program explores techniques for leading meetings that are based on understanding political interactions, and using that knowledge effectively to meet organizational goals. Read more about this program. Here's an upcoming date for this program:

101 Tips for Targets of Workplace BulliesAre you being targeted by a workplace bully? Do you know what to do to end the bullying? Read 101 Tips for Targets of Workplace Bullies to learn powerful methods for dealing with workplace bullies. Check it out!
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?
My free weekly email newsletter gives concrete tips and suggestions for dealing with the challenging but everyday situations we all face.
A Tip A DayA Tip a Day arrives by email, or by Yahoo! Widget, 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!
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 away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.
SSL