Chapter 1 Summary and Online Reading (original post: January 30, 2020)
The UX book that I will be using for class reading is “Killer UX Design: Create User Experiences to Wow Your Visitors” by Jodie Moule. UX is short for user experience, and is based around computers and the internet. The book defines it as a series of interactions that a person has with a specific product, service, or organization.
Moule also brings up the methodology for user-based design systems, and the remaining seven chapters of the book will be based all around this method, with the chart found below.
There’s also qualitative and quantitative research as methods for testing during the UX process: quantitative research looks at the actual behaviors of clients/users in order to get an understanding of why they do what they do, and quantitative focuses on mass data collection and analysis themes in order to make assumptions regarding human behavior. In order to dive into UX research, the person must also be able to put themselves in other people’s shoes in terms of what they would like and how the user would use the project (if they like it or don’t), which requires empathy.
This first week of class also saw me reading another article for class, this one from an article that talks about UX. Basically it’s a little re-hash of the introductory chapter that the class read, but it does go in-depth as to what UX Designers do, which is that they must be general with a high-level understanding of various aspects in order to make the design/aapp/technology suitable and meets the needs of the user.
The article also list five steps as a good way of developing a successful UX design (the article says four, but there is a fifth step inserted in — obviously a typo on the author’s part): I think the first step is really important, which is to pay attention to the products that are of daily use. Any product that offers something that needs to be improved is a sure way of letting someone know that a) this product needs to be updated and b) this product needs to be of useful benefit to either me or anybody else that sees the potential use of a product’s upgrade/another app.
Finding a problem that interests you, start making designs and getting it in fromt of them, and recording what you have learned are the other four steps that the author discusses.
Hopefully this journal entry and others will come in handy when we begin our group project in a matter of weeks.
Moule also brings up the methodology for user-based design systems, and the remaining seven chapters of the book will be based all around this method, with the chart found below.
There’s also qualitative and quantitative research as methods for testing during the UX process: quantitative research looks at the actual behaviors of clients/users in order to get an understanding of why they do what they do, and quantitative focuses on mass data collection and analysis themes in order to make assumptions regarding human behavior. In order to dive into UX research, the person must also be able to put themselves in other people’s shoes in terms of what they would like and how the user would use the project (if they like it or don’t), which requires empathy.
This first week of class also saw me reading another article for class, this one from an article that talks about UX. Basically it’s a little re-hash of the introductory chapter that the class read, but it does go in-depth as to what UX Designers do, which is that they must be general with a high-level understanding of various aspects in order to make the design/aapp/technology suitable and meets the needs of the user.
The article also list five steps as a good way of developing a successful UX design (the article says four, but there is a fifth step inserted in — obviously a typo on the author’s part): I think the first step is really important, which is to pay attention to the products that are of daily use. Any product that offers something that needs to be improved is a sure way of letting someone know that a) this product needs to be updated and b) this product needs to be of useful benefit to either me or anybody else that sees the potential use of a product’s upgrade/another app.
Finding a problem that interests you, start making designs and getting it in fromt of them, and recording what you have learned are the other four steps that the author discusses.
Hopefully this journal entry and others will come in handy when we begin our group project in a matter of weeks.
Comments
Post a Comment