Let's say that you are working in the engineering department of a new automotive manufacturing company. The name of this new companies test go. I've made up this name as a combination of two automotive companies that I like Tesla, and Google. They are truly trying to bring innovation in the automotive sector. Oh, yeah, I know, this reading is not about Tesla or Google, nor am I getting paid for placing their products on this training video. So let's come back to our topic.

So, as an engineering employee of Tesco, you're solving a simple problem of building a car door that serves the customer feedback such as the door should be easy to close, or it should not leak in rain, or allow little or no road noise. As you think of linking these customer expressions into Specific engineering characteristics of the door. This simple problem will start looking big. For example, when the customer says the door should be easy to close, how would your engineering department know what amount of force on the door is easy for the customer? Similarly, if the customer says that the door should allow little road noise, how would you know what noise level is acceptable by the customer? Everyone in the engineering department would be clueless because the customer needs are not translated into engineering characteristics.

Imagine how easier it would be if the customer tells you that the car door should not exceed a force of thousand Newtons or the allowable limit for road noise is five decibels. Do you really think This will happen. This never happens because customer requirements are always hazy. And this is where quality function deployment comes handy.