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.

January 6, 2010 | Ken Reed

Root Cause Analysis Tip: Use of Checklists

Yesterday, I posted an article that discussed the advantages of using checklists in the medical profession (see this link).  I thought I’d talk a little more about checklists and how the use of checklists shows up on the Root Cause Tree® Diagram.

Let’s look at a reactive incident, where someone made a mistake while performing a common yet labor-intensive evolution.  For example, a mechanic was starting up an expensive compressor, and he forgot one step, causing serious damage to the machine.  He has done this evolution several times and is familiar with the equipment, but this time, one step out of 16 was missed.  This is a very typical example, and your analysis must take into account many different possibilities.  Happily, TapRooT® walks you through the analysis to make sure you don’t forget to check everything.  The Root Cause Tree® and Dictionary® will have you check many potential problems (fatigue, equipment design, work environment, supervision, etc).  However, I’d like to concentrate on:

“When should we expect to have a checklist in place?”

Looking at the Corrective Action Helper® under no procedure, we get some ideas concerning when a step-by-step checklist makes sense. 

– First of all, if a new checklist had been in place, would performance have improved?  Would this mistake have been prevented?  Sometimes, the task is so obvious that having a checklist would not fix anything.  If this is the case, don’t write a silly checklist just for the sake of having a checklist.  For example, if someone forgets to wear his seatbelt, I highly doubt that putting a checklist in the cab of the truck telling the driver when and how to put on a seatbelt is going to make any difference.  This is an obvious evolution, and other corrective actions (audits of seatbelt compliance, proper rewards for wearing seatbelts, consistent enforcement of the rule) will be much more effective.

Additionally, situations where other factors have made it easy for the operator to make a mistake (poorly designed equipment, excessively fatigued workers, etc.) probably need these other issues addressed first and then evaluate whether a procedure would also help.

– The Corrective Action Helper® also states that a checklist makes sense for high-risk, high-consequence tasks that must be performed correctly every time and require considerable short-term memory.  Starting this expensive compressor is an example where checklist use should be considered.  Other examples include:
a. documentation of the work is required
b. extremely infrequent evolutions
c. tasks that must be performed under stress, like emergencies (both aircraft engines shut down due to a bird strike?)

What do you do when you have checklists, but people aren’t using them?  You are now under the enforcement root cause, and the Corrective Action Helper® has a load of great information on how tackle this problem.

What are your thoughts on checklists?  Do you have examples of checklists that helped?  What about a checklist that was completely useless at your facility?  Let me know what you think!

Categories
Root Cause Analysis
-->
Show Comments

Leave a Reply

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