May 8, 2007 | Ken Reed

More Best Practices from the TapRooT® Summit

Here are a few more ideas shared at the TapRooT® User Best Practices session (with Linda Unger, Michele Lindsay and Jade Washmon):

“If an incident appears to be easy to resolve, immediately assign one person to investigate. If the assigned person finds the incident is more complicated, then form a team.”

“Follow through with corrective actions. We developed a system with e-mail notification. Three individuals are assigned to follow-up to make sure corrective action is implemented.”

“Corrective Actions Team: take your corrective actions back to management before the final report is complete.”

“Review process for each investigation. Use a TapRooT® quality checklist – making sure leadership is trained in TapRooT® so when management reviews the checklist, they know what they are looking for.”

“Be efficient with utilization of investigative teams. Establish a goal of the investigation that is thorough, efficient and objective. Cover all bases on data collection: 1) Go see the equipment/facility involved (example, walk to the pothole, check visability); 2) Collect all paper for the incident (example: reports, records); 3) Meet all people involved (conduct interviews); 4) Review recordings (request security videos). Last but not least, recognize your team’s work!”

Root Cause Analysis
Show Comments

Leave a Reply

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