Category: Video

Technically Speaking – TapRooT® VI User Settings Menu

April 20th, 2017 by

Here is a quick video highlighting the new User Settings menu in TapRooT® VI.

Technically Speaking is a weekly series that highlights various aspects of the TapRooT® VI software and occasionally includes a little Help Desk humor.

Remember, just because it’s technical, it doesn’t mean it has to be complicated!

Are You Writing the Same Corrective Actions?

April 17th, 2017 by

Repeating the same corrective actions over and over again defeats the purpose of a quality root cause analysis investigation. If you spend the time investigating and digging deeper to find the REAL root cause, you should write the most effective corrective actions you can to ensure it was all worth the resources put into it. Instructor & Equifactor® and TapRooT® Expert, Ken Reed, talks about corrective actions and how to make them new and effective for each root cause.

 

Take a TapRooT® Root Cause Analysis course today to learn our effective and efficient RCA methodology. 

Technically Speaking – TapRooT® VI Exporting Trending Data

April 13th, 2017 by

Here is a quick video highlighting the Export Trending Data feature in TapRooT® VI.

Technically Speaking is a weekly series that highlights various aspects of the TapRooT® VI software and occasionally includes a little Help Desk humor.

Remember, just because it’s technical, it doesn’t mean it has to be complicated!

How to Interpret Body Language In Your Incident Investigation Interviews

April 10th, 2017 by

TapRooT® Instructor and Non-Verbal Communication Expert, Barb Phillips, explains how to interpret common body language cues with an example investigative interview. Watch here for some investigative interviewing tips!

Want to know more? Take a TapRooT® Effective Interviewing and Evidence Collection course.

Technically Speaking – TapRooT® VI New Features

March 30th, 2017 by

*NOTE that Audit logging and Customizing Equifactor ® are features only available for TapRooT® VI Enterprise.  Contact sales@taproot.com to get Enterprise Software.

These enhancements are considered the 6.2.0 release.

Technically Speaking is a weekly series that highlights various aspects of the TapRooT® VI software and occasionally includes a little Help Desk humor.

Remember, just because it’s technical, doesn’t mean it has to be complicated!

Case Study: Using Dye Packs to Locate Leaks

March 16th, 2017 by

Watch as Brian Tink discusses how his company used dye packs to help them isolate the location of a pipe leak.

Technically Speaking – TapRooT® VI Notifications Feature

March 9th, 2017 by

Here is a quick video highlighting the new notifications system in TapRooT® VI.

Technically Speaking is a weekly series that highlights various aspects of the TapRooT® VI software and occasionally includes a little Help Desk humor.

Remember, just because it’s technical, it doesn’t mean it has to be complicated!

Technically Speaking – TapRooT® VI Attachments

February 23rd, 2017 by

Here is a quick video highlighting the Attachment Tab and how to upload files in TapRooT® VI.

Technically Speaking is a weekly series that highlights various aspects of the TapRooT® VI software and occasionally includes a little Help Desk humor.

Remember, just because it’s technical, it doesn’t mean it has to be complicated!

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

Technically Speaking – Creating a Paperless Report (Part 3)

December 29th, 2016 by

Here is the finale of our three-part series detailing the steps to take a paper report and re-create it in the TapRooT® VI software.

Here are: Part 1 Part 2

Technically Speaking is a weekly series that highlights various aspects of the TapRooT® VI software and occasionally includes a little Help Desk humor.

Remember, just because it’s technical, it doesn’t mean it has to be complicated!

Technically Speaking – Creating a Paperless Report (Part 2)

December 15th, 2016 by

Here is part two of our three part series detailing the steps to take a paper report and re-create it in the TapRooT® VI software.

You can find Part 1 here: Part 1

Technically Speaking is a weekly series that highlights various aspects of the TapRooT® VI software and occasionally includes a little Help Desk humor.

Remember, just because it’s technical, it doesn’t mean it has to be complicated!

How Far Away is Death?

December 4th, 2016 by

Teenagers seem to have no concept of how far away from death that they are. Very few over 25 would do this…

Technically Speaking – Creating a Paperless Report (Part 1)

December 1st, 2016 by

I wanted to introduce you to a short three part series detailing the steps to take a paper report and re-create it in the TapRooT® VI software.

Technically Speaking is a weekly series that highlights various aspects of the TapRooT® VI software and occasionally includes a little Help Desk humor.

Remember, just because it’s technical, doesn’t mean it has to be complicated!

Monday Accident & Lessons Learned: Remembering The Concord Crash

November 21st, 2016 by

Found this TV show about the crash and thought it was interesting … What can you learn?

 

How Far Away is Death?

November 3rd, 2016 by

One guy … 8 near-death experiences!

Fatal Theme Park Ride in Australia

November 2nd, 2016 by

Here’s the press report.

A similar ride in the US has been closed while the investigation is ongoing. 

Connect with Us

Filter News

Search News

Authors

Angie ComerAngie Comer

Software

Barb PhillipsBarb Phillips

Editorial Director

Chris ValleeChris Vallee

Six Sigma

Dan VerlindeDan Verlinde

VP, Software

Dave JanneyDave Janney

Safety & Quality

Gabby MillerGabby Miller

Marketing

Garrett BoydGarrett Boyd

Technical Support

Ken ReedKen Reed

VP, Equifactor®

Linda UngerLinda Unger

Co-Founder

Mark ParadiesMark Paradies

Creator of TapRooT®

Per OhstromPer Ohstrom

VP, Sales

Shaun BakerShaun Baker

Technical Support

Steve RaycraftSteve Raycraft

Technical Support

Wayne BrownWayne Brown

Technical Support

Success Stories

We started using TapRooT® in the mid 1990s after one of our supervisors wanted to instill a more formal process to our investigations…

CONOCO PHILLIPS

Alaska Airlines adopted System Safety and incorporated TapRooT® into the process to find the root causes…

Alaska Airlines
Contact Us