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 27, 2022 | Mark Paradies

Blog Posting on How To React To A Mistake

Mistake

The Wrong Way to React to a Mistake

The blog posting on another site starts out with …

I was thrashed by my boss way back in 2001 for a minor mistake I did working on a project based on a very new technology. I literally had tears in my eyes after I was shouted upon, knowing that I had worked on the module for 18 hours at a stretch without taking a single break, learning the technology and getting the job done. My mistake was minor, but the one my boss committed was major. He lost my respect.  Shouting was his way of reinforcing the belief that he was in charge. I moved on!

Is This a Better Way to React?

The same blog posting also related this story…

Another interesting case happened with one of my friends Alan who was a tech lead with a multi-national company. He had accidentally replaced the production database with an incorrect version leading to overall application failure. Alan knew that he would get a beating and probably may lose his job. While he was still preparing himself mentally for the eventuality, his manager approached him. He entered with a smile on his face and said “I know this is serious, but I am also sure you would do whatever it takes to correct this. Let us put our best and get this back on track”. Alan and his team worked overnight to correct it the next morning and the client really appreciated this in form of an encouraging email. A few days after this incident, the manager called Alan in the canteen to share a cup of coffee. It was then that the manager inquired about the root cause of such a mistake. The manager informed Alan that such mistakes should not have happened and that he needs to be careful in the future.

Being more careful IS NOT a good corrective action. This shows that the manager did not understand root cause analysis and effective corrective actions. But I like the ideas in the article.

The Right Way to Find Root Causes and Develop Effective Corrective Actions

If you would like to learn effective root cause analysis that helps you develop effective corrective actions, I would suggest attending a TapRooT® Root Cause Analysis Course.

You can have these courses at your site or attend one of our public courses held around the world.

For our public course schedule, see:

https://store.taproot.com/courses

To schedule a course at your site, contact one of our TapRooT® Implementation Advisors at 865-539-2139 or by CLICKING HERE.

Implementation Advisors

Whole Blog Posting

To read the whole post, see:

http://qualsys.wordpress.com/2008/11/10/to-err-is-human-treating-people-when-they-make-mistakes/

Note that our blog post is a reprint from 2008. Since that time, the referenced blog has been made “private.” Now you will need to get permission to read the whole article.

Categories
Accident
-->
Show Comments

Leave a Reply

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