Corrective actions that fix the cause, not the symptom

A customer receives the wrong item. Someone sends the right one, apologises and everyone moves on. Two months later it happens again. The first time you made a correction. You did not make a corrective action, so the cause was still there, waiting.

Fixing the thing in front of you is necessary and not enough. A corrective action changes how the work is done so that this kind of problem becomes rare. It is one of the most useful habits a small business can have, and it does not need to be complicated.

Six steps, in order

1. Describe the problem. Plain facts: what, where, when, how it was noticed, who or what was affected.
2. Contain it. Stop it getting worse and put the customer right.
3. Find the cause. Ask why until you reach something you can change.
4. Decide the action. One or a few changes, each with an owner and a date.
5. Do it.
6. Check that it worked, after enough time has passed to see, and close it.

Most failures happen at steps 3 and 6: people stop at the first answer, and nobody checks later.

Describe the problem without blame

Write the facts in one or two sentences: "On 4 March, order 1182 was shipped with the blue model instead of the green. The customer wrote on 7 March." Leave out guesses and adjectives. A problem described as "John was careless" gets defended. A problem described as "the order sheet lists colours by code, and the codes for blue and green differ by one digit" can be fixed.

Contain first

Containment is what you do today: send the right item, refund, apologise, warn the people affected, check whether other orders have the same problem. If the customer needs a message, a short, honest apology works better than a long one. The customer apology email template gives the shape: say what happened, say what you are doing about it, say what happens next.

Check for others. If one order had the wrong colour, look at the others packed in the same batch.

Find the cause by asking why

The classic method is simply to ask "why?" and keep going. Example:

• Why was the wrong item sent? Because the packer picked the blue box.
• Why did they pick blue? Because the code on the order sheet looked like the code on the blue box.
• Why do the codes look alike? Because we number colours in one sequence with one digit apart.
• Why did nobody notice? Because the check at packing only compares the first three digits of the code.

Now there are two things you can change: the codes, and the check. "The packer was careless" would not have helped anyone.

A few warnings:

• A person is almost never the root cause. If the answer is a name, ask what made the mistake easy: unclear instructions, no training, too much time pressure, a bad tool.
• There may be more than one cause. Write them all, then pick those you can act on.
• Do not guess. If you cannot tell, add a check to see what happens next time and write down that you are gathering evidence.
• Ask the people who do the work. They often know the cause immediately.

Choose actions you can finish

Good actions are specific, owned and dated. "Be more careful" is not an action. "Renumber colour codes so that no two differ by only one digit, by 20 March, owner: Priya" is.

Prefer changes that make the mistake hard to make over reminders to people. In order of strength:

1. Remove the cause altogether, for example by changing the codes.
2. Build in a check, for example a scan that compares the whole code.
3. Make the right way easier, for example a photo on the order sheet.
4. Train or remind, which works but fades.

Match the effort to the risk. A small slip does not need a project. A repeated or serious problem, or one that could harm someone or break a law, does.

Check that it worked

Set the check date when you set the action. Choose a date far enough away that the problem would have appeared again if the fix did not work: one or two months for a monthly process, longer for a rare one. On that date, look at the evidence: the orders since, the complaints, the records. If the problem is gone, close the action and write down what you saw. If it is not, go back to the cause.

Close only when you have looked. "Done" and "worked" are different words.

Keep a simple record

For each problem keep a short record: the number, the date, the description, the containment, the cause, the actions with owners and dates, the check and the result. A table or a list is enough. After a few months, read the records together. Patterns show up that single cases hide: the same supplier, the same step, the same day of the week.

Corrective, preventive and improvement

You will hear three terms. Corrective action deals with a problem that has happened. Preventive action deals with a risk you can see before it happens. Improvement is making something better that was not wrong. They use the same method, so a team that is good at the first is good at the others.

Where nerix helps

In Checks (early access), a minor or major issue, or an observation, opens a numbered issue. Its corrective action is a task in Work with an owner and a due date that follow how serious it is, and an owner or the person who ran the check closes the issue only after checking that the fix worked. If a result is changed later, the issue follows it.

Outside audits, you can use Work for any problem the same way: a task for each action, owners, dates and a check task on the date. In the chat you can paste your notes and ask nerix to help with the why questions, to suggest what else to check or to draft the message to the customer. It can ask good questions. It does not know your process, so the answers must come from the people who do the work.

The short version

Describe the facts. Put the customer right today. Ask why until you reach something you can change. Choose a few specific actions with owners and dates, prefer changes that prevent the mistake over reminders, and check later that it worked.