Study guide

10.4 Quality Function Deployment & the House of Quality

Certified Quality Improvement Associate CQIA

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction to CQIA & Exam Overview

1.1 About the ASQ CQIA Exam 1.2 How to Use This Study Guide & CQIA Exam Strategy 1.3 Quality Fundamentals & Historical Evolution

2 Chapter 2: Quality Basics & Management Philosophies

2.1 Core Quality Concepts, Terminology & Definitions 2.2 Quality Pioneers: Deming, Juran & Crosby 2.3 Additional Quality Pioneers: Ishikawa, Shewhart, Feigenbaum & Taguchi 2.4 Benefits of Quality & Organizational Impact 2.5 Employee Involvement, Empowerment & Organizational Culture

3 Chapter 3: Quality Systems, Standards & Cost of Quality

3.1 Quality Management Systems & ISO Standards 3.2 Baldrige Award & Quality Excellence Frameworks 3.3 Cost of Quality (COQ) & The PAF Model 3.4 The Quality Plan: Purpose, Content & Ownership 3.5 Internal Audits as an Improvement Technique

4 Chapter 4: Teams, Roles & Formation

4.1 Team Types, Purpose & Team Charters 4.2 Team Roles, Member Responsibilities & Sponsorship 4.3 Bruce Tuckman's Stages of Team Development 4.4 Initiating Teams & Selecting Team Members

5 Chapter 5: Team Dynamics, Facilitation & Decision-Making

5.1 Meeting Management, Facilitation & Communication 5.2 Decision-Making & Consensus Tools 5.3 Conflict Resolution & Overcoming Team Roadblocks

6 Chapter 6: Continuous Improvement Frameworks & Lean Six Sigma

6.1 Continuous Improvement Cycles: PDCA, PDSA & DMAIC 6.2 Lean Principles, Kaizen & The 8 Wastes (Muda) 6.3 Problem-Solving Methodologies & Root Cause Analysis 6.4 Pull Systems, Kanban, JIT & Setup/Cycle-Time Reduction 6.5 Benchmarking

7 Chapter 7: The 7 Basic Quality Tools

7.1 Process Flowcharts & SIPOC Diagrams 7.2 Check Sheets, Histograms & Pareto Analysis 7.3 Cause-and-Effect (Ishikawa) Diagrams & Scatter Plots 7.4 Statistical Process Control (SPC) & Run Charts

8 Chapter 8: Additional Process Improvement Tools

8.1 Affinity, Tree, Matrix & Process Decision Program Charts 8.2 Error-Proofing (Poka-Yoke), 5S & Standard Work 8.3 Process Capability Basics (Cp & Cpk) 8.4 Decision Trees & Expected Value Analysis 8.5 Risk Management: FMEA, SWOT & Risk-Based Prioritization

9 Chapter 9: Data Collection, Measurement & Basic Statistics

9.1 Data Types, Measurement Scales & Sampling Techniques 9.2 Descriptive Statistics & Measures of Variation 9.3 Data Integrity, Verification & Visual Presentation

10 Chapter 10: Customer Relations & Voice of the Customer

10.1 Customer Identification: Internal vs. External Stakeholders 10.2 Voice of the Customer (VOC) & The Kano Model 10.3 Customer Satisfaction, Feedback & Retention 10.4 Quality Function Deployment & the House of Quality

11 Chapter 11: Supplier Relations & Supply Chain Quality

11.1 Supplier Identification & Strategic Partnerships 11.2 Supplier Selection, Evaluation & Rating Systems 11.3 Incoming Quality Control, Audits & Supplier Continuous Improvement

10.4 Quality Function Deployment & the House of Quality

Key Takeaways Explain This Topic AI

Quality function deployment translates customer needs stated in the customer's own words into measurable technical requirements, and prioritizes those requirements by customer importance.

The House of Quality is QFD's first matrix: customer requirements (the Whats) on the left, technical requirements (the Hows) across the top, and a relationship matrix connecting them.

Relationships are conventionally weighted 9 for strong, 3 for moderate, and 1 for weak; multiplying each weight by the customer importance rating and summing down a column gives that technical requirement's priority.

The roof of the house records correlations among technical requirements, and negative correlations expose the design trade-offs that must be resolved deliberately.

In the four-phase model the Hows of one matrix become the Whats of the next, carrying the customer's voice from product planning through design, process planning, and production control.

Last updated: September 2026

10.4 Quality Function Deployment & the House of Quality

Body of Knowledge entry V.B.3 (Customer needs) states: understand the key elements of quality function deployment (QFD) and how it identifies and prioritizes customer expectations and needs. Customer Relationship is only 7 scored questions, and QFD is one of its four entries — so this is worth roughly one to two items, and it is a topic candidates routinely skip.

1. Purpose

Quality function deployment (QFD) is a structured method for translating the voice of the customer into measurable technical requirements , and for prioritizing those requirements according to what customers actually value.

It solves a specific and expensive problem. Customers express needs in their own language — "the door should feel solid," "the software should be easy to learn," "the coffee should stay hot." Engineers can only act on measurable characteristics — closing force in newtons, time-to-first-successful-task in minutes, temperature retention in degrees per fifteen minutes. Without a disciplined translation, one of two failures occurs: engineers optimize what is easy to measure rather than what customers value, or design decisions are made by whoever argues most persuasively in the meeting.

QFD was developed by Yoji Akao in Japan in the mid-1960s, with its first large-scale application at the Mitsubishi Heavy Industries Kobe shipyard in 1972. It reached Western industry through the automotive sector in the 1980s.

2. The House of Quality

The House of Quality (HOQ) is QFD's first and best-known matrix, named for the roof-shaped correlation triangle on top. Its rooms: +-------------+

  • | ROOF | Correlations among the HOWs
  • | (trade-offs)| (+ synergy / - conflict)
  • +-------+-------------+-------+
  • | HOWs (technical |
  • | requirements) |
  • +-------+------------------------------+--------+
  • | WHATs | | Customer|
  • | + | RELATIONSHIP MATRIX | compet. |
  • | Imp. | (9 / 3 / 1) | assess. |
  • +-------+------------------------------+--------+
  • | Technical priorities, |
  • | targets, benchmarks |
  • +------------------------------+

Room Content

Left wall — the WHATs Customer requirements in the customer's own language, gathered from VOC work (surveys, interviews, focus groups, complaints, warranty data), usually organized with an affinity diagram

Importance ratings Each WHAT weighted, typically 1–5 or 1–10, by how much customers value it

Ceiling — the HOWs Technical or design requirements: measurable characteristics the organization can specify and control. Each carries a direction of improvement (maximize, minimize, or hit target)

  • Body — relationship matrix The strength with which each HOW affects each WHAT
  • Right wall — customer competitive assessment How customers rate us versus competitors on each WHAT
  • Roof Correlations among the HOWs themselves — where improving one helps or hurts another
  • Basement Calculated technical priorities, competitive technical benchmarks, and target values for each HOW
  • Calculating Technical Priority

Relationships are scored with the conventional weights:

  • Symbol Strength Weight
  • ● Strong 9
  • ○ Moderate 3
  • △ Weak 1
  • (blank) No relationship 0

For each technical requirement, multiply its relationship weight to each customer requirement by that requirement's importance rating, then sum down the column: Absolute importance j = ∑ i ( Customer importance i × Relationship i j ) \text{Absolute importance}_j = \sum_i (\text{Customer importance}_i \times \text{Relationship}_{ij}) Absolute importance j ​ = i ∑ ​ ( Customer importance i ​ × Relationship ij ​ )

Worked example. A HOW ("insulation R-value") relates strongly (9) to a WHAT rated 5 in importance, moderately (3) to a WHAT rated 4, and weakly (1) to a WHAT rated 2: ( 5 × 9 ) + ( 4 × 3 ) + ( 2 × 1 ) = 45 + 12 + 2 = 59 (5 \times 9) + (4 \times 3) + (2 \times 1) = 45 + 12 + 2 = \mathbf{59} ( 5 × 9 ) + ( 4 × 3 ) + ( 2 × 1 ) = 45 + 12 + 2 = 59

Ranking all columns by this score tells engineering where design effort buys the most customer-perceived value. This is the "prioritizes" half of the BoK entry , and it is the output that matters.

The non-obvious diagnostic is a blank row or a blank column :

A blank row means a customer requirement no technical characteristic addresses — the design will not deliver something customers asked for.

A blank column means a technical requirement that serves no customer requirement — effort and cost with no customer value, and a candidate for elimination.

The Roof and Design Trade-offs

The roof records how the technical requirements interact. A positive correlation means improving one helps another. A negative correlation means they conflict: increasing wall insulation raises thermal performance and increases weight and cost; tightening a manufacturing tolerance improves fit and slows cycle time.

Surfacing negative correlations is one of QFD's most valuable outputs, because these are the trade-offs that otherwise get discovered late — after tooling, when resolving them is expensive. The roof forces them into an explicit, documented decision made early.

3. The Four-Phase Model

The House of Quality is phase one. The classic four-phase deployment carries the customer's voice all the way to the production floor by a simple recursive rule: the HOWs of one matrix become the WHATs of the next.

  • Phase Matrix WHATs HOWs
  • 1 Product planning (House of Quality) Customer requirements Technical/design requirements
  • 2 Part deployment Technical requirements Part characteristics
  • 3 Process planning Part characteristics Process operations and parameters
  • 4 Process/production control planning Process parameters Control methods, inspection plans, work instructions

The payoff is traceability: by phase four, a control on the shop floor can be traced back through process parameters and part characteristics to the specific customer requirement it protects. When a control plan is questioned, QFD answers which customer need it exists to serve .

4. Benefits and Limitations

Benefits: it forces cross-functional agreement early; it makes design priorities explicit and defensible instead of political; it front-loads effort into design where change is cheap; it surfaces trade-offs and gaps that would otherwise appear late; and it creates a documented link from every control back to a customer need.

Limitations: a full four-phase deployment is time-consuming and matrices grow large quickly; the analysis is only as good as the underlying VOC data; and importance ratings are judgments that can be manipulated.

QFD and the Kano Model

The two are complements, and the exam may pair them. Kano (section 10.2) classifies requirements as must-be, one-dimensional, or attractive. QFD translates and prioritizes them. Kano feeds QFD: must-be requirements need no importance rating because their absence is disqualifying, whereas attractive requirements are systematically under-rated in direct surveys because customers do not ask for what they have not imagined. Feeding raw survey importance scores into a House of Quality without a Kano screen predictably under-weights the delighters and over-weights the expected basics.