I really connected with this quote because it explains why storytelling is so effective. I agree that stories help facts stick better, and thinking about it, most of the meaningful lessons I’ve learned in my own life came through someone’s story, not just raw information. The idea that stories act like “simulators for life” also stood out to me, because it’s true that hearing someone else’s experience can prepare us for situations we haven’t faced yet. This made me realize how much storytelling shapes the way we understand people, which makes it a powerful tool in design and communication.

I agree with this part. I think a lot of times, we design for people without actually putting ourselves in their shoes which can often not solve problems that we want to fix in the first place. I think has also made me reflected a bit that even though we have good intention in our design process or what not, it may not always lead to the proper outcome. This also made think about communites like my church community are are all volunteer based are left out of descsions that shape system they are expected to click through or navigate.

I really agree with this because when a system doesn’t show what it’s doing, I get confused or . I hate when I click something and I’m not sure if it worked, if I need to wait, or if something broke. Clear system status makes the experience way easier and reduces a lot of stress. It reminded me that even small UI choices affect whether users feel confident or lost when using something.

I liked how this part because i think a lot of people, including me, tend to feel judged when we try something new in front of others. This kinda push the responsibility back onto us as designers, which I think is more fair and also encourages better feedback.

It also reminded me how easy it is to assume user are thing wrong but in reality, if they are confuse, the design and interface didnt not pass and failed. This is what I also talked about in my essay for informatics.

Professor Amy makes a really good point because it talks about how small design choices like default choice can even reinforce inequality. This made me relize that how much bias can be built into everyday interfaces like on the devices we use. Like my own parents; since they only speak vietnamese, a lot of american interfaces are english by default which makes it confuse to look for the language option. This also reminded me that inclusive design isn't just about accessibility for people with disabilities but also about making sure products work for people with different language and cultural.

This quote stuck out to me as it talks about prototyping as a tool over a step to a final product. Ko talks about prototypes help designers to answer question and reduce uncertainty. This also shifted how I view my projects instead of taking these prototype as steps towards to final, I will now treat it as a tool to to test ideas and get feedback. I wish to also take this mindset towards other things outside of design too.

This line stood me as this really shows how people can see and interpret language easily even when researcher think that they are being neutral. I remember in INFO 300 that research should be as neutral as possible. I also agree with this because, the small wording in a conversation can make a break a conversation and that also applies here. Overall, this whole reading helped me see that making question needs to consider ethical thoughs in it.

I think this makes an interesting point and also added another perspective. Usually when I do competitive analysis, I would usually come up with potential competition in my mind but never make an actual list of competition and comparison. Also the text mentioned that this will keep your research guided. This also added another perspective that you can use your comparison and competition to help you stay in your lane and I think that this also makes your solution go towards something that will solve a problem.

I have to agree with professor Ko that good critique is a conversation over a single opinion. I've been in situations such as group project in my other INFO classes where people can simply say that that looks good or "I think you should fix that small..." without having proper reasoning. ALso the article mention the hamburger rule as it's not just about being nice, but about giving feedback that will help people or project grow. This reminded me that giving critical feedback is important and that also helping the other grow, Personally, I am very much open to critical feedback as long as the reasoning is good!

I really like this point as it reminded me of my own hobbies and creativity. As a photographer when I first started taking photos, I would often compared myself with those who have much more experience even though I was very much a beginner or even felt like I wasn't creative enough. Although looking up to others is good to get more inspiration and learn, I think that I was doing it to the point where it was hurting me more then i was learning. Over time, I realized that creativity and finding my own 'presets' just took a lot of time and practive. The more I experience with different styles of photography and editing styles, I started developing my own visions and editing styles. This reading reflected and how creativity isn't talent but it's also about ability to see different things and express it which i can take forward with this class.

I like this idea and concept of personas that professor Amy is talking about. To me, this made reflected and think back how important a person with proper credential make up for valid data if that make sense. Or in other words, its easy for us to use data that makes up generic user instead of important 'personas'. I know that using relevant and important data / personas is important but this does change my perspective a bit as I though persoans was another approach but now, I see persoans as something that should be taken highly into consideration as evidence for design.

This is a really interesting way the approach a 'problem'. To me when I am approaching a problem weather that is at school, work or anywhere, I would often approach in bits similar such as breaking it down and knowing where to tackle first but as professor Amy said in this quote, "They're tangled webs of causality which one might call wicked". This kinda changed my perspective a bit on how problems are often far more interconnected and not organized. This gave me a new perspective because I now see that problems are not always getting from point A to B or even like breaking down steps like I mentioned. This challenged me that sometimes, design is accepting what it is and moving forward with it such as having small improvement instead of one big fix.

I agree with professor Amy on this one. Usually when I do a group project or something creative and that it is geared towards multiple customers, I want to. seek as many perspective as possible. Not only that, but also being open to critical feedback and taking that forward and reapplying to your projects and design is important. Seeking multiple perspective can also give you a better idea or solution to what you want to get done or achieve.

This one of they things that spoke out to me in this . At my internship this past summer, one of the key values that I learned is to work backwards and put the customer first or that the customer is always right. After learning that, I could not really approach a problem without having to work backwards. Similarly can be said about design and in this paragraph: instead of jumping into conclusions, and making solutions right away, we should put the customer, user or human first and work backwards that we can design and create solutions that actually matter!