Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

June 7, 2023 | Mark Paradies

Investigating the Root Causes of Procedure Problems

Procedure

TapRooT® RCA Procedure Investigation Guidance

TapRooT® Users … How do you investigate an incident that includes a procedure problem?

Easy! There is guidance on pages 170-172 of Book 4: TapRooT® Root Cause Analysis for Major Investigations.

Book 4

The book has these eight steps to investigate problems in the Procedures Basic Cause Category:

  1. Get an unused copy of the procedure.
  2. Get the completed, signed-off or checked-off procedure (if sign-off/check-off is required).
  3. Get any reference material/documentation.
  4. Was the procedure used?
  5. Was it signed off properly?
  6. Verify the technical accuracy of the procedure (table-top review).
  7. Verify the usability of the procedure by performing a field walk-through. (Consider performing a Critical Human Action Profile, Appendix F, and reviewing potential human factors problems at the same time.)
  8. If problems are found, consider looking for generic causes in the procedure writing and review system.

That’s the guidance for procedure problems. What about human factors, work direction, training, or management system problems? Book 4 has guidance for all the Basic Cause Categories from the back side of the TapRooT® Root Cause Tree®.

My Favorite Procedure Related Investigation Story

My favorite procedure-related story was an investigation where the team doing the investigation said that the person who was injured was using a procedure. I asked to see it. They said:

“You want to see the procedure?”

I said, “Yes.”

They sent someone off to get it.

They came back with a brown paper grocery bag.

procedure on a brown paper bag

They handed it to me.

I said, “What’s this?”

They said, “the procedure.”

I looked in the bag. There was nothing inside.

They said, “No look on the outside of the bag.”

There were handwritten notes on the outside of the bag. Mainly equipment part numbers. That was …

The Procedure.

The person who was performing the work had written a list of what parts went in which crates for shipment. There was no procedure for doing the work.

Lesson Learned

ALWAYS ask for the procedure when someone says that a procedure was used. You might get a good laugh too!

Learn More About Advanced Root Cause Analysis

course, TapRooT® Training
People enjoying a TapRooT® Root Cause Analysis Course.

We hold public courses on advanced root cause analysis around the world. See the course types HERE. See the upcoming dates and locations HERE.

If you would like a quote for a course at yoour site, contact us by calling 865-539-2139 or CLICK HERE.

Categories
Root Cause Analysis
-->
Show Comments

Leave a Reply

Your email address will not be published. Required fields are marked *