Problem 3 of 5 · Quality
Process, not people. We don't believe in operator error.
How well the part conforms to spec. Field failures hurt most.
From the problem to a production plan
How Phoenix approaches it
Phoenix starts with the failure in the finished product—not an assumption that the display or operator is at fault. Bring failed samples, the enclosure and bonding materials, test conditions and the failure history so engineering can define a root-cause investigation.
See how Phoenix brings engineering and supply planning together in its published client projects.
Explore Phoenix's client projectsWhat creates this problem
The root causes we see most often behind quality issues.
- Incoming inspection that samples instead of tests
- No documented process controls at the supplier
- Bond, gasket and enclosure materials never tested together
- Failures blamed on handling instead of root-caused
What the framework recommends
The sequence from Keith Mitnik's Why Change? framework for a quality problem.
- 1
Root-cause the failure in your application before accepting any corrective action
- 2
Test the display with your real bond, gasket and enclosure materials together
- 3
Require documented process controls, not sampling plans
- 4
Change the process that allowed the failure — never blame the operator
See it in practice
Signs you have this problem
- Field returns you can't explain
- Incoming inspection keeps finding defects
- Failures appear months after install
- Your supplier blames handling or the operator
How Phoenix fixes it
- Root-cause analysis on your application, not just the display
- Documented process controls under our quality system
- First-article and reliability testing before volume
- Corrective action that changes the process, not the person
How this becomes a line-down risk
Display defects rarely show up as a clean pass/fail at incoming inspection. A marginal backlight, an intermittent touch response, or a cover lens that delaminates under thermal cycling can pass initial testing and still fail in the field months later, at a point where the cost of correction is far higher than it would have been at the design or supplier-qualification stage.
Where Quality Costs Actually Hide
Cost of quality frameworks distinguish between prevention costs — incurred to avoid problems in the first place, such as establishing clear material specifications — and appraisal costs, the ongoing measuring and monitoring activities used to confirm a product conforms to spec.
Many display sourcing decisions are made on unit price alone, with little visibility into whether a supplier is actually investing in prevention and appraisal activities or simply passing inspection costs downstream to the buyer in the form of field returns.
Root Cause Analysis vs. Treating Symptoms
When a display defect does surface, the easy response is to replace the unit and move on. Root cause analysis is a systematic process for identifying the underlying cause of a problem rather than only addressing its symptom, with the explicit goal of preventing recurrence.
For a display program, that means asking whether a touch failure traces back to a controller firmware issue, an adhesive process variation, or a design tolerance — not just whether the replacement unit passed inspection.
What a Quality-First Display Partner Looks Like
A supplier that documents material specifications, maintains in-process monitoring rather than relying solely on final inspection, and can walk through a root cause investigation when something does go wrong is making a materially different quality commitment than one offering only a lowest-price quote.
Use your Phoenix Display engineering discussion to agree on acceptance criteria, qualification evidence, inspection scope, and how a recurring defect would be investigated. Confirm these requirements for the specific display and production program.
Bring these checks to your engineering review
- Ask your display supplier to describe their documented material specifications, not just their final test procedure.
- Confirm whether appraisal activities happen only at final inspection or throughout the manufacturing process.
- Request the root cause for any past field failure, not just a replacement unit.
- Review whether failure data from returned units is tracked and fed back into design or process changes.
Questions from manufacturing teams
What is the difference between prevention and appraisal costs in display quality?
Prevention costs are spent up front to avoid defects, such as defining clear material and process specifications. Appraisal costs are spent to measure and monitor whether products already meet those specifications, typically through inspection and testing.
Why does root cause analysis matter more than simply replacing a defective display?
Replacement addresses a single unit; root cause analysis addresses the underlying cause so the same defect does not recur across future production, which matters significantly more at volume.
Research & further reading
A few quick questions about your quality problem.
Answer them and we'll connect you with a sales engineer. Reply within 24 hours.
Question 1 of 5
What quality issue are you seeing?
Keep learning · Performance
Does meeting the spec mean meeting the need?
Quality asks whether the display meets its specification. Performance asks whether that specification is right for your users.
Learn about performanceReady to discuss your program?
Bring the requirements. Start a conversation.
Share your display, application and production schedule with Phoenix's engineering team.
Contact usPlanning a new product? Review fit, interface, readability and lifecycle before the design is locked.
Plan your display design