I got a couple of questions about discursive design and interaction design. I thought about how an interaction design can be a discursive design. I found it was because that the starting point is different. An interaction design, or product design, usually starts from hacking problems. While discursive design, starts from understanding the problem. Even they seem no difference from each other. As solving a problem is based on understanding the problem. But when we narrate a design we created, it is totally different. Problem-solving design is more logical and highly depends on the process. None solution oriented design depends on designer himself and the cultural impact. How you see the problem? What is people’s experience of your design? What your design can bring to people other than convenience or efficiency?

The narration of discursive design seems more objective and doesn’t need to explain the benefit that people can get from design, which makes a discursive design not measurable like the profits from app or web design. As a complicated design object, interaction design is more dependent. To figure out the system itself, interaction design needs more comprehensive thinking. And the thinking itself cannot be simply explained by simple ideas, which cuts down or hide some deeper or time-based influence of interaction design.

How an interaction design can be a discursive design? As a designer in working industry, we thought a lot about how to attract users, how to make the interaction efficient, and how to guide user’s behavior. To explore more, throwing all of these things away and starting to think about people’s mental experience, seem the only way to come up with discursive design or speculative design.

Comments(0)

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.