When developing a product, designers must decide what consumer variation will be addressed and how they will address it, because each consumer has a unique set of human factors, preferences, personal knowledge, and solution constraints. Numerous design methodologies exist to support the design of a product or set of products that address this consumer variation. However, currently there is little work supporting the selection of a design methodology, resulting in an ad hoc or a priori decision before conceptual design begins. This paper presents an affordance-based design method for use prior to conceptual design to help designers understand the consumer variation that is present. This facilitates the creation of a product or set of products that meets the demands of both the consumer(s) and the organization that is developing the product. Once consumer variation is understood, conceptual design can be performed with a more complete understanding of the overall problem.

When developing an artifact, designers must first understand the problem. This includes the benefits that the artifact must deliver and the user variation that is present. Each user has a unique set of human factors, preferences, personal knowledge, and solution constraints that could potentially influence the characteristics of the artifact. Currently, there is little work supporting the process of how to formally generate user-specific design specifications, resulting in ad hoc or a priori decisions when generating design specifications. Further, because most design processes generate design specifications manually, the number of design specifications is not typically addressed at the user level. This research presents an affordance-based approach for use in the early stages of design to help designers establish user-specific design specifications. This information can then be used in the creation of a system or set of systems that meets the demands of both the user(s) and the organization that is developing the artifact. An affordance-based approach is leveraged because it maintains the relational field of view among the user, existing artifacts, and the artifact(s) being designed. Once individual design specifications are generated, designers can use this information in later stages of the design process.