Asee peer logo

Learning How To Identify Customer Requirements: A Key Component Of Product Development Courses

Download Paper |


2004 Annual Conference


Salt Lake City, Utah

Publication Date

June 20, 2004

Start Date

June 20, 2004

End Date

June 23, 2004



Conference Session

Teaching Design

Page Count


Page Numbers

9.851.1 - 9.851.31



Permanent URL

Download Count


Request a correction

Paper Authors

author page

Karim Muci-Kuchler

author page

Jonathan Weaver

Download Paper |

NOTE: The first page of text has been automatically extracted and included below in lieu of an abstract

Session 2125

Learning How to Identify Customer Requirements: A Key Component of Product Development Courses

Karim H. Muci-Küchler1 and Jonathan M. Weaver2 1 Mechanical Engineering Department South Dakota School of Mines and Technology 2 Mechanical Engineering Department University of Detroit Mercy


A crucial step in the process to develop a new product is the identification of the customer requirements. The outcomes from this step strongly influence both the rest of the development effort and the ultimate success or failure of the product. When students work in teams in product development (PD) projects, they often tend to start generating solution concepts right away without carefully identifying all the stakeholders that must be taken into consideration, determining all the customer needs, and establishing their relative importance. The reason for this may be twofold. First, many engineering students believe that in their professional career they will seldom be actively involved in the identification of the customer needs. Second, it is more appealing for engineering students to embark in the creative and open-ended process of concept generation than to spend time interacting with customers to establish their true expectations. The problem is that, in the “real world,” an engineer working in PD needs to be substantially involved in the process of identifying product requirements. In addition, without direct interaction with the customers, it is not possible to have a clear understanding of what they want. This, in turn, usually leads to the selection of a product concept that either fails to satisfy some key customer expectations or sub-optimally trades-off one attribute against another.

To overcome the problems stated above, it is important to emphasize in PD courses a formal process to identify customer needs. Furthermore, students must apply what they learn so that they can really acquire the knowledge and skills required to successfully complete this task. To explore the benefits of this approach, a formal process to actively identify customer requirements was introduced into a sophomore PD course, a senior capstone design course, and a graduate level course in PD. Although the level of interest demonstrated by the teams varied, some of them managed to understand the customer requirements at a level that was above the instructor’s expectations. In this paper, the approach followed, the results obtained, and suggestions for future improvement are discussed in the context of projects carried out by the students.

Proceedings of the 2004 American Society for Engineering Education Annual Conference & Exposition Copyright © 2004, American Society for Engineering Education

Muci-Kuchler, K., & Weaver, J. (2004, June), Learning How To Identify Customer Requirements: A Key Component Of Product Development Courses Paper presented at 2004 Annual Conference, Salt Lake City, Utah. 10.18260/1-2--13997

ASEE holds the copyright on this document. It may be read by the public free of charge. Authors may archive their work on personal websites or in institutional repositories with the following citation: © 2004 American Society for Engineering Education. Other scholars may excerpt or quote from these materials with the same citation. When excerpting or quoting from Conference Proceedings, authors should, in addition to noting the ASEE copyright, list all the original authors and their institutions and name the host city of the conference. - Last updated April 1, 2015