How to Write Effective Corrective Actions

By Kevin McManus, Chief Excellence Officer, Great Systems

A well-written corrective action clearly defines how to modify a process, or alter a piece of equipment, in order to reduce the potential for future human error or equipment failure. When we modify a process, we can add, or delete, one or more process steps. Also, we might rewrite the standard operations procedure so it is more usable. All too often however, we attempt to use weak fixes to prevent future problems of a significant nature. How many of your staff know how to write effective actions?

If we want to modify the work environment or equipment, diligence must be taken to ensure that we provide an adequate level of detail.  When leaders make changes of this nature and fail to include sufficient detail, it can actually worsen the problem from a human-machine or human versus work environment perspective. At the same time, many corrective actions are too general in focus. Worse yet, they might fail to define an actual process or equipment change.

If you would like to learn how to mistake proof your work processes and consistently write effective corrective actions, please take a look at my 2-day virtual “Best Practices in Mistake Proofing and Corrective Writing” workshop.

A Possible Workflow for Writing Effective Corrective Actions

If you use the TapRooT® root cause analysis process to find root causes and write effective corrective actions, the above workflow may help. In this process, there are multiple points where an incomplete investigation can result in less than effective fixes. However, you can avoid such gaps.

Design the investigation process to capture the right mix of evidence. Teach investigators how to effectively use this evidence to find key causal factors, root causes, and ultimately, effective fixes. Install effective corrective and preventive actions that minimize the chance of your problems coming back.

DISCOVER MORE: How Great are Your Work Systems?

Define Expectations for Effective Corrective Action Design

Once the new rules and direction are set, leaders must define and execute a systematic means to communicate these procedural changes to the workforce. A well-written corrective action should also define what formal mechanisms will be used to gauge (1) if the change was put in place and (2) if the change was effective.

The CAPA Guidelines perhaps provide the best definition of a corrective action. These guidelines state that “documentation for a corrective action provides evidence that the problem was recognized, corrected, and proper controls installed to make sure that it does not happen again.”

When I teach people how to write corrective actions, or when I write them myself, I use the ‘corrective action burger’ approach. This sentence approach helps me make sure that I include two things in the main body of the corrective action I write. First, I need to provide sufficient detail on the change to be made. Second, I need to describe how to roll out the change to all stakeholders.

LEARN MORE: Root Cause Analysis FAQs

Why Writing Effective Corrective Actions Matters

Effective corrective actions eliminate or minimize the reoccurrence of the ‘at risk’ behaviors that were part of the incident. If you ask to what degree will the fix take away, or minimize, those behaviors, you can quickly determine the potential impact of a given fix. You can also assess the change in risk level once the likelihood of error, and possibly the severity of error, have been reduced.

In general, leaders expect too much behavior change that lasts from weak fixes like reprimands, reminders, and more rules. A certain percentage of people will change for good when you ask them to, but others need system changes to help guide, encourage, and reinforce their use of the new behaviors.

What are your favorite fixes? How do you teach people to both identify and write more effective corrective actions? Odds are that if you improve this process alone, you could save significant time and money. You will also reduce the potential for process errors.

EXPLORE MORE: Safety System Best Practices

Three First Steps for Writing Effective Corrective Actions

Review your most recent 50 or so root causes and corrective actions. What patterns, biases, and gaps do you see? Do you have favorite root causes and fixes? Are there certain types of root causes and fixes you don’t see very often on the list?

Require the effective completion of a corrective action writing class. This class does not have to fancy, expensive, or even live, but it does need to include practice writing effective corrective actions. One or more coaches should be on hand to provide feedback on the practice corrective actions as they are written. Support this in-class practice with the use of examples of both well-written and poorly written fixes. This use of examples helps define post-class expectation standards.

Evaluate ‘fix mix’ strength against potential problem severity to ensure a match exists. All too often we base our mix of necessary corrective actions on what actually did occur versus what the outcome might have been. The difference between a near miss and a fatality is often not that much. We should not dilute our mix of fixes just because we got lucky in this instance. We should always ask “What could have been the outcome?”

DISCOVER MORE: How Effective is your Process Improvement Work System?

Three More Steps to Help Write Effective Corrective Actions

Push for creative, engineered fixes. One way to do this is to always recommend at least one engineered fix of some fashion in any mix of changes you propose. Another way to push for engineered fixes is to work your way down the hierarchy of controls as you look for solutions. Human factors improvements can often be made without the need for a significant investment. Examples include the use of color codes, RFID asset tags, and tablet-based behavior cues and triggers.

What options exist to help eliminate or minimize the potential for hazard or defect exposure? Can you better protect the customer or the patient from potential hazards or errors? Can we do better guard the internal or external customer from the potential problem?

Expect ‘high risk’ behavior observation trends to reflect corrective action effectiveness The best way to tell the degree to which your corrective actions are working or not is to look for ‘high risk behaviors’ during daily process operation. What are your work process error rates? Have the error or failure rates decreased?

Reduce the holes in your current safeguards before you add new ones (more slices of cheese). Too few companies measure safeguard effectiveness. In turn, they don’t know the relative degree to which each safeguard type is effective. They assume that the safeguards in place work somewhat, but they need more of them to prevent the current rate of errors.

LEARN MORE: Buy my “Error Proof – How to Stop Daily Goofs for Good” book at Amazon.com

How Do You Know When Your Corrective Actions are Effective?

In reality, much opportunity exists for safeguard improvement if you use best practices as a guide in most companies. Instead of spending more time and money trying to prevent errors, spend the existing time and money you now contribute to this purpose differently.

Once a corrective action has been written, you should always question the degree to which it will be effective. It is even more important to assess the relative impact of the set of corrective actions that you will recommend and implement. Will this mix of fixes significantly reduce the risk from future human errors or equipment failures of this type?

If you would like to learn how to mistake proof your work processes and consistently write effective corrective actions, please take a look at my 2-day virtual “Best Practices in Mistake Proofing and Corrective Writing” workshop. You can also always email me at kevin@greatsystems.com!

Keep improving!

Kevin McManus, Chief Excellence Officer, Great Systems

www.greatsystems.com      kevin@greatsystems.com

LIKE Great Systems on Facebook

CONNECT with me on LinkedIn

CHECK OUT my Amazon.com Author Page

FOLLOW me on Twitter: @greatsystems