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.

August 10, 2010 | Mark Paradies

How Do You Measure Backlog

Almost everyone would agree that backlogs of incident investigations and corrective actions are BAD. Imagine if you have another accident while you are waiting for a corrective action to be completed.

Therefore, the measurement of the backlog could be used as a performance measure.

But how do you measure “backlog”?

Let’s start with incident investigation backlog.

First, one measure is the oldest outstanding root cause analysis. But one hard investigation doesn’t necessarily mean that you have a bad program.

Therefore, second, people tend to measure the average time to complete an investigation. This could be measured using a twelve month rolling average.

But an average time doesn’t say much about the total number of investigations outstanding. So some use the total number of investigations not completed as a program measure.

One additional idea is to measure the total number of investigations overdue (beyond some standard for completion (i.e., 30 days or 90 days).

Who knew measuring backlog could be so hard?

Corrective action (improvement) backlog is similar … Longest outstanding item, the average time to complete an item, the total number of outstanding items, and the total number overdue.

Actually, measuring all of these is a good idea. And trending them using advanced trending techniques is a great idea! Read the trending book (pictured above).

Categories
Implementation
-->
Show Comments

Leave a Reply

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