Using QFD To Write An ISO
Using QFD To Write An ISO
Quality Engineering
Publication details, including instructions for authors and subscription information:
[Link]
To cite this article: Glenn H. Mazur (2012) Using Quality Function Deployment to Write an ISO Standard for QFD*, Quality
Engineering, 24:3, 436-443, DOI: 10.1080/08982112.2012.682510
Taylor & Francis makes every effort to ensure the accuracy of all the information (the “Content”) contained
in the publications on our platform. However, Taylor & Francis, our agents, and our licensors make no
representations or warranties whatsoever as to the accuracy, completeness, or suitability for any purpose of the
Content. Any opinions and views expressed in this publication are the opinions and views of the authors, and
are not the views of or endorsed by Taylor & Francis. The accuracy of the Content should not be relied upon and
should be independently verified with primary sources of information. Taylor and Francis shall not be liable for
any losses, actions, claims, proceedings, demands, costs, expenses, damages, and other liabilities whatsoever
or howsoever caused arising directly or indirectly in connection with, in relation to or arising out of the use of
the Content.
This article may be used for research, teaching, and private study purposes. Any substantial or systematic
reproduction, redistribution, reselling, loan, sub-licensing, systematic supply, or distribution in any
form to anyone is expressly forbidden. Terms & Conditions of access and use can be found at http://
[Link]/page/terms-and-conditions
Quality Engineering, 24:436–443, 2012
Copyright # Taylor & Francis Group, LLC
ISSN: 0898-2112 print=1532-4222 online
DOI: 10.1080/08982112.2012.682510
the customer to explore high-priority spoken and unspoken needs that must
be met for a new product or service to be accepted. To achieve this first-time
quality, developers must know what problems the customer has, how
important those problems are to helping the customer do their job better,
and what level of improvement is necessary for the customer to accept it
in place of their current practice. Thus, QFD is highly dependent on the cus-
tomer and their business, the industry of the product or service, and what
competitive alternatives the customer has access to. This article will discuss
how these same methods are used to write the QFD standard itself.
FIGURE 1 Draft writing timeline for QFD standard. (Color figure available online.)
Step 1.2—Define Process Steps 10. Propose QFD implementation guidelines for
successful and sustainable QFD applications.
for WG2 Activities
11. Propose criteria for measuring the success of a
The task of writing the standard was broken down QFD application.
into a series of tasks as follows: 12. Propose guidelines for continuous improvement
of QFD activities within the organization.
1. Define timeline for WG2. Ask SC8 to please 13. Recommend resources for obtaining QFD
provide this information to me as soon as knowledge and best practice.
possible. 14. Provide examples of QFD applications.
2. Develop WG team member selection criteria.
Based upon the purpose and scope, develop a
prioritized list of criteria from which to propose Step 1.3—Develop Timeline
and select membership in WG2. Creating, submitting, receiving commentary, revis-
3. Identify users (customers) of the proposed QFD ing, and publish a standard has its own scheduling
standard. requirements that must be managed like any other
4. Interview and=or survey users in order to under- project. To make sure the proper experts, draft
stand their problems and wishes. editors, and other resources are available when
5. Translate problems and wishes into user needs. needed, as well as interim meeting attendance and
6. Have users prioritize their needs. appropriate review periods, a timeline was created
7. Translate prioritized needs into prioritized and approved by the chairman of Subcommittee 8
technical characteristics of QFD, including (see the timeline Figure 1).
recommendations for methods, tools, and
approaches.
8. Develop standards and recommendations in
Step 2—Select Team Members
accordance with the priorities of the technical Discussions with several members of other U.S.
characteristics. TAG69 conveners revealed what makes a good
9. Identify potential failure modes for QFD and working group team member. Because not every
recommendations. potential team member would epitomize all
G. Mazur 438
useful to convert all of the statements into expressions
of positive expectations for which each candidate mem-
ber could be evaluated objectively or subjectively.
These were structured into the hierarchy in Figure 2.
The hierarchy helps organize criteria by layers of
abstraction, which will improve the prioritization pro-
cess described below.
FIGURE 3 AHP-derived prioritized working group membership selection criteria. (Color figure available online.)
TAG69 members who advised on the criteria. The and teams were formed to begin writing the draft,
AHP method has the leaves of each hierarchical and deadlines were established. Additional interim
branch compared pair-wise using a verbal scale to WebEx conference calls were also scheduled. The
determine which of the pair is more important and project teams were as follows:
by how much. The verbal scale is as follows: equally
important, moderately more important, strongly 1. Voice of customer—engineers
more important, very strongly more important, or 2. Review of the Japanese standard Q-9025
extremely more important. A pair-wise survey was 3. Architecture and structure of standard
e-mailed and the results were entered into an AHP 4. Scope setting
matrix from which the right principle eigenvector 5. QFD in design life cycle
was calculated to approximate the ratio scale priori- 6. ISO terminology alignment
ties shown in Figure 3. 7. QFD definitions
8. QFD principles
9. Minimum QFD effort
Step 2.3—Nominating WG Members 10. QFD methods
Based on the above weighted criteria, individuals 11. Related methods bibliography
were evaluated according to how well they met the 12. Integration of all work in first draft
criteria. Because this is to be an international stan-
dard, members from the worldwide QFD com-
munity were considered first. These included QFD
leaders from countries that had hosted one or more Step 3—Voice of the Customer—
international symposia on QFD. Members were
then asked to join their country’s ISO member body
Engineers
so that they could participate and vote fully. QFD, at its core, is about designing in customer
These individuals are also country representatives satisfaction from the beginning in order to assure
of the ICQFD and the chairman of the SC8 recom- first-pass quality acceptance. This requires that the
mended that the ICQFD be appointed a liaison developers understand clearly what customers want
organization of the SC8. ICQFD members, in alpha- before design work begins. Though QFD is widely
betical order: used in manufactured products, service products,
and software products, I believe it was best to start
Ms. Veronica Gonzalez Bosch (Mexico, ITESM and with the voice of engineers who would use this
QFD-LAT) QFD standard in the process of developing new pro-
Dr. Nicklas Bylund (Sweden, Sandvik Corporation) ducts for their companies.
G. Mazur 440
TABLE 1 Voice of the customer table for aerospace engineers (partial)
Segment VOC (Standards User) Customer needs Design ideas
Aerospace Engineer Where to look standard, how Easy to find when I need it. Put ISO links on ICQFD member
to find websites?
differs from our std Easy to know how stand differs
from our internal standards.
simple enough for average Easy for non-QFD specialist to
person to understand understand.
too loosey-goosey-is it worth Standard is useful to my work. Sufficient detail. Role specific
the trouble (marketing, design,
engineering, manufacturing,
quality, supply chain, etc.)
morphs over time to cover new I am always from the current Ongoing VOC feedback
req’t-are we using current versio. I know when next version gathering.
version? User wants to stay will be released so I can plan for
up to date with standard, it. Standard is useful to my
offer suggestions on how to future work.
improve or make more
Downloaded by [Northeastern University] at 04:44 12 November 2014
relevant.
have multiple implementation Standard is easy for beginners to Multiple implementation levels.
levels within the standard. utilize. Standard is useful to my
Common level, plus special work.
areas with more meat.
make sure your customer and Benefits of following standardare
vendors buy into the easy to explain to my customers.
standard-cost=benefit ratio. Easy for my vendors to follow
the standard. Easy to follow
standsrd.
easily accommodate changes in Standard is easy to adapt to Publish case studies?
my business as technology changes in my business.
changes.
make something people want Standard is useul to my work. Easy
to use. must be easy to use, to follow standard.
especially if voluntary.
must be on website. Best if no Easy to find standard when I need Standard published website.
charge because of the effort it. Benefits of following
to rationalize to my boss or standard are easy to explain to
company the need to pay for my mamagement.
the documentation.
Step 3.1—Identify Users of the receive. Instead, we looked at industries that were
most recently adopting QFD methods and selected
QFD Standard
aerospace, automotive, medical devices, and infor-
Most development projects today struggle to mation technology business architects. The next step
meet all requirements of all users and must accept was to identify representatives from these industries
that at best they should focus on meeting the most for in-depth interviews in order to capture the voice
important requirements of the most important users. of the customer.
In a business environment, user importance can be
measured by such criteria as revenue potential, prof-
Step 3.2—Capturing and Analyzing
itability, market share, and other financial metrics. In
ISO standards development, financial benefit is the Voice of the Customer
replaced by the sense of professional contribution Voice of the customer starts our analysis of true
and recognition the volunteer team members customer needs, which QFD defines as the following
G. Mazur 442
Symposium on Quality Function Deployment. Glenn academician of the International Academy for Qual-
is the Executive Director of the QFD Institute and ity. He is the honorary president of the Hong Kong
International Council for QFD, adjunct lecturer on QFD Association.
TQM at the University of Michigan College of Engin-
eering (ret.), President of Japan Business Consultants
Ltd., and a senior member of the American Society
for Quality (ASQ) and the Japanese Society for Qual-
REFERENCES
ity Control (JSQC). He is a certified QFD Red Belt1 Akao, Y., Ed. (1990). Quality Function Deployment: Integrating Customer
Requirements into Product Design. Translated by Glenn Mazur.
(highest level), one of two in North America. He is
Cambridge, MA: Productivity Press.
a certified QFD-Architekt #A21907 by QFD Institut Mizuno, S., Akao, Y., Eds. (1994). QFD: the Customer Driven Approach to
Deutschland. He is convenor of the ISO Technical Quality Planning and Deployment. Translated by Glenn Mazur. Tokyo:
Asian Productivity Organization.
Committee 69 Subcommittee 8 Working Group 2 to Saaty, T. L. (1990). The Analytic Hierarchy Process. Pittsburgh, PA: RWS
write an international standard for QFD. He is an Publications.
Downloaded by [Northeastern University] at 04:44 12 November 2014