Juran’s Quality by Design

Security is a quality outcome — and should be built that way.

In 1986, J.M. Juran presented the Quality Trilogy, a model for building better products:

Quality Planning: define what security means for your product

Quality Control: monitor whether processes meet those goals

Quality Improvement: continuously analyze failures and near misses

Fun fact: Juran also popularized the Pareto Principle in quality control in the 1940s.

Discussion prompts

• How would you map Juran's Quality Trilogy to your software development process?
• Does your organization treat a critical security defect the same way it treats a critical quality defect?
• What near misses in your codebase have you analyzed to improve your process?