Category: Pictures

Top 3 Reasons for Bad Root Cause Analysis and How You Can Overcome Them…

February 7th, 2017 by

NewImage

I’ve heard many high level managers complain that they see the same problems happen over and over again. They just can’t get people to find and fix the problems’ root causes. Why does this happen and what can management do to overcome these issues? Read on to find out.

 

1. BLAME

Blame is the number one reason for bad root cause analysis.

Why?

Because people who are worried about blame don’t fully cooperate with an investigation. They don’t admit their involvement. They hold back critical information. Often this leads to mystery accidents. No one knows who was involved, what happened, or why it happened.

As Bart Simpson says:

“I didn’t do it.”
“Nobody saw me do it.”
“You can’t prove anything.”

Blame is so common that people take it for granted.

Somebody makes a mistake and what do we do? Discipline them.

If they are a contractor, we fire them. No questions asked.

And if the mistake was made by senior management? Sorry … that’s not how blame works. Blame always flows downhill. At a certain senior level management becomes blessed. Only truly horrific accidents like the Deepwater Horizon or Bhopal get senior managers fired or jailed. Then again, maybe those accidents aren’t bad enough for discipline for senior management.

Think about the biggest economic collapse in recent history – the housing collapse of 2008. What senior banker went to jail?

But be an operator and make a simple mistake like pushing the wrong button or a mechanic who doesn’t lock out a breaker while working on equipment? You may be fired or have the feds come after you to put you in jail.

Talk to Kurt Mix. He was a BP engineer who deleted a few text messages from his personal cell phone AFTER he had turned it over to the feds. He was the only person off the Deepwater Horizon who faced criminal charges. Or ask the two BP company men who represented BP on the Deepwater Horizon and faced years of criminal prosecution. 

How do you stop blame and get people to cooperate with investigations? Here are two best practices.

A. Start Small …

If you are investigating near-misses that could have become major accidents and you don’t discipline people who spill the beans, people will learn to cooperate. This is especially true if you reward people for participating and develop effective fixes that make the work easier and their jobs less hazardous. 

Small accidents just don’t have the same cloud of blame hanging over them so if you start small, you have a better chance of getting people to cooperate even if a blame culture has already been established.

B. Use a SnapCharT® to facilitate your investigation and report to management.

We’ve learned that using a SnapCharT® to facilitate an investigation and to show the results to management reduces the tendency to look for blame. The SnapCharT® focuses on what happened and “who did it” becomes less important.

Often, the SnapCharT® shows that there were several things that could have prevented the accident and that no one person was strictly to blame. 

What is a SnapCharT®? Attend any TapRooT® Training and you will learn how to use them. See:

TapRooT® Training

NewImage

2. FIRST ASK WHAT NOT WHY

Ever see someone use 5-Whys to find root causes? They start with what they think is the problem and then ask “Why?” five times. Unfortunately this easy methods often leads investigators astray.

Why?

Because they should have started by asking what before they asked why.

Many investigators start asking why before they understand what happened. This causes them to jump to conclusions. They don’t gather critical evidence that may lead them to the real root causes of the problem. And they tend to focus on a single Causal Factor and miss several others that also contributed to the problem. 

How do you get people to ask what instead of why?

Once again, the SnapCharT® is the best tool to get investigators focused on what happened, find the incidents details, identify all the Causal Factors and the information about each Causal Factor that the investigator needs to identify each problem’s root causes.

NewImage

3. YOU MUST GO BEYOND YOUR CURRENT KNOWLEDGE

Many investigators start their investigation with a pretty good idea of the root causes they are looking for. They already know the answers. All they have to do is find the evidence that supports their hypothesis.

What happens when an investigator starts an investigation by jumping to conclusions?

They ignore evidence that is counter to their hypothesis. This problem is called a:

Confirmation Bias

It has been proven in many scientific studies.

But there is an even bigger problem for investigators who think they know the answer. They often don’t have the training in human factors and equipment reliability to recognize the real root causes of each of the Causal Factors. Therefore, they only look for the root causes they know about and don’t get beyond their current knowledge.

What can you do to help investigators look beyond their current knowledge and avoid confirmation bias?

Have them use the SnapCharT® and the TapRooT® Root Cause Tree® Diagram when finding root causes. You will be amazed at the root causes your investigators discover that they previously would have overlooked.

How can your investigators learn to use the Root Cause Tree® Diagram? Once again, send them to TapRooT® Training.

THAT’S IT…

The TapRooT® Root Cause Analysis System can help your investigators overcome the top 3 reasons for bad root cause analysis. And that’s not all. There are many other advantages for management and investigators (and employees) when people use TapRooT® to solve problems.

If you haven’t tried TapRooT® to solve problems, you don’t know what you are missing.

If your organization faces:

  • Quality Issues
  • Safety Incidents
  • Repeat Equipment Failures
  • Sentinel Events
  • Environmental Incidents
  • Cost Overruns
  • Missed Schedules
  • Plant Downtime

You need to be apply the best root cause analysis system: TapRooT®.

Learn more at: 

http://www.taproot.com/products-services/about-taproot

And find the dates and locations for our public TapRooT® Training at:

 http://www.taproot.com/store/Courses/

NewImage

TapRooT® Around the World: Dubai, UAE

January 20th, 2017 by

A great onsite course in Dubai this week for Weatherford International.

unnamed

unnamed-1

Want TapRooT® to bring a course to you? Inquire here.
Want to send your team to a course near you? Check our calendar for upcoming courses.

Have You Planned Your TapRooT® Training for 2017?

January 10th, 2017 by

 Are you sending people to our Public TapRooT® Training?

 

Public

 

Or are you having a TapRooT® Course at your site?

 

Class picture

 

And arranging TapRooT® Training at one or more of your facilities around the world?

 

KualaLumpur

 

If you want to choose your dates, now is the time to get your onsite courses scheduled.

And if you want to choose a particular public course, now is the time to get your folks registered!

TapRooT® Around the World: Course in Mongolia

December 27th, 2016 by

One of our instructors, Peter Berkholz, held a great TapRooT® course for Transwest in Ulaanbaatar, Mongolia.

unnamed

Want TapRooT® to come to you for a course? Inquire here.

Want to send some team members to a TapRoooT® course? See our 2017 schedule here.

TapRooT® Around the World: Onsite Course at Torex

December 22nd, 2016 by

Last week we had a great course at Torex in Guerrero, Mexico!unnamed-3

unnamed

unnamed-2

unnamed-4

unnamed-1

 

If your company would like TapRooT® to bring training to you, inquire here.

If you want to send some team members to a public course, see our many options here.

TapRooT® Around the World: Ecuador

December 12th, 2016 by

A great 2-Day TapRooT® course in Ecuador at AGUIP!

20161129_085257 20161129_085320 20161129_085231

Monday Accident & Lessons Learned: Railroad Bridge Structural Failure

December 12th, 2016 by

Screen Shot 2016 11 14 at 6 18 33 PM

A Report from the UK Rail Accident Investigation Branch:

Structural failure caused by scour at Lamington viaduct, South Lanarkshire, 31 December 2015

At 08:40 hrs on Thursday 31 December 2015, subsidence of Lamington viaduct resulted in serious deformation of the track as the 05:57 hrs Crewe to Glasgow passenger service passed over at a speed of about 110 mph (177 km/h). The viaduct spans the River Clyde between Lockerbie and Carstairs. Subsequent investigation showed that the viaduct’s central river pier had been partially undermined by scour following high river flow velocity the previous day. The line was closed for over seven weeks until Monday 22 February 2016 while emergency stabilisation works were completed.

The driver of an earlier train had reported a track defect on the viaduct at 07:28 hrs on the same morning, and following trains crossed the viaduct at low speed while a Network Rail track maintenance team was deployed to the site. The team found no significant track defects and normal running was resumed with the 05:57 hrs service being the first train to pass on the down line. Immediately after this occurred at 08:40 hrs, large track movements were noticed by the team, who immediately imposed an emergency speed restriction before closing the line after finding that the central pier was damaged.

The viaduct spans a river bend which causes water to wash against the sides of the piers. It was also known to have shallow foundations. These were among the factors that resulted in it being identified as being at high risk of scour in 2005. A scheme to provide permanent scour protection to the piers and abutments was due to be constructed during 2015, but this project was deferred until mid-2016 because a necessary environmental approval had not been obtained.

To mitigate the risk of scour, the viaduct was included on a list of vulnerable bridges for which special precautions were required during flood conditions. These precautions included monitoring of river levels and closing the line if a pre determined water level was exceeded. However, this process was no longer in use and there was no effective scour risk mitigation for over 100 of the most vulnerable structures across Scotland. This had occurred, in part, because organisational changes within Network Rail had led to the loss of knowledge and ownership of some structures issues.

Although unrelated to the incident, the RAIB found that defects in the central river pier had not been fully addressed by planned maintenance work. There was also no datum level marked on the structure which meant that survey information from different sources could not easily be compared to identify change.

As a result of this investigation, RAIB has made three recommendations to Network Rail relating to:

  • the management of scour risk
  • the response to defect reports affecting structures over water
  • the management of control centre procedures.

Five learning points are also noted relating to effective management of scour risk.

For more information, see:

R222016_161114_Lamington_viaduct

TapRooT® Around the World: Colombia

December 9th, 2016 by

TapRooT® course in Colombia recently had a great group! unnamed-10 unnamed unnamed-7 unnamed-6 unnamed-8 unnamed-3 unnamed-9 unnamed-4 unnamed-1 unnamed-2 unnamed-5

For more information on our TapRooT® courses, click here.

Old Fashioned Definition of Root Cause vs. Modern Definition of Root Cause

November 29th, 2016 by

NewImage

When we first started the development of TapRooT® back in the 1980s, we developed this definition of a root cause:

Root Cause
The most basic cause (or causes)
that can reasonably be identified 
that management has control to fix
and, when fixed, will prevent 
(or significantly reduce the likelihood of)
the problem’s recurrence.

The modern definition of a root cause, which was proposed in 2006 by Mark Paradies at the Global TapRooT® Summit and really isn’t so new, is:

Root Cause
The absence of best practices
or the failure to apply knowledge
that would have prevented the problem.

 This modern definition of a root cause leads to this definition of root cause analysis:

Root Cause Analysis
The search for the best practices
and/or the missing knowledge that
will keep a problem from recurring

Since most people (including, in the past, me) say that root cause analysis is the search for why something failed, this reversal of thinking toward looking for how to make something succeed is truly a powerful way of thinking. The idea changes the concept of root cause analysis.

Even though a decade had passed since proposing this new definition, I still have people ask:

Why did you change the definition? I liked it like it was!

Therefore, I thought that with the new TapRooT® Books coming out, I would explain our reasoning to show the clear advantage of the modern definition.

The modern definition focuses on the positive. You will search for best practices and knowledge. You aren’t looking for people to blame or management faults. Yes, a best practice or knowledge is missing, but you are going to find out how to do the work more reliably. Thus, the focus is on improvement … the opportunity to improve vision!

The same thing can be said about the old fashioned definition too. But the old definition focused on cause. The difference in the definitions is a matter of perspective. Looking up at the Empire State Building from the bottom is one perspective. Looking down the Empire State Building from the top is quite another. The old definition looked at the glass as half empty. The new definition looks at the glass as half full. The old definition focuses on the “cause.” The modern definition focuses on the solution.

This shift in thinking leads people to a better understanding of root causes and how to find them. When it is combined with the Root Cause Tree® and Dictionary, the thinking revolutionizes the search for improved performance.

The concept of looking for ways to improve has always been a part of the TapRooT® System. It is the secret that makes TapRooT® such a powerful tool. But the modern definition – the new perspective – makes it easier to explain to others why TapRooT® works so well. TapRooT® is a tool that finds the missing knowledge or best practices that are needed to solve the toughest problems.

One last note about the modern definition: In the real world, absolutes like “will prevent” can seldom be guaranteed. So the root cause definition should probably be augmented with the additional phrase: “or significantly reduce the likelihood of the problem’s recurrence.” We chose not to add this phrase in the definition to keep the message about the new focus as strong as possible. But please be aware that we understand the limits of technology to guarantee absolutes and the ingenuity of people to find ways to cause errors even in well-designed systems.

That’s the reasons for the definition change. You may agree or disagree, but what everyone finds as true is that TapRooT® helps you find and fix the root causes of problems to improve safety, quality, productivity, and equipment reliability.

Attend a TapRooT® Course and find out how TapRooT® can help your company improve performance.

Monday Accident & Lessons Learned: Collision at Yafforth, UK, level crossing, 3 August 2016

November 28th, 2016 by

NewImage

For a report from the UK Rail Accident Investigation Branch, see:

www.gov.uk

Happy Thanksgiving

November 24th, 2016 by

Here is my Thanksgiving posting. I post it every year, lest we forget…

NewImage

In America, today (Thursday) is a day to get together with family and friends and reflect on our blessings – which are many!

One of my ancestors, Peregrine White, was the first child born to the Pilgrims in the New World.

During November of 1620, Peregrine’s mother Susanna, gave birth to him aboard the ship Mayflower anchored in Provincetown Harbor. His father, William, died that winter – a fate shared by about half of the Pilgrim settlers.

The Pilgrims faced death and the uncertainty of a new, little explored land. Why? To establish a place where they could worship freely.

With the help of Native Americans that allied with and befriended them, they learned how to survive in this “New World.” Today, we can be thankful for our freedom because of the sacrifices that these pioneers made to worship God in a way that they chose without government control and persecution.

Another interesting history lesson about the Pilgrims was that they initially decided that all food and land should be shared communally. But after the first year, and almost starving to death, they changed their minds. They decided that each family should be given a plot of land and be able to keep the fruits of their labors. Thus those that worked hardest could, in theory, reap the benefits of their extra labor. There would be no forced redistribution of the bounty.

The result? A much more bountiful harvest that everyone was thankful for. Thus, private property and keeping the fruits of one’s labor lead to increased productivity, a more bountiful harvest, and prosperity.

Is this the root cause of Thanksgiving?

This story of the cause of Thanksgiving bounty is passed down generation to generation in my family. But if you would like more proof, read the words of the first governor of the Plymouth Colony, William Bradford:

“And so assigned to every family a parcel of land, according to the proportion of their number, or that end, only for present use (but made no division for inheritance) and ranged all boys and youth under some family. This had very good success, for it made all hands very industrious, so as much more corn was planted than otherwise would have been by any means the Governor or any other could use, and saved him a great deal of trouble, and gave far better content. The women now went willingly into the field, and took their little ones with them to set corn; which before would allege weakness and inability; whom to have compelled would have been thought great tyranny and oppression.”

William Bradford, Of Plymouth Plantation 1620-1647, ed. Samuel Eliot Morison (New York : Knopf, 1991), p. 120.

What You May Not Know About Mark Paradies, President of System Improvements

November 14th, 2016 by

 

P1020482

As a TapRooT® User, you probably know that Mark is one of the co-creator’s of the TapRooT® Root Cause Analysis System and a co-author of the TapRooT® Book series. You have probably heard that he has all sorts of experience with root cause analysis and incident investigation. But did you know that …

Mark is a Certified Professional Ergonomist (CPE).

He was the 85th person to be certified in ergonomics and human factors by the Board of Certified Professional Ergonomists. Mark has worked extensively on projects to improve human performance and reduce human errors. 

His Masters Degree research at the University of Illinois was focused on the proper roles of operators and automation for the next generation of nuclear power plants (human factors function allocation).

Before starting System Improvements, he worked on projects to improve aspects of human performance including procedures usability and usage, and operator, maintenance, and technical training.

He also developed systems for managing performance improvement in a resource limited environment.

He used his human factors knowledge and experience to build into the TapRooT® System the ability to analyze and fix human performance/human behavior issues.

Mark was in Admiral Rickover’s Nuclear Navy (a High Reliability Organization).

Mark has studied high reliability organizations. But Mark has one major advantage over most of those who do academic research and speak about high reliability organizations … He has worked in a high reliability organization – the Nuclear Navy (the original high reliability organization). Therefore, he knows what works, why it works, and what doesn’t work BECAUSE HE HAS BEEN THERE. He understands Admiral Rickover’s management systems and practical methods to guard against normalization of deviation.

Mark has a unique understanding of process safety.

Marks has two engineering degrees (BSEE and MS Nuc E), human factors training, and experience working in Admiral Rickover’s Nuclear Navy (where he achieved his Engineer Certification). This gives him a unique understanding of process/nuclear safety. He has written about this experience (see this LINK) and provided talks for companies interested in improving their process safety systems and senior management understanding of process safety. (See part of his Summit talk in 2012 HERE.)

Mark has developed trending techniques for infrequently occurring safety and quality data.

Mark used the work of statistical experts Dr. Donald Wheeler, Dr. Walter Shewhart, and W. Edwards Deming to develop techniques to find statistically valid trends of infrequently occurring accident data. Mark is working on a new book about performance measurement and trending that will be published in 2017. Watch for the next trending course based on his work being held prior to the 2018 Global TapRooT® Summit.

Mark has practical experience.

In his spare time between working for high reliability organizations (the Nuclear Navy and Du Pont) and leading System Improvements, Mark designed and built roads (driving a bulldozer, track loader, excavator, and dump trucks), produced hardwood lumber from trees, and helped design two houses. While working in college getting his  BS in Electrical Engineering, he was a field supervisor (in actual agricultural fields) and a cable TV installation and repair man. While still in high school, Mark worked in agricultural jobs, construction, retail, and ran his own lawn mowing and landscape business.

That’s a little more about the lessor known facts about Mark’s experience and expertise. If you have questions for Mark or would like him to consult with you about your improvement efforts, contact him at this LINK, or call 865-539-2139.

Connect with Us

Filter News

Search News

Authors

Barb PhillipsBarb Phillips

Editorial Director

Chris ValleeChris Vallee

Six Sigma

Dan VerlindeDan Verlinde

Software Development

Dave JanneyDave Janney

Safety & Quality

Gabby MillerGabby Miller

Communications Specialist

Ken ReedKen Reed

Equifactor®

Linda UngerLinda Unger

Vice President

Mark ParadiesMark Paradies

Creator of TapRooT®

Steve RaycraftSteve Raycraft

Technical Support

Success Stories

Reporting of ergonomic illnesses increased by up to 40% in…

Ciba Vision, a Novartis Company

Our Acrylates Area Oxidation Reactor was experiencing frequent unplanned shutdowns (trips) that…

Rohm & Haas
Contact Us