QFD on the Web

Changing the Orientation of Your QFD

Peter Wolfe — Mon, 01 Oct 2007 02:00:14 +0000

Have you ever watched a team of engineers modifying their secondary requirements (a.k.a. the “demanded quality hierarchy” or “hows”) on a House of Quality spreadsheet? They remind me of a group of hillbillies staring at a piece of modern art—their heads are usually cocked to the side with grimaced looks on their faces. (It’s quite entertaining actually.) Considering that in a spreadsheet environment secondary requirements are generally edited far more than primary requirements (the primary requirements list or “quality characteristics hierarchy” is usually pulled automatically from other Houses of Quality in the QFD), have you ever wondered why it is that the secondary requirements are the ones that are flipped on their sides and run across the top of the HOQ?

(more…)

Difficulty Values and the House of Quality

Peter Wolfe — Wed, 15 Aug 2007 08:00:55 +0000

I was recently reviewing a QFD that was created by a group of software developers. They had opted to omit several traditional columns, rows and/or matrices, and had added some new ones. On their final House of Quality they had added a “status” column. Many of the top requirements on this HOQ (the list was sorted by calculated importance) had status values of “Prioritized” or “Completed”. However, I noticed that several of the highest ranked requirements had been skipped and had no status at all. I assumed that these items had no status because they had only recently been added to the QFD. However, I soon learned that my assumption was wrong—these items had been skipped because there simply wasn’t enough time left before the upcoming version release to try to bite off such complex or difficult features.

I asked the team how they knew that a given feature was too complex or time-consuming to complete before a scheduled deadline. I was informed that team members were assigned to do some preliminary analysis on top features in order to estimate how difficult it would be to complete them. When I then asked where they logged this information, I was informed that they “just remembered it”. I then asked how they communicated this information upstream to the business stake holders and received some blank stares. When I asked why they had removed the “difficulty” row from their QFD, I was met with questioning glances and the response, “difficulty row?” (more…)

How Did QFD Get Its Name?

Joseph P. Merts — Fri, 13 Jul 2007 00:00:17 +0000

What’s in a name? While Shakespeare may have been correct in observing that “that which we call a rose by any other name would smell as sweet”, most people would not know what you were talking about if you referred to it as a “bee leaf pollen perch”.

Similarly, the name “Quality Function Deployment” gives little hint as to what the tool actually is or what purpose it serves. So why is its name so perplexing? The answer lies in two main issues…

First, “Quality Function Deployment” was originally created by two Japanese professors back in the 1960’s (Drs. Yoji Akao and Shigeru Mizuno). Thus, the process was originally given a Japanese name, which was later translated into English. The original Japanese name, “Hin-shitsu Ki-no Ten-kai”, was translated quite litterally into the name “Quality Function Deployment”. Although the name supposedly carries with it a more intuitive meaning in Japanese, it doesn’t seem to have the same readily apparent meaning in English.

Additionally, the term “QFD” is used by many people today to refer to a series of “House of Quality” matrices strung together to define customer requirements and translate them into specific product features to meet those needs. However, these prioritization matrices were only a small part of the system that Drs. Akao and Mizuno originally created. (See “What is the House of Quality? Why it isn’t a QFD?” at qfdi.org for more information on this topic.) Thus, the application of the term “QFD” has changed over the course of the past 30+ years as well. Even though much was lost in translation from its Japanese name, “Quality Function Deployment” was a much more apropos name for the system of processes originally created by Akao and Mizumo than it is for the derivative tool that it has come to refer to today.

Limiting the Requirements in a House of Quality

Joseph P. Merts — Sun, 10 Jun 2007 00:00:24 +0000

A comment was recently submitted to QFD Online regarding the limits that should be imposed on the number of requirements for any given House of Quality. The basic premise of the comment was that the number of requirements should be limited in order to keep the HOQ “maintainable”. While the core principle was accurate (i.e. that it requires care and attention when crafting a QFD in order to make sure that it can be maintained long-term), the idea that there is a one-size-fits-all limit that can be used is misguided. Luckily, however, there are processes and procedures that can be applied on a case-by-case basis to ensure maintainable requirement lists.

(more…)

Other QFD Sites

QFD Web — Mon, 04 Jun 2007 23:02:42 +0000

Explanations & Descriptions

Quality Function Deployment (www.wikipedia.org)
Quality function deployment or ‘QFD’ is a flexible and comprehensive group decision making technique used in product or service development, brand marketing and product management…
What is QFD? (www.qfdi.org)
…QFD links the needs of the customer (end user) with design, development, engineering, manufacturing, and service functions…
Customer-focused Development with QFD (www.npd-solutions.com)
…Quality Function Deployment (QFD) is a structured approach to defining customer needs or requirements and translating them into specific plans to produce products to meet those needs….
QFD (www.isixsigma.com)
Quality Function Deployment (QFD) is a systematic process for motivating a business to focus on its customers….

FAQs

QFD FAQ: Frequently Asked Questions about QFD (www.qfdi.org)
How does QFD differ from other quality initiatives? What are the characteristics of QFD as a quality system? What are the tools of QFD?…

Tutorials

Free QFD Tutorial (www.webducate.net)
This tutorial and exercise aims to introduce the approach to product, service and software design decision-making provided by Quality Function Deployment (QFD).

History

Quality Function Deployment: History (www.wikipedia.org)
QFD was originally developed by Drs. Yoji Akao and Shigeru Mizuno in the early 1960s.These techniques extend the original HOQ approach by…
History of QFD (www.qfdi.org)
QFD was developed in Japan in the late 1960s by Professors Shigeru Mizuno and Yoji Akao. At the time, statistical quality control…
QFD: Past, Present, and Future (www.qfdi.org)
…When the name “Toyota” is cited in QFD history, most usually assume it is Toyota Motors,. but that is not correct. It was actually Toyota Auto Body where …

Case Studies

QFD Case Studies and White Papers (www.mazur.net)
QFD case studies performed by Glenn Mazur in connection with companies ranging from Blue Cross Blue Shield to Nokia, and from Rubbermaid to Universal Studios.

QFD and DFSS

QFD and DFSS (www.qfdi.org)
This is where QFD brings power to DFSS. A weakness of many design teams is that they expect that what the customer asks for is only what they want….

QFD vs. House of Quality

Truth About the House of Quality (www.qfdi.org)
…Most interesting is that in many QFD studies, the House of Quality (HOQ) is not the starting point and can even be unnecessary. That “the House of Quality is the QFD” is a myth that is still propagated by many people….

General QFD Topics

House of Quality Online (www.houseofqualityonline.com)
QFD Online (www.qfdonline.com)
The QFD Journal (www.qfdonline.net)
Quality Function Deployment Online (www.qualityfunctiondeploymentonline.com)

QFD and Agile Feature Prioritization

John Livingston — Tue, 22 May 2007 01:30:48 +0000

Imagine for a moment that you are the president of a successful software development company. Your company is doing reasonably well from a sales perspective, but you have been dealing with some sizable challenges in terms of your development team hitting their scheduled release dates on time. (The past 2 releases have been late by more than six months a piece.) Then one day your development manager comes into your office droning on about the success of something called “Agile” development methodologies. He goes on to tell you that he knows how to eliminate the slippages that he and his team have experienced in relation to your two year development plan: simply do away with the two year development plan. Needless to say, the conversation would probably not go well. However, there is a sweetener that can assist executive management in swallowing the sometimes bitter pill of “Agile” development—and that sweetener bears the name “QFD”. (more…)

QFD First Step: Determine Your Customer

Joseph P. Merts — Sun, 20 May 2007 00:00:18 +0000

Most people believe that the first step in creating a successful QFD is to identify the list of customer requirements. Although documenting customer requirements is key to ensuring that the “voice of the customer” is heard, there is actually an even more crucial first step. The very first task to complete when creating a Quality Function Deployment is to identify exactly who your “daddy” (i.e. customer) really is, and that task isn’t as easy as you might think.

Numerous QFDs fail (i.e. cease to be used or to be useful) because too many features are added to the relevant product or service in a manner that bypasses the QFD altogether. These assignments are made in a manner that circumvents the system in order to address “urgent” requirements. Unfortunately, as soon as a window is opened for non-customers to push “urgent” matters to the front of the queue, they stop using methodical processes for prioritization altogether. Soon, every pet project or feature gets identified as “urgent” or “imperative”, and the QFD falls to the wayside with the voice of the customer close behind.

This may seem like an easy problem to fix—all that needs to be done is to make sure that these “urgent” items get added to the QFD like every other feature or requirement. If needed, these items can be evaluated and rated before other requirements, but they won’t be worked on until they merit attention. The problem is that many of these urgent items would never warrant attention, according to the QFD, because the wrong customer was identified in the first place.

(more…)

Remodeling the House of Quality

Peter Wolfe — Tue, 24 Apr 2007 01:30:56 +0000

In 1979, a PBS station in Boston called “WGBH” aired a one-time, 13-part series entitled “This Old House”. Since that time, the program has grown to become one of PBS’s most popular programs, has generated spin-offs, produced a popular magazine, spawned a for-profit website, and even inspired sitcoms.[1] And why has this program been so successful? In my opinion, it’s because people have an inherent love for taking something great, stripping away its faults, and putting it to new found use. That is the same explanation that I use when people ask me about Quality Function Deployment’s resurgence in popularity during recent years. In short, when people ask me why QFD has experienced so much growth in adoption, my answer is simply: “This Old House…of Quality”.

(more…)