Quality Function Deployment was supposed to be the bridge between
what customers say they want and what your engineering team actually
designs. Developed in Japan in the late 1960s by Yoji Akao and Shigeru
Mizuno, it was embraced by Toyota, Mitsubishi, Ford, and a generation of
manufacturers who believed that systematic translation of customer
requirements into technical specifications would eliminate the guesswork
from product development. The tool was elegant: a matrix — the famous
“House of Quality” — that mapped customer desires against engineering
characteristics, scored relationships, correlated technical features
against each other, and produced a prioritized set of engineering
targets grounded in what the market actually valued.
For a minority of organizations, QFD still works exactly this way.
For the majority, the House of Quality has become something else
entirely: a tedious exercise completed once during a product launch,
filed in a project binder, and never referenced again. The customer
voice that was supposed to drive design decisions became a row of labels
in a spreadsheet nobody opens. The correlation matrix that was supposed
to reveal engineering tradeoffs became a grid of symbols (strong,
medium, weak) filled in by a single engineer working alone at his desk
on a Friday afternoon. And the prioritized output — those carefully
weighted technical targets — became numbers that were quietly overridden
the moment the design team ran into its first real constraint.
The story of how QFD fails is not a story about the tool. The tool is
sound. It is a story about what happens when a methodology that demands
deep cross-functional collaboration is dropped into an organization that
has no practice of deep cross-functional collaboration. The House of
Quality requires marketing to articulate customer needs with precision,
engineering to map those needs to measurable characteristics,
manufacturing to confirm producibility, and leadership to accept the
prioritization the matrix produces. When any one of those functions
disengages, the matrix stops being a decision-making tool and starts
being paperwork.
The Six Ways QFD Decays
1.
The Voice of the Customer Becomes the Voice of the Marketing
Department
The first room in the House of Quality is the customer needs section
— the WHAT. This is supposed to be filled with verbatim customer
language: the actual words real customers use when they describe what
they want from your product. Not interpreted. Not summarized. Not
translated into marketing-speak. Raw, specific, and honest.
What actually happens in most organizations is that marketing — or
whoever gets assigned the task — conducts a customer survey, runs the
responses through their own interpretive filter, and produces a list of
“customer needs” that sound suspiciously like the company’s existing
product brochure. “Customers want durability” becomes “customers want
our industry-leading construction.” “Customers want it to start reliably
in cold weather” becomes “customers want dependable performance across
environmental conditions.” The specificity that makes QFD useful is
stripped out in the name of professional presentation, and what remains
is a list of platitudes that could describe any product in the
category.
The test for whether your customer needs section is real is simple:
could a competitor’s product satisfy the need as written? If the answer
is yes, your needs are too generic. Akao himself emphasized that
customer needs should be specific enough that the engineering team can
design to them — not so abstract that they become motherhood statements
everyone nods at and nobody acts on.
The fix begins with how you collect the input. Structured customer
interviews — not surveys — produce the richest raw material. Ask
customers to describe the last time they used the product. What went
well? What frustrated them? What workaround did they invent? The
language they use in these moments is your QFD input. Record it.
Transcribe it. Use their actual words in the matrix. The moment you
paraphrase, you have replaced the customer’s voice with your own.
2.
The Engineering Characteristics Become a List of Everything
Measurable
The second room maps customer needs against engineering
characteristics — the HOW. These are supposed to be measurable,
controllable technical parameters that your design team can target: a
torque value, a surface finish specification, a cycle time, a material
hardness range. Each engineering characteristic should connect
meaningfully to at least one customer need, and the relationship between
them (strong, medium, weak, none) is what drives the prioritization.
The failure mode here is comprehensiveness without discipline.
Engineering teams, asked to list the technical characteristics relevant
to customer needs, produce a list of everything they can measure —
fifty, sixty, sometimes over a hundred parameters. The matrix balloons
to unmanageable size. The relationships become guesswork because nobody
can meaningfully evaluate sixty columns against thirty rows of customer
needs. The symbols get filled in quickly, without discussion, by whoever
drew the short straw.
The discipline of QFD is in reduction, not expansion. If your
engineering characteristics list is longer than twenty items, you have
not done the work of identifying which parameters actually matter. The
original Japanese practitioners typically worked with eight to fifteen
engineering characteristics. This forced prioritization — you could only
include the parameters that genuinely connected to customer needs. The
constraint produced clarity. The absence of constraint produces
noise.
3. The
Correlation Matrix Becomes a Guessing Game
The roof of the House of Quality — the correlation matrix — is where
engineering characteristics are evaluated against each other for synergy
and conflict. A strong positive correlation means two characteristics
reinforce each other: improving one tends to improve the other. A strong
negative correlation means a tradeoff: improving one degrades the other.
This is where QFD earns its keep, because it makes tradeoffs visible
before the design team encounters them in the prototype shop.
In practice, the correlation matrix is the most frequently skipped
or敷衍地 completed section of the entire QFD process. Engineers look at
it and either see it as redundant (they already know which parameters
conflict) or as impossible to assess without data they don’t have. So
the symbols get filled in from memory, from intuition, from whoever is
in the room. Positive correlations are overestimated because the
engineer who proposed a characteristic naturally believes it supports
everything else. Negative correlations are underestimated because nobody
wants to be the person who says “this design direction conflicts with
that one” before the design has even started.
The consequence is that tradeoffs — which are the single most
valuable output of QFD — remain invisible until they emerge as problems
during the design phase, at which point they are far more expensive to
resolve. A properly constructed correlation matrix would have revealed
the conflict at the planning stage, when alternatives could still be
evaluated without rework.
4.
The Competitive Assessment Becomes a Self-Friendly Fantasy
The right side of the House of Quality is supposed to contain an
honest assessment of how your product and your competitors’ products
perform against each customer need and each engineering characteristic.
This benchmarking data is what gives the prioritization meaning: it
tells you not just what customers value, but where you have gaps
relative to the market.
What tends to happen is that the competitive assessment is filled in
by people who have not actually tested competitor products. Scores are
assigned based on reputation, based on brochure specifications, based on
what the sales team says they hear in the field. Your own product is
rated charitably — or, if the exercise is being run by a frustrated
engineer, rated harshly to make a point. Either way, the data is
unreliable, and the competitive gaps the matrix reveals are artifacts of
bias rather than evidence of market reality.
Real competitive assessment requires structured evaluation: buying
competitor products, testing them on the same equipment, using the same
criteria, with blind scoring where feasible. This is expensive and
time-consuming, which is why most organizations skip it. But without
honest competitive data, the House of Quality is a house without
foundations — the structure stands, but it doesn’t rest on anything
real.
5.
The Prioritization Output Is Overridden on First Contact with
Reality
The entire point of building the House of Quality is to produce a
prioritized set of engineering targets — the output at the bottom of the
matrix that tells the design team where to focus. These priorities are
derived from customer importance weightings, relationship scores, and
competitive gap analysis. Done well, they represent the most
analytically defensible set of design priorities the organization can
produce.
And then the design phase starts, and the priorities are ignored.
Not maliciously. Not through conscious rejection. Through the slow
erosion that happens when cost pressure, schedule pressure, technical
feasibility constraints, and supplier limitations each chip away at the
prioritized list. The engineering characteristic that QFD ranked as most
important turns out to be expensive to achieve, and the cost reduction
meeting produces a cheaper alternative. The second priority turns out to
conflict with a regulatory requirement that wasn’t in the matrix. The
third priority gets descoped because the program timeline was
compressed. By the time the design is frozen, the QFD output has been
hollowed out so thoroughly that it bears no resemblance to the product
that emerges.
This is not necessarily a failure. Constraints are real, and QFD
cannot anticipate all of them. But the failure is in how the overrides
happen: silently, without traceability, without revisiting the customer
needs the matrix was built on. When a priority is overridden, the
question that should be asked is: “What customer need does this decision
compromise, and is that compromise acceptable?” Instead, the question
that gets asked is: “Can we get this past the program review?” The
customer disappears from the conversation at the exact moment their
needs are most at risk.
6.
QFD Becomes a One-Time Document Instead of a Living Process
The most fundamental decay is temporal. QFD was designed as a living
process — a tool that gets updated as customer needs evolve, as
competitive landscapes shift, as engineering teams learn more about the
design space. The House of Quality for a product should look different
at concept stage, at design review, and at pre-launch. Not because the
methodology changes, but because the inputs change, and the outputs
should reflect that evolution.
In most organizations, QFD is a gate document. It gets produced once
— typically at concept approval or program kickoff — checked off the
deliverables list, and archived. It is never updated. The customer needs
collected at concept stage may have been valid then, but the market has
moved. The competitive assessment reflected products that have since
been revised or replaced. The engineering characteristics were based on
assumptions that design work has since invalidated. But the document
sits unchanged, a snapshot of a moment that the program has long since
passed.
The consequence is that when a new team member joins the program and
asks “what does the customer want from this product?”, the QFD document
is either not found (because nobody remembers where it was filed) or
found and treated with suspicion (because everyone knows it’s outdated).
The institutional knowledge about customer priorities that QFD was
supposed to capture and communicate instead lives in the heads of a few
individuals, and walks out the door when they do.
What Working QFD Looks Like
Organizations that use QFD effectively share a few characteristics.
First, they treat the House of Quality as a meeting tool, not a document
tool. The matrix is built in a room with marketing, engineering,
manufacturing, and quality present — not by a single person at a desk.
The discussions that happen while filling in the cells are more valuable
than the completed matrix itself, because those discussions surface
assumptions, disagreements, and gaps that would otherwise remain hidden
until they become problems.
Second, they limit scope. A focused QFD on one subsystem or one
product attribute — say, the durability of a specific component, or the
usability of a particular interface — produces more actionable insight
than a comprehensive QFD that tries to cover the entire product. The
matrix stays small enough to manage, the cells stay specific enough to
mean something, and the output stays focused enough to actually
influence design decisions.
Third, they iterate. The House of Quality is revisited at design
milestones — not to redo the entire exercise from scratch, but to update
the cells that have changed. Competitive data gets refreshed. Customer
needs get revalidated. Engineering characteristics that proved
infeasible get replaced. The document evolves with the program, and
because it evolves, it stays relevant — and because it stays relevant,
people actually use it.
Fourth, they connect QFD output to downstream processes. The
prioritized engineering targets feed into design FMEA, into control
plans, into production part approval processes. The customer needs flow
into marketing briefs, into user documentation, into service training.
QFD is not a standalone exercise — it is an input to the rest of the
quality system, and when it functions that way, its value compounds
rather than depreciating.
The Deeper Lesson
The deeper lesson of QFD failure is the same lesson that applies to
every quality tool discussed in this series: tools do not fail because
they are flawed. They fail because organizations adopt the form of the
tool without building the practice that makes it work. QFD requires
cross-functional conversation, and most organizations are functionally
siloed. QFD requires honest competitive assessment, and most
organizations prefer comfortable self-assessment. QFD requires
revisiting decisions as conditions change, and most organizations prefer
to lock decisions and move on.
The House of Quality is a structure that works when the people who
build it are willing to have the conversations it demands. Without those
conversations, it is just a matrix — a grid of symbols on a page that
represents the work you were supposed to do together but instead did
separately and called it collaboration.
The fix is not a better template. It is not a software tool. It is
not a training program. The fix is a decision: are you willing to put
marketing, engineering, manufacturing, and quality in the same room and
have them build the matrix together, cell by cell, disagreement by
disagreement, until the picture is honest enough to act on? If yes, QFD
will transform your product development. If no, the matrix will become
another document in another binder on another shelf — and the customer
voice you worked so hard to collect will be the voice nobody in your
engineering department ever hears.
Peter Stasko is a Quality Architect with over 25
years of experience in manufacturing quality management, process
improvement, and quality system design. He has implemented and assessed
quality management systems across automotive, electronics, and heavy
industry sectors, and writes about the practical realities of making
quality tools work in organizations that are not Toyota.
