Robust Quality Function Deployment
Also known as: Robust QFD, Uncertainty-tolerant QFD, Fuzzy-robust QFD, Robust House of Quality
Robust Quality Function Deployment (Robust QFD) extends the classical House of Quality framework by explicitly modeling uncertainty and variability in customer requirements, perception ratings, and engineering correlation judgments. Instead of treating inputs as crisp single-point values, it applies fuzzy sets, interval analysis, or Taguchi-inspired robustness techniques to ensure that the resulting design targets remain stable and customer-satisfying even when inputs are imprecise or fluctuating.
Read the full method
Sign in with a free account to read this section.
Method map
The neighbourhood of related methods — select a node to explore.
When to use it
Use Robust QFD when translating voice of the customer into engineering targets in contexts where customer preference data are noisy, survey sample sizes are limited, or expert teams disagree about relationship strengths in the House of Quality. It is especially valuable in early product development when requirements are still evolving, and in regulated industries (medical devices, aerospace, automotive) where under-delivering on a customer requirement has severe consequences. Do not use it as a replacement for adequate market research — Robust QFD manages uncertainty but does not manufacture information; if only two or three customer data points exist, no robustness treatment can substitute for proper sampling. Avoid it when the QFD matrix is very large (50+ requirements × 50+ characteristics), as fuzzy arithmetic becomes computationally demanding without tool support.
Strengths & limitations
- Explicitly acknowledges and propagates uncertainty in customer ratings and engineering correlations rather than hiding it behind false precision.
- Produces stability rankings — revealing which engineering priorities are robust consensus choices and which depend on contested assumptions.
- Compatible with standard QFD software and workflows; the robust layer can be added incrementally without redesigning the entire process.
- Particularly valuable in multi-disciplinary teams where engineering and marketing experts hold genuinely different relationship-strength beliefs.
- Aligns naturally with Taguchi-style robustness objectives already familiar to quality engineers.
- Increases computational and cognitive complexity relative to classical QFD — teams unfamiliar with fuzzy arithmetic may find interpretation challenging.
- Defining meaningful fuzzy membership functions or uncertainty intervals for relationship strengths requires calibrated expert elicitation, which is itself uncertain.
- Does not resolve fundamental ambiguity: if the voice of the customer is poorly captured, the robust layer cannot compensate for flawed input data.
- Limited off-the-shelf software support; most commercial QFD tools use crisp values, requiring custom spreadsheet or coding implementations.
Frequently asked
What is the difference between Fuzzy QFD and Robust QFD?
Fuzzy QFD uses fuzzy linguistic terms (e.g., 'high', 'medium', 'low') to encode customer ratings and relationship strengths, converting them to fuzzy numbers for computation. Robust QFD goes a step further: it evaluates how stable the engineering priority rankings are under the modeled uncertainty and selects targets that perform well across the uncertainty range. Fuzzy QFD addresses representation; Robust QFD addresses decision stability under that fuzzy representation.
Do I need special software to implement Robust QFD?
Standard QFD tools (QFD Capture, QFD Designer) do not natively support fuzzy or interval arithmetic. Implementations typically use Excel with custom formulas, MATLAB, or Python (with scipy or fuzzy-logic libraries). For small matrices (fewer than 20 requirements and 20 characteristics), a spreadsheet implementation is tractable; larger matrices benefit from dedicated scripting.
How many customer respondents are needed?
Classical QFD has no minimum rule, but the robustness framework makes the problem explicit: with very few respondents the confidence intervals around importance weights are wide, and the Robust QFD output will reflect this by showing most engineering priorities as uncertain. A sample of at least 30 respondents is generally needed to produce reasonably stable importance estimates before applying robust prioritization.
Can Robust QFD be combined with FMEA?
Yes. After Robust QFD identifies and ranks engineering characteristics, FMEA can be applied to the highest-priority characteristics to identify failure modes that would undermine the customer requirements they serve. This is a common workflow in automotive APQP (Advanced Product Quality Planning) processes.
Is Robust QFD applicable to service design, not just physical products?
Yes. QFD has been applied to service design since the 1980s, and the robust extension is equally applicable. Service attributes and their relationships to customer satisfaction are often more uncertain than physical engineering parameters, making the robustness layer particularly valuable in healthcare services, hospitality, and financial product design.
Sources
- Fung, R. Y. K., Tang, J., & Tu, Y. (2002). Modeling of quality function deployment planning under resource allocation constraints. Computers & Industrial Engineering, 43(1–2), 313–328. link ↗
- Kwong, C. K., & Bai, H. (2002). A fuzzy AHP approach to the determination of importance weights of customer requirements in quality function deployment. Journal of Intelligent Manufacturing, 13(5), 367–377. link ↗
How to cite this page
ScholarGate. (2026, June 3). Robust Quality Function Deployment. ScholarGate. https://scholargate.app/en/experimental-design/robust-quality-function-deployment
Which method?
Set this method beside its closest kin and read them side by side — the library lays the books on the table; the choice is yours.
- Failure Mode and Effects AnalysisExperimental design↔ compare
- Quality Function DeploymentExperimental design↔ compare
- Robust Failure Mode and Effects AnalysisExperimental design↔ compare
- Robust Statistical Process ControlExperimental design↔ compare