I searched about this title and found that there is the potential for misalignment and conflict when the quality function and the R&D function are divided in two separate organizations, often with different objectives and performance measures. The danger comes when R&D folks start to see themselves as less responsible for product quality as they assume that the Quality organization exists to ensure that warranty cost and customer satisfaction goals are met. In these environments many R&D teams forget their own role in achieving quality, beginning with early system design and architecture and including daily decisions made by individual development engineers. When customer-reported quality issues occur, there’s a tendency in these businesses to blame the Quality organization for failing to detect issues or failing to effectively advocate for design changes late in the development lifecycle.