User Research and Design
Required Readings
- It’s Not Just You: Bad Doors are Everywhere (Video)
- Contextual Design, chapter 3: Principles of Contextual Design (on Canvas, under “Files”)
- Rapid Contextual Design, chapter 4: The Contextual Inquiry Interview (on Canvas, under “Files”)
- Contextual Design, chapter 17: Prototyping as a Design Tool (on Canvas, under “Files”)
- Usability Professionals Association Code of Conduct
All three readings are available on the Canvas page for the course (under “Files”)
Optional Readings
- Menlo Report
- Protecting People from Phishing (Focus on the evaluation)
- You’ve been warned (Focus on the methodology)
- Getting users to pay attention (Again, focus on evaluation methods)
Summary + Question
The three core readings for this week are all about standard / traditional methods for doing user experience work. They all come from an approach called “Contextual Design”, where the UX professional recognizes that users experience technology “in context” – they use technologies to accomplish things in the context of their lives and work. User experience designs, then, need to work for people in the context of their lives. So to ensure that designs work in the context of people’s lives, we have to understand what people are trying to accomplish and what their lives are like, so we can design appropriately.
However, last week we discussed the distinction between “production” tasks – users primary tasks – and “enabling tasks” that users don’t really want to do, but have to to get their primary tasks done. The contextual design readings all focus on designing production tasks. However, as we discussed, security is an enabling task (or secondary task).
For your summary, please think about this distinction. What parts of contextual design do you think can still work for designing security tasks as secondary / enabling tasks, and what parts of contextual design do you think no longer work? For your summary for this week, try to answer this question.