The article made me realise how much more engaging stories become when tension is added, and I agree that the “And-But-Therefore” structure is a simple but effective way to make messages stick. Before reading this, I hadn’t thought about how just listing facts (“and, and, and”) isn’t enough to hold anyone’s attention

The reading made me realise how airport security technology is designed around binary gender norms, which unfairly targets and humiliates people who don’t fit those categories. I agree with the author that these systems are not neutral—they reflect the biases and assumptions of those who create them, often making life harder for marginalized groups. This changed my perspective by showing how important it is to include diverse voices in design so that systems work fairly for everyone

Ko Chapter 10 explains how methods like heuristic evaluations and cognitive walkthroughs help find usability problems early, without needing real users. I think this is very helpful because it lets designers fix problems before spending time and money on user tests. This chapter made me see how careful analysis can make designs better and save effort later.

I found Ko Chapter 9 really useful because it highlighted the importance of choosing the right empirical evaluation method for different design situations. I agree that relying only on expert opinions can miss real user problems, and the chapter made me think more critically about how I interpret usability data.

I found Chapter 7’s explanation of interface design really insightful, especially the focus on how every decision about inputs and outputs can impact users differently. I agree with the author that designers have a responsibility to think about diversity and inclusion, like when setting default languages or considering accessibility. This chapter made me realize that even small design choices can have big consequences for different groups of people, and I appreciate how it challenged me to think more critically about who is served by the interfaces I use and create.

I really liked how Chapter 6 emphasized that prototyping is all about learning and making decisions, not just about quickly building something. I agree that it’s easy to fall into the trap of thinking you should just start coding, but prototyping first can save so much time and effort by helping you test your ideas early. The range of prototyping methods described-from sketches to Wizard of Oz-was especially useful, and it made me realize how flexible and creative the design process can be.

Chapter 8 by Ko made me realize that feedback works best when it’s helpful and comes from someone who knows what they’re talking about, not just someone being vague or negative. I agree with the idea that good feedback should include both positives and negatives, like the “hamburger” method, because it keeps things honest but respectful. The chapter also changed how I think about what makes a design “good.” I now see that it really depends on the situation and what values matter most, which I hadn’t thought about before.

I liked the part where Ko talks about how everyone is creative, but we often stop being creative because of negative feedback from others. I agree with this, I’ve had times where I didn’t share ideas because I was afraid of being judged. It was helpful to read that creativity is something we can practice and get better at. It makes me feel like I don’t have to be “naturally creative” to come up with good ideas.