Quality Function Deployment
Quality Function Deployment
What is QFD?
A method of transferring customer needs and requirements into technical specifications for new product and service development.
Brief History
Dr. Yoji Akao and Shigeru Mizuno First implemented at Mitsubishi Heavy Industries, Kobe Shipyard in 1972 Toyota strongly influenced adoption of QFD in North America
Between 1977-1984 achieved a 61% reduction in product development cost, a 33% reduction in product development cycle, and virtual elimination of rust related warranty problems.
Analysis
Detailed review of market potential and production costs
Development
Detailed specifications Process design Marketing program design Personnel training Testing and pilot runs
Post-launch review
Full Launch
Market promotions Sales personnel briefed Distribution processes activated Old services or products withdrawn Production of new offering and ramp-up
Figure 2.2
Everywhere !
Who must be satisfied with the product in order for the product to be considered successful?"
Defining Customers
Users who are concerned with functionality. Management who is concerned with financial and strategic issues. Distribution and Purchasing Agents who are concerned with purchase transaction and availability issues. Internal workers who are concerned with how the product will affect the quality of their work life.
Prioritizing Requirements
Importance to the Customer Our Current Product Competitor One Competitor Two Our Future Product Improvement Factor Overall Importance Percent Importance
Benchmarking
Benchmarking
Why Benchmark?
Establishes a definition to the level of real performance required to produce the desired level of perceived performance Develop a product or service which will excite the customer and get him/her to purchase your product
Benchmarking
Benchmarking
Target Values
Target Values
The final goal of many QFD projects is to set the target values for the design measures.
Defining Actions
Affinity Diagrams Relations Diagrams Hierarchy Trees (Tree Diagram) Matrices And Tables. Process Decision Program Diagrams (PDPC) Analytic Hierarchy Process (AHP) Blueprinting
Affinity Diagrams
Method utilized by teams to organize/gain insight into a set of qualitative information, (i.e. voiced customer requirements). Developed to discover meaningful groups of ideas within a raw list.
Ishikawa recommends using the affinity diagram when facts or thoughts are uncertain and need to be organized, when pre-existing ideas or paradigms need to be overcome, when ideas need to be clarified, and when unity within a team needs to be created.
Relations Diagrams
Drawn to show all the different relationships between factors, areas, or processes. Facilitates the selection of factors that drive many of the other symptoms or factors.
Illustrates the structure of interrelationships between groups of statements Built from the top down in an analytical manner. Applied to an existing set of structured information, such as that produced by building an Affinity Diagram and then used to account for flaws in the data.
A series of related matrices and tables used as the tool for translating the voice of the customer First to design specifications Second to more detailed part characteristics Third to show the necessary process and technology characteristics Finally to show the specific operational conditions for the production phase
AHP uses pair wise comparisons on hierarchically organized elements to produce an accurate set of priorities.
Blueprinting
Blueprinting is a tool used to illustrate and analyze all the processes involved in providing a service.
Different Modes of Application Matrix of Matrices Approach Used to address wide variety of development issues Uses specific matrices for each specific development issue
Depends on your individual Product Needs Each System can be modified to suit specific situations
House Of Quality
House Of Quality
This technique is a type of conceptual map providing means to the inter-functional planning and coordination in product improvement and development. This method brings the customer needs in the focus to design/ redesign the product and service
Identify Customer Wants Identify How The Good/Service Will Satisfy The Customers Wants Planning Matrix Interrelationship matrix Technical correlation (Roof) matrix Technical priorities, benchmarks and targets
Step 1
Step 2
Step 3
Planning Matrix
Illustrates customer perceptions observed in market surveys Includes relative importance of customer requirements, company and competitor performance in meeting these requirements
Step 4
Interrelationship matrix
Illustrates the QFD team's perceptions of interrelationships between technical and customer requirements An appropriate scale is applied, illustrated using symbols or figures. Filling this portion of the matrix involves discussions and consensus building within the team and can be time consuming Concentrating on key relationships and minimizing the numbers of requirements are useful techniques to reduce the demands on resources
Step 5
used to identify where technical requirements support or impede each other in the product design Can highlight innovation opportunities
Step 6
The final output of the matrix is a set of target values for each technical requirement to be met by the new design, which are linked back to the demands of the customer
Example
Reduced time to market Reduction in design changes Decreased design and manufacturing costs Improved quality Increased customer satisfaction