The best time is at the product conception. The second best time as early as possible in the product development process.
It may change. Be refined. Altered later.
That is fine, yet the initial concept needs the boundary condition of a reliability goal. Continue reading
By the time a product fails in the field, the design team is focused on the next design.
They are looking to the future and not looking for field reliability feedback. We know that each failure contains valuable information.
We, as reliability professionals, often work to create as much useful information concerning failure modes and mechanisms as possible. We want to improve the design. Continue reading
Not much. You need just enough field failure data to identify the root cause and determine if and how to resolve the problem.
Field data will accumulate even if your program works diligently to prevent failures.
The actions taken before the reported failure will frame when you need to take action. Continue reading
During the design phase, we make decisions that create the eventual reliability performance of a product.
It is the decisions we make that matter.
Also during the design phase, we explore numerous questions.
One of my favorite things to do when visiting a new company, it at lunch or during a break, ask:
“Any major disasters that impacted reliability?”
Typically, there are three stories that start with, “Remember the… “, or, “One time…”
It seems every organization has legendary stories in the organizational memory. Continue reading