A3 problem solving: one page for the line and for management.
An A3 report is one page that holds the whole story of a problem: the description with baseline and target, the root cause, the countermeasures, the check and the follow-up. In SolveR the A3 is the result of the case on one page that the line and management both read, and nobody writes the report twice.
When to use A3, and when not to
You pick A3 when management needs to understand the problem. One engineer owns the problem for several weeks, with a mentor alongside, and at the end management sees on one page where the problem came from, what the team found and whether the countermeasures hold. The method comes from Toyota and is built on PDCA thinking, and it takes its name from the A3 paper format.
Example: scrap at a welding step on a plastic housing, today and with SolveR
A typical case: scrap at a welding step on a plastic housing, with cracks that show only in the leak test.
| Today | With SolveR |
|---|---|
| The team fixes first and fills in the A3 sheet just for the meeting. The page reports, and nobody learns from it. | Problem: scrap has gone up, the cracks show in the leak test, mostly on Mondays on the first shift. The baseline comes from the daily scrap log, and the target has a date. |
| The baseline sits in one cell and the target in another, and the chart is redrawn for the management meeting. The story drifts between versions. | Cause: moisture in the granulate, because drying after a bag is opened was never prescribed. It is verified on several batches. |
| The Ishikawa lists factors, the 5 Why stops at a symptom, and the countermeasures start anyway. | Countermeasures: a drying rule with a moisture record, a parameter table and a moisture meter on the line as poka-yoke. |
| The check stops at the action being implemented. | Check: scrap stays below target for several weeks in a row. The drying rule goes into the process sheet, and the follow-up runs on after closure. |
At the meeting we show it on one of your own cases.
What you get: one page for the line and for management
One A3 page with the whole story of the case: the problem with baseline and target, the cause with its verification, the countermeasures, the check before and after, and the follow-up. Management reads it in one go, and the line sees the same page. The engineer does not write the report twice, once for the work and once for the meeting.
What SolveR does
It suggests causes and countermeasures from your plant's closed cases, including cases solved in 8D or another method, and shows the source of each suggestion. The engineer who owns the problem decides.
Steps: problem, cause, countermeasures, check, track
- 1ProblemBaseline, target and data source
- 2CauseThe root cause, verified
- 3CountermeasuresActions on the confirmed cause
- 4CheckBefore and after, against the target
- 5TrackWhether the result still holds later
A countermeasure starts only once the cause is verified. An action on a cause that is merely possible is a common A3 trap.
One knowledge base: the next A3 starts from what the plant has already confirmed
A closed A3 stays in the knowledge base with its confirmed cause, countermeasures and check, even after the engineer who led it has moved on. The next time someone describes a similar problem, this case comes up, even if it was solved in an 8D or another method back then. The next A3 starts from the causes and actions the plant has already confirmed.
Every method writes into the same base. You can also ask Brain. The How it Works page shows what goes into the base and what comes out.
Questions about the A3 report
What is the difference between an A3 report and an 8D report?
An 8D report answers a customer on a complaint, a safety issue or a recurrence: a team works through the steps D0 to D8, and the customer gets the whole answer in one document. An A3 report is one page for internal use, when management needs to understand the problem, with one owner and a mentor. Both methods look for the root cause and check that the actions work.
When is an A3 not the right tool?
When the fix is obvious, Just-Do-It is enough. Internal scrap that the engineer closes alone goes into 4-Step. A customer complaint calls for an 8D, and a team improvement in one area for Kaizen.
Does a digital A3 report still fit on one page?
Yes. The result of the case is one page that management reads in one go. The details, such as measurements, the cause analysis and the evidence of the check, stay in the case and in the knowledge base, and the page holds what management needs to see.
How do you check that a countermeasure really holds?
The check compares the values after the countermeasure with the baseline and the target set at the start, for long enough to show whether the result holds. An A3 closes when the actual results meet the target, and the follow-up shows whether they still hold later. Practitioners name closing an A3 before the results are confirmed as a common mistake, because an implemented action and an effective one are not the same thing.
Who writes the A3 report and who reads it?
The engineer who owns the problem writes it, with a mentor alongside, usually the quality manager or an outside consultant. The line and management read it. Where plants would like to introduce A3, we hear that nobody knows the method well enough and there is no time for it. In SolveR the engineer gets the A3 page as the result of the case and does not write it separately.
Other methods
Every team picks the method that fits the problem, and one knowledge base stands behind all of them.
Bring a problem that management needs to understand to the call.