| | June 20168CIOReviewAdrian O'LearyEffective quality control is essential to creating products that customers love and trust. As the last line of defense before a product arrives in a customer's home or business, quality control teams have the responsibility to ensure that products and services deliver as advertised. But the traditional testing paradigm limits the effectiveness of testing, by involving quality control only after key decisions have been made. At their best, quality control teams should be acting as customer advocacy organizations within companies, but to reach that point, we must evolve past a static paradigm and into an approach where we are conducting true end-to-end quality engineering. The difference between quality engineering and traditional quality control is fundamental and structural. At its most basic, this approach requires quality control organizations to get involved in product development cycles far earlier than they have in the past, and to stay involved long after products are tested and shipped. It's still important to ensure that products meet specifications, but if we can have quality engineers in the room when those specifications are being set, and learn from our customers' experiences with previous products, our input to the development process can be significantly more informed and meaningful.By Adrian O'Leary, SVP of Test & End to End Quality, Comcast Cable Evolving From Quality Control to Quality EngineeringIN MY OPINIONThe difference between quality engineering and traditional quality control is fundamental and structural
< Page 7 | Page 9 >