Reading response

After reading this article about paper prototyping, my strongest feeling is that design can be very light and very fast. I used to think a prototype must “look real” to be meaningful, but the methods in the article showed me another possibility. Rough sketches, tape, and pieces of paper that can be torn off at any moment look almost like a child’s game, yet they can lead to very real reactions from users.

​

The article treats “quick changes” and “being able to adjust anytime” as a basic attitude. This made me think about my own design habits, especially the belief that I should make something more complete before showing it to others. In paper prototyping, incompleteness is not a flaw but an invitation. The less perfect it is, the more willing people are to point out issues, because everyone knows it can be replaced in a second.

The idea that users speak more freely when they see a draft also feels very true to me. In real life, when an interface already looks polished and close to a final product, people become careful. They stop touching it and hesitate to criticize it. But paper does not create pressure. It is light, fragile, and it makes conversations feel more natural.

​

I am also interested in the idea of “a person acting as the computer.” It sounds a bit strange, but because of this small human gap, many hidden problems become easier to notice than in a real interface. It made me realize that a design process does not always need to focus on automation or digital tools. Sometimes leaving a bit of human messiness or uncertainty can make things clearer.