I think this point makes a lot of sense because in order to make the reader hooked about a solution or product. You have to make sure you highlight and emphasize the problem it solves. Everyone has problems and making sure you appeal to a relatable problem that a lot of people have is essential to advertising your product.

I feel like this statement is very true. An example of this that I can think for example is in politics. Many politicians may make policy decisions with interests that may not align with their citizens. I think this point is important because it shows that we need to ensure that our design decisions help reflect what our stake holders are looking for.

Ensuring that designs are consistent with concepts users already know makes sense. I see a lot that websites will be designed in very similar ways, having navigation bars in the same location, account information being available in the same corner, and more. This makes sense because if there was inconsistency in how different websites provide features, then it would be very hard to be able to figure out how to use the website.

I think having participants vocalize their thinking as they test their thinking makes complete sense. By doing so, you can gain insight on what part of the design makes people confused and do other actions than you expected. I recall being asked to perform in a usability test for my Brother who was working on a website for his capstone. Reflecting back, vocalizing my thinking to my brother was really helpful to him, because he saw where the design confused me, and he also gained insight on the design through my comments of what I felt like it was lacking.

This makes sense because even if you have a general idea of what your solution and try to make a user interface. It'll end up weird if you haven't even planned out what you need in order to achieve your solution, inputs etc. In my mind this makes sense because ill design something and realize i need certain functions that dont fit in my design, which tells me I should've considered them before making my design.

I agree that this is a pretty important thing to do, reducing the cost of prototyping. For example, when prototyping for a robot, my highschool robots team would often use cost-effective means of being able to test our ideas by using wood or reusing existing parts and materials as opposed to buying and gathering materials from scratch. Its okay to use worse parts and materials as long as the prototype is able to prove or demonstrate an idea

I think this example really shows a lot about how important wording is in constructing questions in a survey or interview. In this context, adding certain lines or words will lead people into feeling the need to choose a certain answer over another. I think it's interesting how there's so many different things you need to keep in mind when designing good questions. I wonder how long it takes for researchers/interviewers to get good at this skill throughout the course of their careers.

This statement makes a lot of sense to me because looking at competitors both gives you an idea of what doesn't work that you may want to avoid or fix in your solution, and what does work that you may want to incorporate in your solution. For example, I was experimenting once on designing websites, and I was very stumped on ideas. However, through looking at other people's mockups as well as looking at other websites as examples, I was guided into a direction of how I wanted to approach making my website and what features I'd want to add.

This sentence stood out to me a lot because it really is a process that everyone does in their daily lives. For example, students will review presentations and deconstruct them into notes that they can follow. Personally, this makes me reflect on the process of learning human anatomy of an artist. As an artist, I found myself learning how to draw the human figure by deconstructing the human body into 3d shapes that I myself am able to understand.

This statement makes sense to me because there's a limit to which knowledge about general design principles can help you provide advice to other people. I think this statement makes me reflect back to when I did Robotics in high school. As a senior, I would look over my underclassmen's code and from experience, it would be impossible to give them meaningful advice on how to approach their problem without understanding the topic and how to code it myself.

I think this point was pretty interesting. This reminds me of how in class, we talked about how when brainstorming ideas, we need to unfilter out our ideas and let them flow out, because if we filter out our ideas, we may lose out on interesting ideas that can contribute to the bigger picture of how we want the project to look like. Plus, taking a little bit and looking back at the idea later can also add interesting insights that make it useful as opposed to just saying it's a dumb idea and forgetting about it.

I thought this explanation was very insightful. I probably personally would have just stated that "hey we want to do x". However, it makes sense why this isn't good, because you aren't explaining the real context to explain why you want to do what you want to do. You need to paint the picture of the problem first, then you can make others sympathize with your point and thus support you wanting to make a solution

This point was pretty interesting to me. It reminds me of the idea making sure you're not making leading, loading, or double-negative questions, because they will lead the respondent to thinking you're expect them to respond a certain way. I guess it makes sense why people take so much of an effort to design their interviews well, so that they don't lead participants into taking biased answers.

I agree with this statement. This connects back to my INFO 200 class last quarter where I was tasked for a final project with designing a website. In designing a webpage, we were told to think of different things we could add that would promote inclusivity, which really made me think a lot more about why we need things like accessibility features. For example, some people might speak a different language or not be able to see small text, so having settings so that you can modify the website to suit their needs is essential to creating a good user experience.