Quality Function Deployment
Also known as: QFD, House of Quality
Translates customer requirements into engineering specifications via matrix analysis.
Quality Function Deployment (QFD) is the systematic methodology for translating customer requirements into engineering specifications and design decisions through structured matrix analysis, with the iconic 'House of Quality' matrix as central analytical tool. The framework was developed by Yoji Akao at Mitsubishi Heavy Industries' Kobe shipyard from 1966 onward and substantially codified through Akao and Shigeru Mizuno's 1978 book Hinshitsu Tenkai (Quality Deployment, with English translation 1994). QFD's substantial Japanese quality-engineering context — emerging alongside TQM and other quality tools — shaped its commitments to systematic, data-driven translation between customer voice and engineering practice. The House of Quality matrix combines: (1) WHATs — customer requirements (the 'voice of the customer'); (2) HOWs — engineering characteristics that affect those requirements; (3) WHAT-HOW relationships — strength of relationship between each requirement and each characteristic; (4) HOW-HOW correlations — relationships among engineering characteristics ('roof' of the house showing trade-offs and synergies); (5) Importance ratings of customer requirements; (6) Competitive analysis (how the product compares to competitors on each requirement); (7) Target values for engineering characteristics. The framework substantially extends through cascading matrices — House of Quality drives subsequent matrices for parts deployment, process planning, production planning. QFD has been substantially adopted in automotive (Toyota, Ford), aerospace, electronics, and other manufacturing industries, with substantial application in service-design and software-development contexts. Critics note that House of Quality matrices can become bureaucratic exercises that don't substantively drive design decisions, that the substantial methodological apparatus is genuinely demanding without proportional payoff in many applications, and that contemporary user-centered design and agile methodologies provide substantively different (and often more practical) approaches to translating customer needs into design decisions.
Core components
- House of Quality matrix combining customer requirements (WHATs) and engineering characteristics (HOWs)
- WHAT-HOW relationships and HOW-HOW correlations
- Importance ratings and competitive analysis
- Target values for engineering characteristics
- Cascading matrices for parts, process, production planning
- Foundation in Japanese quality-engineering tradition
- Substantial automotive, aerospace, electronics adoption
- Distinction from purely intuitive translation between customer needs and engineering
- Connection to broader TQM tradition
Primary use case
Foundation of systematic customer-requirements-to-engineering translation in manufacturing; basis for substantial work in automotive, aerospace, electronics product development; reference framework in quality-engineering and product-development education; foundation for substantial commercial QFD-consulting practice; integration with broader TQM and Six Sigma methodology; pedagogical foundation in engineering and management curricula; influence on user-centered design and software requirements engineering; foundation for some commercial software-requirements tools.
Common criticisms
- House of Quality matrices can become bureaucratic exercises that don't substantively drive design decisions — the substantial apparatus produces detailed documentation that may not substantively influence engineering choices
- the substantial methodological complexity creates substantial learning curve and time investment that may exceed practical payoff for many product-development contexts
- commercial QFD consulting has substantial financial stake in framework adoption that may shape evidence about effectiveness
- contemporary user-centered design and agile methodologies provide substantively different (and often more practical) approaches to translating customer needs into design decisions
- cross-cultural application of Japanese-developed framework has uneven results — QFD's emphasis on systematic deliberation and consensus-building reflects particular organizational culture that doesn't transfer cleanly
- integration with rapid product development and continuous deployment is genuinely difficult — QFD's substantial upfront analysis fits poorly with iterative design approaches
- tendency for QFD adoption to be compliance-style — organizations produce required matrices without substantive analytical use
- the framework works better for hardware product development with substantial design-locked phases than for software, services, or rapidly iterating products
- voice-of-the-customer capture often involves substantial methodological choice (which customers? which requirements? how to weight?) that the framework doesn't fully address
- integration with quantitative customer-satisfaction data and market research is incomplete in many implementations.
Lineage
- Siblings
- Robust Design, Poka-Yoke