Change Is Hard, Especially in the User Interface

March 22, 2016

One of the most annoying things in life is when you go to the grocery store and notice they have rearranged the entire place since your last visit.  I always ask myself the question, “Why grocery store people did you do this to me?”  Part of the reason is to improve the shopping experience and product exposure, while the other half is to screw with customers (I cannot confirm the latter).  According to the Fuzzy Notepad with its Pokémon Evee mascot the post titled “We Have Always Been At War With UI” explains that programmers and users have always been at war with each other when it comes to the user interface.

Face it, Web sites (and other areas of life) need to change to maintain their relevancy.  The biggest problem related to UI changes is the roll out of said changes.  The post points out that users get confused and spend hours trying to understand the change.  Sometimes the change is announced, other times it is only applied to a certain number of users.

The post lists several changes to UI and how they were handled, describing how they were handled and also the programming.  One constant thread runs through the post is that users simply hate change, but the inevitable question of, “Why?” pops up.

“Ah, but why? I think too many developers trot this line out as an excuse to ignore all criticism of a change, which is very unhealthy. Complaints will always taper off over time, but that doesn’t mean people are happy, just that they’ve gone hoarse. Or, worse, they’ve quietly left, and your graphs won’t tell you why. People aren’t like computers and may not react instantly to change; they may stew for a while and drift away, or they may join a mass exodus when a suitable replacement comes along.”

Big data can measure anything and everything, but the data can be interpreted for or against the changes.  Even worse is that the analysts may not know what exactly they need to measure.  What can be done to avoid total confusion about changes is to have a plan, let users know in advance, and even create tutorial about how to use the changes.  Worse comes to worse, it can be changed back and then we move on.

 

Whitney Grace, March 22, 2016
Sponsored by ArnoldIT.com, publisher of the CyberOSINT monograph

Comments

Comments are closed.

  • Archives

  • Recent Posts

  • Meta