During product development, we're consistently looking for ways to learn more about the product in order to make design decisions. Some of that comes from test.
What do we do when our test results are...surprising?
We talk about some next steps I typically take when tasked with surprises.
Some steps to get us started after surprising test results: what did we learn?
- Revisiting the purpose. Did we answer the question we originally started with, or no?
- Understanding failure modes at test vs. what we expected. We can go back to our definition of a failure mode from requirements and our FMEAs (failure mode and effects analyses). How do our test results compare to those? What have we learned?
- Finding a root cause by following a process, with the help of FMEA causes - things we thought could cause the failure mode. Does it match? What has changed?
- Deciding what to do next, depending on where we are in the development process. We also refer back to the FMEA with an update to it based on our test results. Has our risk analysis changed? Has our concluding risk statement changed? We may find that it has, in which case we need to assess what to do about that with our team. If we've identified a new risk, we can work to eliminate or control it.
Other Quality during Design podcast episodes you might like: