Quality by Design
Shared Quality Ownership
Summary
Quality is a shared responsibility across the people who define, build, test, release, operate, and support a product or service.
Reasoning
Quality is weakened when it is treated as the responsibility of QA alone. Requirements, design, implementation, release, and operational decisions each affect whether a product meets the needs of its users and remains safe, reliable, secure, accessible, and maintainable.
Shared ownership gives each contributor responsibility for the quality consequences of their decisions. QA provides specialist assurance and an independent perspective, while product, business, engineering, delivery, operations, and vendors remain accountable for quality within their own work.
Implemented By These Standards
Shift-Left Quality Involvement
Summary
QA contributes from discovery and design onward so quality risks, expected outcomes, testability, data, environments, and evidence needs are addressed before implementation decisions become costly to change.
Reasoning
When QA is involved only after implementation, unclear outcomes and design constraints can first become visible during test execution. At that stage, correcting an untestable design, missing control, unsuitable environment, or misunderstood requirement can require substantial rework and delay.
Early QA involvement brings questions about risk and verification into decisions while options remain open. It complements the expertise of product, business, engineering, security, operations, and other specialists without transferring ownership of their decisions to QA.
Implemented By These Standards
Quality Failure Prevention
Summary
Preventive design and development are a major source of product and service quality, and QA validates their effectiveness and identifies where they can improve.
Reasoning
Quality is created through requirements, design, implementation, configuration, and operational decisions before formal testing begins. Clear contracts, appropriate controls, reviewable designs, and early engineering checks prevent avoidable failures and make remaining problems less costly to correct.
QA uses testing, findings, trends, and operational evidence to evaluate how effectively these preventive practices work. It identifies gaps and opportunities for improvement, while the people responsible for product, design, engineering, and operations remain accountable for deciding and implementing the appropriate changes.
Implemented By These Standards
End-to-End Quality Outcomes
Summary
Quality covers the complete user or service outcome across every component, team, and organisation involved.
Reasoning
A product or service can work correctly in separate parts but still fail when those parts work together. Differences in interfaces, data, dependencies, timing, or responsibilities can prevent the expected outcome from being achieved.
Teams define complete outcomes early and consider every part involved. Assurance verifies the individual parts and their combined behaviour so gaps between them remain visible.