Design to Cost · Value
QFD Lite
Translate customer requirements into technical characteristics with weights — the light house of quality, one matrix, no cult.
- Time1 h 30
- FormatTeam
- StageValue
QFD Lite: what it is and why it works
QFD Lite is a simplified form of Quality Function Deployment that uses a single matrix to connect customer requirements with the technical characteristics that deliver them. Customer requirements, with importance weights, form the rows; measurable technical characteristics form the columns. Each cell records how strongly a characteristic influences a requirement, often on a 9-3-1 scale. Multiplying weights by relationship strengths and summing each column gives the priority of each technical characteristic. Adding a comparison with competitors on the same characteristics shows where improvement matters most.
Full QFD, developed by Yoji Akao from 1966, uses a series of linked matrices, and its first matrix is known as the house of quality. Many teams find the full method heavy, but its core logic is valuable for design to cost: it shows which technical characteristics carry customer value and which consume effort and cost with little effect on what customers care about. The one-matrix version keeps that logic while remaining quick enough to use on a real project. It takes customer priorities from Kano analysis and price-value alignment and links them to the engineering functions defined in functional analysis, so that cost can be directed toward characteristics that matter.
What you need
- The top customer requirements, typically five to ten, with importance weights
- A list of measurable technical characteristics that could influence those requirements
- Engineering knowledge of how characteristics relate to requirements
- Competitor data or test results on the same characteristics
- The cost of improving each characteristic, at least approximately
What you get
- A one-page relationship matrix with scored cells
- A priority ranking of technical characteristics
- A competitor comparison for the highest-priority characteristics
- A short list of characteristics to invest in and characteristics not worth extra cost
When to use it
When customer wishes and engineering specs meet but do not talk.
How to do it, step by step
- Collect the top customer requirements for the product.
- List the main technical characteristics that drive those requirements.
- Build a light matrix: how strongly does each characteristic serve each requirement?
- Add the competitor comparison on the same characteristics.
- Prioritize the characteristics with high impact and weak competitor position.
Worked example: High-volume, low-speed fans for warehouses
Illustrative scenario — figures are realistic but not from a real company.
A manufacturer of high-volume, low-speed ceiling fans for warehouses was designing a new model. Engineering wanted to invest in an advanced blade profile, while sales reported that contractors complained about installation time.
- The team collected five customer requirements from distributors and facility managers and weighted them: cover a large floor area (5), use little energy (4), need little maintenance (4), install quickly (3), and run quietly (3). Safety features such as secondary retention were treated as fixed requirements, not traded.
- They listed technical characteristics: blade diameter, blade profile, motor efficiency, direct drive versus gearbox, installed weight and number of wear parts.
- Scoring 9, 3 or 1 for strong, medium or weak relationships, direct drive scored 81: strong for energy and maintenance, medium for noise. Blade diameter scored 57, installed weight 30, and the advanced blade profile only 24.
- A competitor comparison showed the new design was already competitive on airflow but weak on installed weight and number of wear parts.
- The team prioritized direct drive and a lighter mounting system and dropped the advanced blade profile from the first release.
Result. The new model used a gearless direct drive and a lighter mount that reduced installation time on a typical warehouse job by about a third. The cost saved on the blade profile helped fund the motor. The team concluded that the matrix had settled a debate that had been running on opinion for months.
Common pitfalls and how to avoid them
- Listing too many requirements and characteristics, so the matrix becomes unmanageable.Limit rows and columns to the most important items; the goal is one readable page.
- Writing technical characteristics that cannot be measured.Express each characteristic with a unit or a clear test, such as sound level in dBA or installed weight in pounds.
- Filling the matrix with strong relationships everywhere.Challenge each strong score and require a clear technical reason for it.
- Treating safety or regulatory requirements as tradable.Handle them as fixed constraints outside the scoring.
Frequently asked questions
What is the house of quality?
The house of quality is the first and best-known matrix of Quality Function Deployment. It links customer requirements to technical characteristics through a relationship matrix and usually adds a roof showing correlations between characteristics, competitor comparisons and target values. Its shape resembles a house, which gives it its name. QFD Lite uses a simplified version of this matrix.
How do you score a QFD relationship matrix?
For each cell, decide how strongly a technical characteristic influences a customer requirement. A common scale uses 9 for strong, 3 for medium, 1 for weak and blank for none. Multiply each score by the requirement's importance weight and sum each column. The totals rank the technical characteristics by their overall contribution to customer needs.
When is full QFD worth it compared with a one-matrix version?
Full QFD, with several linked matrices from requirements to parts and processes, can be worth it for complex, high-stakes products where requirements must be traced in detail through the whole development. For most design-to-cost decisions, a single matrix linking customer needs to technical characteristics gives most of the insight with much less effort.
Origin
Quality Function Deployment — Yoji Akao, 1966; simplified one-matrix form here.
Related methods
- Kano ClassificationSort features by customer reaction: basics, performers, delighters — and question the ones nobody would miss.
- Functional AnalysisExpress the product as functions — verb plus object — free of solutions: what must it do, not how.
- Price-Value AlignmentCheck that the price customers accept matches the value they perceive — a gap means margin risk or value left…
More in “Value”
Find what the customer actually values — and what they never asked for.