Failures happen. Sometimes product failures happen quickly.
You just bought a new feature rich computer and discover it doesn’t work. Right out of the box, it will not power up. Conversations with the tech support and it’s a trip back to the store.
The failures that occur early the in the life of a product tend —
this ‘tend’ really is just a vague ‘in general’
…tend to occur because of manufacturing errors or shipping/installation damage.
Not always, though.
The Delta Program
Years ago a company was struggling in the market. The product reliability was not very good compared to the competition and the market knew this and bought accordingly. The product design team worked to bring out a new product with many reliability enhancements.
Yet, they did not know if that would be good enough. So they focused a small part of the core design team on the first few months of field returns. Once they went into production and started selling units, this team received nearly all of the reported field failures.
The intent of the Delta program was to keep a team of development engineers on the program even after it had been released to the market. The common practice was to move the engineers to the next development project.
The mandate for the Delta program was to find design errors and implement immediate design improvements.
They found power supplies that were not robust- inadequate electronic filtering, underpowered fans, and many other design flaws.
The result in less than two months from the initial shipment was a reduction of the field failure rate by over 50%, which then continued to decline with the normal process and design improvements.
Added benefit of the Delta Program
The company previous would work to improve the design and process as they discovered flaws. It took time for the manufacturing and new product introduction engineers to learn the details of the new product. It took time to consider and evaluate the suitability of solutions. They had reviews and a detailed approval process. Plus they generally rolled out improvements after the current inventory of components was consumed.
The Delta Program eliminated delays. They did some experimentation and evaluations. Did very quick reviews and implemented changes resulting in the rework of existing in-house inventory and scrapped components being replaced.
They shorten the time to field failure reduction. In other words, they cut the monthly warranty expense in half 6 months sooner than previous programs.
One more benefit of the Delta Program
The entire engineering team wanted to be on the next Delta Program. It was a fun and important (highly visible) position. The engineers on the team were recognized as product design experts within the organization and given the trust to implement significant changes to an existing design.
It was a fun and important (highly visible) position. The engineers on the team were recognized as product design experts within the organization and given the trust to implement significant changes to an existing design.
Plus they learned a lot. They learned about product failures first hand. They got to conduct extensive failure analysis and talk to customers. They improved their design skills dramatically, becoming even more valuable to the organization.
Notes on implementing the Delta Program
- Select a small team representing the major elements of the product. They have to know the product. They need to know the theory of operation and how it actually works.
- Get products back quickly. An overnight shipment is expensive, and not compared to the avoided cost of 100 other field failures. If possible have the team attend the installation of the product.
- Give the team the tools to conduct detailed failure analysis. They need the equipment and skills to do chemical, thermal, vibration, etc. analysis quickly. If the failure analysis lab and technicians are not in house, establish a close relationship with a nearby lab. Remove the barriers to permit quick results.
- Streamline the design review process. It is worth reviewing changes and considering all the impacts. Yet it can and should be the same day the proposed changes occur. Again, dedicate the people to make this happen.
- At the start of production, any detected and unresolved issue the leads to field failures costs money and customer satisfaction.
Yes, the product should not have early field failures. It happens. There are just too many elements and consideration and unknowns to get the design perfect every time. A Delta Program pays for itself quickly and is worth adding to your next project.
Field Data and Reliability (article)
When to Take Action on Field Failure Data (article)
Failure Analysis: The Key to Learning from Failure (article)
Gene Danneman says
The Delta team is a great concept. In the continuous process industry, plant startups expose an amazing amount of design errors and early equipment failures that must be swiftly addressed to assure plant safety, environmental protection, reliability, production schedule and minimize financial risks. As a member of the team, expect long hours, lots of customer feedback, and being able to see and feel the results of effective problem solving. Root cause analysis, problem solving analysis and an effective failure reporting and corrective action program are critical.
Fred Schenkelberg says
Took a while to respond to your excellent comment. Thanks for the comment which seems based on personal experience. You know how important it is to quickly address any issues so you can avoid other problems later. It’s an investment, yet well worth it.