A3 Report Case Study Analysis —— The Complete Path from On-site Challenges to Project Closure

1. A Quality Incident That Made Management Uncomfortable

In the first week after the Spring Festival in 2026, the injection molding workshop of a home appliance manufacturing company (hereinafter referred to as "the company") was thrown into turmoil by a single piece of data: the shrinkage defect rate of the A model panel, which had been consistently stable at 1.2%, soared to 7.8%, and on the worst day, it exceeded 10%. Shrinkage is one of the most common defects in injection molded parts, characterized by凹陷或收缩痕迹 on the surface of the product, directly affecting the appearance rating. This particular panel is the most scrutinized appearance component during customer inspection.

After the issue erupted, the workshop initially handled it using the old methods: machine operators took turns adjusting the material temperature, mold temperature, and injection pressure, but after three days of effort, the defect rate fluctuated between 4% and 9%, never returning to normal levels. Even more critical, the good products selected for rework and delivered to the customer were found to have shrinkage defects during incoming inspection, leading to a formal complaint being sent directly to the general manager's office.

The general manager decided at the quality meeting: a cross-departmental task force would be formed, led by the quality department, to provide conclusions within two weeks and reduce the defect rate to below 2% within one month. Quality Engineer Xiao Zhou was appointed as the project leader. His first action was not to rush into adjusting parameters but to pull out an A3 paper from his drawer—using one page to clearly explain and solve the problem. This is the case we will analyze in detail: how an A3 report transforms an on-site issue that seems solvable by machine adjustment into a systematic project improvement.

2. Background and Current Status: Pinning the Problem on a Single Page

The first step in an A3 report is to clearly state "why this action is necessary." In the "Background" section of the A3, Xiao Zhou wrote only three lines: the shrinkage defect rate of the A model panel increased from 1.2% to 7.8%, exceeding the specification limit; one customer complaint, with a risk of production line shutdown; estimated monthly loss of about 60,000 yuan, including scrap, rework, and customer claims.

The purpose of writing the background is to answer "what would happen if we don't act." Many improvement projects fail at the first step because the background is vague, such as "improve quality" or "enhance appearance," which do not convey urgency. By including the loss amount and customer complaint, Xiao Zhou made the project's priority clear, providing a basis for requesting personnel, resources, and equipment downtime.

Next comes the current status analysis. This is the most challenging and critical part of the entire A3 report. Instead of sitting in his office and reviewing reports, Xiao Zhou took a stratification form to the site, retrieving the defective products and shift records from the past two weeks, and stratifying them by four dimensions:

• By machine: the defect rate for Machine No. 8 was as high as 12.3%, while the rates for other machines were below 2%.
• By shift: the defect rate for the night shift was three times that of the day shift.
• By mold: the defects were concentrated in Mold No. 1.
• By raw material batch: no significant differences were observed.

After cross-stratifying the data, the issue clearly pointed to the combination of "Machine No. 8 + Night Shift + Mold No. 1."

Xiao Zhou spent two night shifts at the site and discovered a previously unnoticed detail: night shift operators, in an effort to meet production targets, had reduced the cooling time from the specified 28 seconds to 20 seconds. The mold was not fully cooled before it was opened, causing the product to continue contracting after demolding, resulting in shrinkage marks on the surface. Stratification data identified "where the problem lies," and on-site observation revealed "what people were doing when the problem occurred," making the current status more comprehensive.

3. Goal Setting: Good Goals Should Be "Just Out of Reach"

After clearly understanding the current status, the third step in the A3 report is to set goals. After discussions with the team, Xiao Zhou wrote: within one month, reduce the shrinkage defect rate of the A model panel from 7.8% to below 2%, and maintain stability for two consecutive weeks; simultaneously, eliminate the unauthorized adjustment of cooling time during the night shift.

This goal has two key aspects. First, it is measurable; the defect rate is a clear statistical metric, and the success of the project will be determined by data, not vague statements like "significant improvement." Second, it is phased; Xiao Zhou did not directly set the goal to "0.5%," as achieving it in one step is unrealistic and could lead to fabricated data under pressure. Reducing the defect rate from 7.8% to below 2% is achievable based on the current analysis, but it requires genuine effort, making it a goal that is "just out of reach."

Another often overlooked aspect of the goal section is that it serves as the "acceptance contract" for the A3 report. At the end of the project, managers will check each item against the goals to determine if the project is closed. Many A3 reports fail to maintain their goals and end up as "work summaries," which often stems from not establishing a clear goal at this step.

4. Root Cause Analysis: Five Whys Turn a "Machine Adjustment Issue" into a "Management Issue"

The current status pointed to the compression of cooling time, and the surface cause seemed clear. However, Xiao Zhou did not stop there. In the root cause section of the A3, he used a combination of a fishbone diagram and the 5 Whys method to delve deeper into the issue.

The fishbone diagram expanded from five angles: personnel, machine, material, method, and environment:

• Personnel: night shift operators lacked experience and were insensitive to shrinkage defects.
• Machine: Machine No. 8's cooling timer lacked an alarm function.
• Method: the standard work instruction specified a cooling time of "28 seconds" but did not explicitly state "no unauthorized adjustments."
• Management: the night shift lacked process discipline inspections.

After expanding, Xiao Zhou asked five consecutive whys for the most suspicious chain:

1. Why was the cooling time reduced to 20 seconds? Answer: to meet the shift production target.
2. Why did they dare to reduce the cooling time? Answer: because no one noticed, and no one verified the process parameters.
3. Why did no one verify the parameters? Answer: because the night shift had no process inspections, and quality inspectors only checked the appearance of the finished products.
4. Why did quality inspectors only check the appearance and not the parameters? Answer: because the inspection procedure only defined appearance sampling and did not include parameter verification.
5. Why was parameter verification not included in the procedure? Answer: because when the procedure was initially compiled, it was assumed that the parameters would be automatically guaranteed by the equipment, and no one considered the possibility of manual intervention.

After five whys, the nature of the problem changed: it was not just an "individual issue" of operators being lazy, but a "systemic issue" resulting from three management loopholes—"no parameter monitoring, no night shift inspections, and no parameter verification in the procedure." Simply restoring the cooling time to 28 seconds would not solve the problem if the production pressure remained, as the parameters would eventually be adjusted again. The root cause analysis in the A3 report aims to penetrate from the surface to the underlying mechanisms.

5. Countermeasure Development: Addressing Each Root Cause Individually, Not in a Haphazard Manner

With the root causes clear, the countermeasures followed logically. The A3 report requires each countermeasure to correspond to a specific root cause, not to be listed arbitrarily without analysis. Xiao Zhou's team developed four countermeasures:

Countermeasure 1, addressing "no parameter monitoring": install a cooling timer and real-time mold temperature display on Machine No. 8. If the cooling time falls below the set value, a sound and light alarm will be triggered and recorded in the MES system. This is a technical poka-yoke, ensuring that "reducing time" becomes "inevitably detected."

Countermeasure 2, addressing "no night shift inspections": establish a night shift process discipline inspection system, where the shift supervisor verifies key process parameters every two hours, and the inspection results are photographed and uploaded. The quality department reviews the results at the morning meeting the next day.

Countermeasure 3, addressing "no parameter verification in the procedure": revise the inspection procedure to include a "cooling time parameter verification" item in the first article inspection. If the parameters do not match, the product is deemed nonconforming and not allowed to proceed to the next process.

Countermeasure 4, addressing "inexperienced operators": conduct specialized training for night shift operators on shrinkage defect identification and standard operations, and include the prohibition of unauthorized cooling time adjustments in the job red line, with violations affecting performance evaluations.

Each of the four countermeasures targets a specific root cause, forming a chain of actions: the alarm system prevents "whether time can be reduced," the inspection system prevents "whether time will be reduced," the inspection procedure prevents "whether reduced time will flow through," and training and evaluation address "whether operators know not to reduce time." Xiao Zhou also specified the responsible person, completion deadline, and verification method for each countermeasure, which is a fundamental requirement of the A3 countermeasure section—countermeasures without responsible persons and deadlines are essentially just slogans.

6. Implementation and Verification: Proving "It Really Works" with Data

The first week of implementing the countermeasures was not smooth. The alarm system was delayed in delivery, so Xiao Zhou coordinated with the equipment department to use a temporary timer. For the first two days of the night shift inspections, the shift supervisors felt burdened by the additional tasks and showed clear resistance. Xiao Zhou and his quality department team followed the night shifts for two consecutive nights, accompanying the supervisors to ensure they understood "what to check, how to record, and how to handle abnormalities."

By the third week, all four machines were equipped with alarm systems, and the inspection system was running smoothly. The results began to show: the defect rate dropped from 7.8% to 3.1% in the first week, further to 1.8% in the second week, and stabilized between 0.9% and 1.4% in the following two weeks, consistently below the 2% target. Xiao Zhou plotted the daily defect rate into a trend chart and attached it to the verification section of the A3 report, using data curves rather than "it feels better" to prove the effectiveness of the improvements.

A crucial detail in the verification phase is that Xiao Zhou extended the verification period to two weeks, covering different production scenarios such as day shifts, night shifts, and weekend production changes. Many projects fail because they declare success after just three days of verification, only to see the problem re-emerge with a different shift or mold. The verification section of the A3 report must answer not just "whether the improvement is effective," but "whether the effect is stable and replicable."

7. Standardization and Horizontal Deployment: Ensuring the Improvement Lasts Beyond This Month

After confirming the effectiveness, the final step in the A3 report is standardization and prevention of recurrence. Xiao Zhou's team took three actions:

1. Update the cooling time to 28 seconds, alarm threshold, and inspection frequency in the standard work instructions and inspection procedures. All old versions were recalled and destroyed to prevent a mix of old and new versions at the site.
2. Promote the alarm system to the other five main injection molding machines in the workshop and extend the night shift process inspection system to the entire injection molding workshop, not just Machine No. 8. Horizontal deployment is the step where many A3 reports fall short, as people often lock the results in a drawer after the project is completed, allowing similar issues to reoccur in different machines or workshops. Xiao Zhou confirmed the installation of the devices and the training of personnel at each machine to ensure that the deployment was not just on paper.
3. Document this project as an internal case study and include it in the new employee training program. One month later, the defect rate stabilized at around 1.1%, the alarm system triggered 17 times, and unauthorized parameter adjustments during the night shift were eliminated. More importantly, a new rule was established in the workshop: any adjustments to process parameters must follow a change request process, and no one can make adjustments casually.

8. Reflection: Five Practical Points Exposed by This Case

After the case, let's return to the methodology level. The reason this project was successfully closed is that there are five key points worth remembering for anyone working on an A3 report:

1. Current status analysis must be done on-site, not just by reviewing reports. Stratification data narrows the scope from "the entire workshop" to "Machine No. 8 night shift," and on-site observation adds the behavioral details of "operators reducing parameters" that are not visible in the data. Data plus on-site observation forms a complete current status.
2. Root cause analysis must penetrate to the mechanism level. The surface cause is "cooling time reduced," but the true root causes are "no parameter monitoring, no night shift inspections, and no parameter verification in the procedure." Addressing only the surface causes will inevitably lead to recurrence.
3. Countermeasures must correspond to each root cause. Four countermeasures for four root causes, each clearly assigned to a responsible person with a specific deadline. An A3 report with countermeasures that do not align with root causes, no matter how well-written, is useless.
4. Verification must be extended over a longer period and cover different scenarios. Two weeks of verification, across shifts and scenarios, ensures that the effect is stable and replicable, not just a matter of luck.
5. Standardization and horizontal deployment are essential for true closure. Updating documents, extending to other machines, and documenting the project as a case study transforms a "one-month achievement" into a "long-term system."

9. Conclusion

Looking back at this case, the value of the A3 report lies not in the paper itself but in the logical process it forces the team to follow: "background—current status—goal—root cause—countermeasure—verification—standardization." Before the A3 report, the workshop relied on the experience and luck of senior operators to handle issues. With the A3 report, problem-solving becomes a replicable path, with each step based on evidence, records, and verification. When more and more projects in the company are successfully closed using the A3 report, improvement ceases to be a sporadic effort and becomes an organizational capability. This is the true power of the A3 report.

An A3 paper contains not just the problem but the complete path for the team to transition from "firefighting" to "prevention."

Knowledge code: 5.2.2

Version: v20260804

Author: Quality Think Tank

Quality Think Tank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously enhance their quality capabilities.