Quality Function Deployment
Quality Function Deployment
Outline
Introduction QFD Team Benefits Of QFD Voice Of The Customer House Of Quality Building A House Of Quality QFD Process Summary
Introduction
Dr. Mizuno, Prof. Emeritus Mitsubishi Heavy Industries
Kobe Shipyards, 1972
QFD Team
Significant Amount Of Time
Communication
Benefits Of QFD
Customer Driven Reduces Implementation Time Promotes Teamwork Provides Documentation
Customer Driven
Creates Focus On Customer Requirements Uses Competitive Information Effectively Prioritizes Resources Identifies Items That Can Be Acted On Structures Resident Experience/Information
Promotes Teamwork
Based On Consensus Creates Communication At Interfaces Identifies Actions At Interfaces Creates Global View-Out Of Details
Provides Documentation
Documents Rationale For Design Is Easy To Assimilate Adds Structure To The Information Adapts To Changes (Living Document) Provides Framework For Sensitivity Analysis
Customer Satisfaction
Meeting Or Exceeding Customer Expectations Customer Expectations Can Be Vague & General In Nature Customer Expectations Must Be Taken Literally, Not Translated Into What The Organization Desires
House Of Quality
Interrelationship between Technical Descriptors Technical Descriptors (Voice of the organization) Customer Requirements (Voice of the Customer) Prioritized Customer Requirements
QFD Matrix
Technical Descriptors Primary Secondary
Our As Bs Customer Importance Target Value Scale-up Factor Sales Point Absolute Weight
Technical Our Competitive As Assessment Bs Degree of Technical Difficulty Target Value Absolute Weight and Percent Relative Weight and Percent
Customer Requirements
+9 +3 -3 -9
Primary
Secondary
Relationship between Customer Requirements and Technical Descriptors WHATs vs. HOWs
+9 +3 +1 Strong Medium Weak
Primary
Secondary
Primary
Secondary
L - Shaped Diagram
Technical Descriptors Primary Secondary Secondary
Customer Requirements
Primary
Relationship Matrix
Technical Descriptors Primary Secondary Secondary Primary
Customer Requirements
Relationship between Customer Requirements and Technical Descriptors WHATs vs. HOWs
+9 +3 +1 Strong Medium Weak
Correlation Matrix
Technical Descriptors Primary Secondary Secondary Primary Interrelationship between Technical Descriptors (correlation matrix) HOWs vs. HOWs
+9 +3 -3 -9 Strong Positive Positive Negative Strong Negative
Customer Requirements
Relationship between Customer Requirements and Technical Descriptors WHATs vs. HOWs
+9 +3 +1 Strong Medium Weak
Customer Requirements
Relationship between Customer Requirements and Technical Descriptors WHATs vs. HOWs
+9 +3 +1 Strong Medium Weak
Secondary
Secondary
Primary
Relationship between Customer Requirements and Technical Descriptors WHATs vs. HOWs
+9 +3 +1
Prioritized Customer Requirements
5 3 1 2 5 1 4 4 1 3 4 21 2 1 4
7 3 9 10 2 4 8 1
Our As Bs Customer Importance Target Value Scale-up Factor Sales Point Absolute Weight
Customer Requirements
n a R c j ij i i 1
n b R d j ij i i 1
1 3 4 21 2 1 4 Technical Our Competitive As Assessment Bs Degree of Technical Difficulty 1 8 4 2 9 8 2 5 2 3 4 31 3 1 5 Target Value Absolute Weight and Percent 90 133 Relative Weight and Percent Prioritized Technical Descriptors
Customer Requirements
Our As Bs Customer Importance Target Value Scale-up Factor Sales Point Absolute Weight
+9 +3 -3 -9
Primary
Secondary
Secondary
Relationship between Customer Requirements and Technical Descriptors WHATs vs. HOWs
+9 +3 +1
5 3 1 2 5 1 4 4 7 3 9 10 2 4 8 1
QFD Process
HOWs HOWs
WHATs
HOW MUCH
Production Launch
QFD Summary
Orderly Way Of Obtaining Information & Presenting It Shorter Product Development Cycle Considerably Reduced Start-Up Costs Fewer Engineering Changes Reduced Chance Of Oversights During Design Process Environment Of Teamwork Consensus Decisions Preserves Everything In Writing