As designers, we understand the importance of prototypes in the product development process. Prototypes help us test our assumptions, gather feedback from users, and refine our designs. But have you ever stopped to consider what exactly prototypes are meant to prototype? This is the central question that Houde and Hill (1997) explore in their seminal article, "What Do Prototypes Prototype?"

Houde and Hill are both design researchers who have contributed extensively to the field of human-computer interaction. In this article, they argue that prototypes can serve a variety of purposes, depending on the stage of the design process and the intended audience. They propose a framework for understanding the different types of prototypes, which they classify into three main categories: role prototypes, look-and-feel prototypes, and implementation prototypes.

So, how does this article affect our design practice? First and foremost, it reminds us to be intentional about the purpose of our prototypes. Are we trying to test the functionality of a new feature, or are we simply trying to get feedback on the overall user experience? By clarifying the goals of our prototypes, we can make better decisions about what type of prototype to create and how to test it.

Reading this text also raises a number of interesting questions. For example, how do we decide which type of prototype to create at each stage of the design process? How do we ensure that our prototypes are serving the intended purpose? And what role do prototypes play in communicating design ideas to stakeholders and team members?

Role prototypes are meant to explore the functional requirements and user roles of a system, while look-and-feel prototypes focus on the user interface and visual design. Implementation prototypes, on the other hand, are meant to test the technical feasibility and performance of a design. By understanding these different types of prototypes, we can make more informed decisions about how to use them in our own design practice.

By understanding the different types of prototypes and their intended purposes, we can create more effective prototypes and make better design decisions.

prototypes are not selfexplanatory: looks can be deceiving. Clarifying what aspects of a prototype correspond to the eventual artifact—and what don’t—is a key part of successful prototyping.

“Look and feel” denotes questions about the concrete sensory experience

“Implementation” refers to questions about the techniques and components through which an artifact performs its function

“Role” refers to questions about the function that an artifact serves in a user’s life