- Jan 2025
-
faculty.washington.edu faculty.washington.edu
-
good critique
I found this passage insightful, especially in how it highlights the balance between structured critique and domain expertise. While peer feedback can be valuable, nothing truly replaces deep knowledge of a field. The discussion on design justice also stood out, bringing in stakeholders makes sense, but participant response bias can limit honest critique. The idea that good design depends on context is important. I once saw how different users interpreted the same design in completely different ways based on their needs and experiences. This reinforces the need for both expert insight and real-world feedback in the critique process.
-
-
faculty.washington.edu faculty.washington.edu
-
100th idea
This made me think about how important it is to keep generating ideas and not stop at the first one. Externalizing ideas really makes sense because it helps uncover flaws and sparks improvement through feedback and reflection. I also liked the point about surrounding yourself with rich context to inspire creativity. It’s a reminder that great ideas don’t happen in isolation but rather they come from constantly building, critiquing, and improving. The thought that your best idea might be your 100th one is motivating because it shows how persistence and iteration lead to better outcomes.
-
-
faculty.washington.edu faculty.washington.edu
-
One simple form of knowledge is to derive goals and values from your data.
I find it really practical to focus on understanding goals and values from data. Instead of just listening to what people say, it’s about identifying what they’re actually trying to achieve. For example, when people talk about renting, some care about affordability, others about saving time, or accessibility due to a disability. I think recognizing these goals helps in designing something that truly addresses their needs. It reminds me how important it is to dig deeper and create solutions that align with people’s real priorities.
-
-
faculty.washington.edu faculty.washington.edu
-
This approach, called Contextual Inquiry, is part of a larger design approach called Contextual Design11 Beyer, H., & Holtzblatt, K. (1997). Contextual design: defining customer-centered systems. Elsevier. .
Contextual inquiry feels like a refreshing way to understand people’s behaviors by observing them directly in their natural environment. I like how it emphasizes collaboration, with the participant as the expert and the researcher as the learner. It seems more authentic than relying on interviews alone, as it captures real-time actions and decisions. That said, its time-intensive nature and limited generalizability are definite challenges. I also appreciate how adaptable this method is, like during the pandemic when researchers had to observe people working from home. It’s a method that feels immersive and insightful despite its constraints.
-