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.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s