Training video 7 of 21 · Improve
Corrective actions and 8D
From the first report to proof that the fix worked.
3:20 · captions in English
Chapters
Transcript
Introduction
When a problem matters, you need more than a quick fix. You need to understand why it happened and make sure it can't happen again. Doctilla runs corrective actions through the eight disciplines, known as eight D. In this video, we'll follow one from start to finish.
The CAR register
Corrective action requests, or CARs, live here. You can filter by status, owner, process or department. The trends tab shows how many you're opening and closing, the processes they come from, and the root causes behind them, so you can see whether the same kind of problem keeps coming back.
Agreeing a proposed CAR
A CAR raised from a family of nonconformities, or by the API, starts as a proposal. It isn't counted as open until someone agrees it. Review the summary, and choose agree CAR to start the work, or delete the proposal if it isn't needed.
The eight disciplines
Here's a CAR in progress: low free expansion on a fire seal. Across the top are the steps, D zero to D eight. A tick means the step is complete. On the right is the summary, with the process it belongs to, the target date, and everything linked to it.
Team, problem and containment
The first steps set it up. D one names the team. D two describes the problem in measurable terms: what, where, when and how much. D three records the containment, the actions that protect the customer straight away, such as quarantining the batches and testing every reel.
Root cause: 5 Whys
D four is root cause. With five whys, you keep asking why until you reach something you can actually fix. Stuck? Ask Doctilla for the next why. It suggests one, and you apply it or dismiss it. It never writes into your analysis without you choosing to.
Other root-cause tools
There are other tools for other problems: an Ishikawa fishbone for causes across people, machines, methods and materials, TRIZ prompts, and cause and effect. Then write the root cause in one sentence, and, just as important, why your checks didn't catch it.
Guidance on each step
On every step, ask for guidance and Doctilla reviews what you've written so far. It points out gaps, asks the questions an auditor would ask, and makes suggestions you can apply or dismiss one by one. All of it is kept in the CAR's conversation, so there's a record of the advice and what you did with it.
Corrective actions
D five is where you fix the cause. Each corrective action has an owner and a due date, and goes on their list. Notice the action for the escape, changing the test method so a failure is investigated before any re-test. That's the one most often forgotten.
Proving it worked
D six asks the question that matters: did it work? Set up an effectiveness check, saying what you'll measure and when. When the time comes, a person records the result, with the evidence. Doctilla never decides a fix worked on its own.
Prevention and closing
D seven stops it happening elsewhere: which other processes and documents need to change. And D eight closes the CAR, with lessons learned and thanks to the team. Doctilla won't close a CAR until every step is complete.
Next
That's corrective actions. Next, we'll look at actions and reminders, and how Doctilla makes sure nothing is forgotten.
See Doctilla with your own processes
Book a 30-minute demo. We'll walk through the parts that matter to you, using a fully populated demonstration company, and answer anything you want to ask.