Page 79-end

“When you’re prioritizing features, remember that users value features that relate to their everyday experience of a product.”


I can relate to this comment in regards to the project we are working on and from general personal experience. When there is a feature that is created, it needs to solve a user problem that is essential for the core of the product. A lot of initial ideation that me and my partner had in the initial stage of our project were just abundance of features, which we later found to be a bad idea. One of the people I interviewed said “the weather app should be a weather app and nothing else” which directly speaks to this quote. When a product has one specific thing that it is really good at, adding random things just to have theme is a bad recipe. I personally experience something similar with Facebook right not. I have always used Facebook for its main purpose, to communicate with friends, and follow up on people or events that I am interested in. When I open facebook or facebook messenger right now, there are just so many new things added and cluttered everywhere, mingling with the rest of the content that you really care about. I find it very distracting, and overall a bad experience.


“Whenever a user has to correct an error, it breaks his concentration and makes the experience feel more complex.”


This quote made me think of one thing immediately. Setting up a new password! There are still so many websites that have you think of a password, enter it, and wait for the website to load, only to tell you that your password does not meet the minimum requirements. It is a very frustrating and long process because it order to figure out what works you have to see a dozen error messages in red. Thankfully some websites have an improved system where little requirement ticks get marked up in green as you are entering your password. This way you are aware of whether you are doing it right or not and it speeds up the process so much.


“Focus on solutions that completely meet users’ high-priority goals. Only then move on to the lower-priority goals.”


This thought can be especially important when we figure out what to prioritize on our mobile app. What users see and interpret first, should be the solution to their high priority goals, the information they are there to find. Only then can additional information appear, if it solves a lower-priority goal.
Colborne, Giles. Simple and Usable Web, Mobile, and Interaction Design (Voices That Matter) (Kindle Locations 720-721). Pearson Education. Kindle Edition.

Pages 1-79

“The more features you add, the less chance you have of coming across a new feature that is of real value to someone.”

I find meaning in this quote by connecting it to our research experience so far. We started off with a bunch of ideas that were pouring out, and that’s all right. But then we looked at competition and saw that other people have though about the same ideas. But what did some of them do? They squished so much information, and so many features into one place. This clutter makes all of these ideas loose value because so many of them are not important to the user and would not be utilized. I can conclude that, it doesn’t matter if you have a lot of ideas if they are not functional and do not solve a problem that the user has.

“Removing options, content, and distractions lightens the load on users so they can focus on getting the job done.”
During our project we came to a point where we put as a priority to display only customized information and to display it only at the right time. Irrelevant information, and scrolling through topics and options that are not of your interest makes you loose patience, get frustrated and really just wastes your time. During our competitive research we encountered an app that seemed to have anything you can think of about weather. It would show you a radar, a map, news, photos, it would even show you a section about hurricanes with a message “these is no threat of hurricanes at the moment” even though you are located in an area where there are never hurricanes. You can see information about pollen, even if you are not allergic. All if this content can be removed because it only makes it hard for the user to find the information that they need.
“Fortunately, when it comes to designing for simplicity, the key emotional need is for users to feel that they’re in control….Secondly, they want to feel in control of their lives.”
The author is right, we should not interfere with people’s emotional need to be in control. Psychologically we demand control in each part of our life (love, social groups, rules and routines). In order to feel in control, we have the need to understand how things work and be able to predict what will happen. Simplicity leads to less need for instruction and support, makes it clear what we can do, what the abilities and limitations are.
Colborne, Giles. Simple and Usable Web, Mobile, and Interaction Design (Voices That Matter) (Kindle Location 168). Pearson Education. Kindle Edition.