Showing posts with label heuristics. Show all posts
Showing posts with label heuristics. Show all posts

Sunday, November 19, 2023

Emotional design, mental health, and user experience, inspired by the Yale School of Art

By Qiyun Feng,

Qiyun Feng is a data scientist currently working at Innovations, Science and Economics Canada. He writes out of pure interest in psychology and technology. You can reach him by his email or his LinkedIn.

A journey of user experiences

There’s an infamous website, the Yale School of Arts front page, which features the most absurd combinations of visual assets and page placements. It conforms to none of the modern design languages, and it almost evokes a sense of the 90s and 2000s with the design language. Despite these characteristics. There are two feelings that this website evokes. Being born in the 90s, I have very deep sense of nostalgia for the olden days where websites were laid out into sitemaps, and we had to navigate through endless hyperlinks to find what we were looking for. The other side of me groans and wants to turn this website off immediately.

A journey of user experiences

Figure 1: Front page of the Yale School of Art

There’s a term in the industry that dubs the culmination of design and customer experience as user experience. It is known by many names throughout time, user centred design, usability, user experience but they are all about the same thing.

Don Norman, the creator of the term usability, defines it as a cohesive integrated set of experience from initiation to the disposal. It is designed to fit that entire experience together seamlessly. The International Organization for Standardization defines use experience as “A person’s perception and responses that result from the use or anticipated use of a product, system, or service.” Steve Krug, the writer of the book, Don’t Make Me Think, considers user experience to be an amalgamation of a dozen different disciplines from interactive design to visual design, to content management, coming together to make a product.

There’s very little disagreement on what it means to create a good design. You need a good product with good functionality, and you need different talents coming together considering various parts of the product so that it fits like a glove to the use case.

However, I want to look at it through a different lens. What about the actual emotional and physical experiences. How about looking at it from the lenses of the user and the customer. While there is an importance to the immediate response of the user, and the reaction of the user, the focus of user design generally seems to end at that point. We want to look at it from the perspective of emotional designs.

Emotional design and UX

Emotional design can be divided up largely in to visceral, behavioural, and reflective, according to Don Norman. Visceral is the physical appearance of a product. Obviously, everyone wants the product that looks “nice” but nice can be defined in a variety of ways. The second is the behavioural design. How usable is a product or how effective is a product is generally the question we ask to figure out how well a product is designed in this category. Finally, there’s the reflective designs, the things that makes the user think back about their experiences.

Using an adequate mix of these different designs is the key to creating a user experience that makes the user appreciate the product. Let’s go back to the front page of Yale School of Art for a demonstration of this.

If we were to analyze this page, solely based on what we would see, the visceral design of this is terrible. There’s no cohesive design language. The fonts are all different. It’s not reactive so everything is left aligned, there’s a different background on every page making it extremely difficult to understand. By this alone, it would seem like this is a terrible design.


Figure 2: A sitemap of the Yale School of Art

Let’s look at the behavioural design of the website. From the behavioural aspects, it would seem all the functionalities are there. There’s a navigation bar, the animations can be paused, most of the assets are in the form of cards with a details button. They even have something that tends to be missing from some websites, a sitemap! From this perspective, this is a functional website though we would have to deduct points for their accessibility.

Finally let’s look at the reflective design of this webpage. On the side of the webpage, there’s a quick blob of text explaining the origin story of the website.

“This website exists as an ongoing collaborative experiment in digital publishing and information sharing. Because this website functions as a wiki, all members of the School of Art community—graduate students, faculty, staff, and alums—have the ability to add new content and pages, and to edit most of the site’s existing content.

Content is the property of its various authors. When you contribute to this site, you agree to abide by Yale University academic and network use policy, and to act as a responsible member of our community.”

This finally makes sense. This is an arts project that is based on the collaboration of the Yale School of Art community. The intent is not to create a website for the public in the traditional sense but to create a piece of modern art that is available to be browsed by the public. Finally, this makes sense.

One of the importance of modern art is experimentation and we are obviously witnessing a large-scale experimentation that an entire community is undertaking individually and witnessing the result. If this was a commercial product it would never work but as a piece of modern art, it will live on.

How does mental health play into this?

There’s a copious amounts of mental health application out there now. The majority of which falls under these following categories.

1. Online therapy sessions: Basically, a glorified chat client that enables text-based or even video-based conversations with a therapist.

2. Meditation: Basically, a glorified audible that contains large amounts of meditations that is aimed to make the user use meditation

3. Journaling: Basically, a prompted notebook that captures your moods and provides feedback.

If we applied emotional design to all these applications, all these applications have an immaculate design. They certainly have good visual artists. They are also very functional in terms of the usability aspects. The chat client does what it is supposed to, the meditation is certainly calming.

The challenge is the reflective aspects. 

There’s a variety of different mental health issues. To give a brief overview, here are a three. ADHD, or Attention-Deficit/Hyperactivity Disorder, is a mental health challenge where the person suffers from persistent or hyperactivity-impulses that interferes with functioning. Depression is a mood disorder that causes persistent feeling of sadness and a loss of interest. Anxiety disorders is a group of mental health disorders characterized by significant feelings of anxiety and fear.

People with ADHD and Depression faces a completely different challenge from those with Anxiety. People with ADHD and depression are more likely to never use the application or product in the first place whereas people with anxiety are at risk of using the application either too much or getting anxious of the very thought of the application itself. 

What is apparent is that the designer of any given application, for mental health needs to provide accommodations for people that are neural-divergent. For example, for those that are ADHD, they will need a reminder to do the activities in this application when they are less busy in their schedule. ADHD is blindness to the time and thus the application will only be successful if they help guide ADHD time manage their therapeutic process. For those are that depressed, on the other hand, this is a case where they need impulsive breaks and a strong external force to break them out of arguing against themselves. This is where the application will require strong reminders and enforced actions to make the individual partake in the therapy process. 

The only way that the mental health therapy works is the have the reflection design built into the process and create an environment where those that are struggling from mental health can leverage the functions of the product to cater to whatever their usage is.

How to leverage this in my designs?

There are a couple of philosophies of design that should be implemented but it is worth mentioning the one that is fundamentally the most important, which is testing whether your application made a positive impact with the user. The marker of a positive impact should be positive mood changes for a prolonged time and the sustained usage of your application. You can only verify this through user testing and user survey.

There is however a couple principle that is necessary to build an application that caters to people that are neural-divergent. The first of the principle is to follow nelson’s heuristics number 7, provide flexibility and efficiency of use. Provide people the ability to set up their schedules for integrating the application for their use. If the application is distracting, people with ADHD should be able to set the time frame they use the application. If it’s people with depression, then depending on whether your application is for therapy, or for other tasks, you will want the application to show customized notifications to enforce the usage of the applications. 

The second important principle is preventing errors, creating a consistency and rules for the customization that people can make in an accessible way to those that are neural-divergent is extremely conducive to the reception of the application. If the customizations are standardized, the range of states the system can be in is standardized and will drastically reduce the likelihood for errors. This is necessary so that people can expect the same customization to function the same way facilitating a community to develop.

The third important aspect is helping users recognize, diagnose, and recover from errors. It is critical to let the users know whether what they did was a slip or if it was a mistake with the system. If it is a slip up or a mistake from the user’s part, then they need to be able to fix it easily. If it is a system mistake, then the user will also need to know that it wasn’t the user’s fault. For those that are neural-divergent, it is simple to be critical of themselves when mistakes or errors occur, and we want to maintain a positive reinforcement for the users in the application.

Finally, allowing the community to be personalized is another important step to allowing the user get help. Yes, having help and documentation is a necessity, but for this day and age, having some sort of chat, or bulletin board where questions can be asked, achievements can be shared, is critical to the success of any platform. Having that ability will simplify help and improve the feedback process.


Figure 3: Communal management of the page

If we bring back the Yale School of Art, these criteria are met perfectly. They provide the maximum flexibility, which is allowing any student, faculty members and professors to contribute to their page. The website is basically a blog with custom stylings. They have both instructional tools and error prevention by design with sitemaps for those finding it challenging to navigate the site. Finally, the entire website is essentially a community bulletin board. For those purposes, this ends up being a great reflective design that not only has the community members examine art in a nuanced way, even if it is not built specifically to cater to the neural-divergent individuals.

Conclusions

Mental health is a topic that has gained a lot of traction over the period of covid, and more people are becoming aware of the individual differences that exists. While this has been fantastic to the understanding and acceptance of those that faces mental health challenges, this has also highlighted various challenges in design faced both in general applications and mental health applications.

This calls for the need of a more intricate investigation into what is done until now.

In the end, I leave you with a simple thought experiment. Using this game here , please leave me a comment on from a scale of 1 to 10, how furious did this game make you. Now I want you to imagine this is what it feels like when you are neural-divergent. People that are neural-divergent face this kind of design as a normality. 

I hope you don’t break your computer out of pure computer rage, and I wish you the best on your journey to good design!


Saturday, March 6, 2021

Usability Evaluation of AirIndia Website

 By: Archa Jain

 Introduction

The website "Airindia.in" is one such system that helps users to book flight tickets in advance over the internet using online payment methods from anywhere in the world. When purchasing a flight ticket, it offers users a variety of options, including the ability to choose between various ticket classes, such as economy, business, and first-class, as well as the ability to choose their preferred seat for their desired flight. This removes the need for the customer to purchase flight tickets in person at the airport. User values feature, but that is not the only thing they seek in software. The usability of the software is another such aspect that the user takes into account. The usability of an application is determined by its user interface, in addition to its functionality. If the software is difficult to use, it can lead to a poor user interface and applications that no one wants to use. 

In this blog, I will discuss some of the major usability problems discovered using various methodologies like heuristic evaluation using Jakob Neilson’s 1994 heuristics and think-aloud user testing of the Air India website. It also mentions the heuristics that are broken in those issues. Furthermore, it suggests some fixes for those issues that developers can use to make the software more usable. Then finally all the findings and the result are concluded.

Usability Issues and Recommendations

1.  Login page does not work and does not even provide any feedback or error message.

To login into a user account, the user needs to click on the login hyperlink on the home page. For logging in to an account, a user needs to fill in the registered email address and the password. Along with that, the user is required to fill in the captcha and click on the login button. On clicking the login button, only the page refreshes and the user does not get logged in even if the information provided is correct as shown in figure 1. Also, it does not provide any kind of feedback or any kind of error message about what is wrong.

This issue violates the following heuristics:

§  Heuristic #1 –Visibility of system status

§  Heuristic #5 –Error Prevention

§  Heuristic #9 – Help users recognize, diagnose, and recover from errors.

 

Screenshot of user performing Login

Figure 1: Screenshot of the user performing Login.

Recommendations 

There are two things that can be done to resolve this problem. 

  • One involves resolving the issue by improving the system to accept the login details and allowing the user to login into the website. 

  • Other involves making a clear error message if any fault occurs and with a relevant solution on how to proceed further from that specific issue.

 

    2.     Unclear input fields in enrolling/user registration form.

To create a new user account, there exist two options, either click on the login hyperlink on the home page and then click “New Users – Register” or by directly clicking on the “Enroll” hyperlink on the home page to access the registration form to create an account. While creating an account, the user needs to fill a huge form with all of them set as mandatory fields. One of the fields is “Name on Card” to fill as shown in figure 2, which does not specify any information on which card they are referring to. This kind of field made users very confused about whether to put a full name or just first name as some users mentioned they had some cards with full name on them and some with just first name.

This issue violates the following heuristics:

§   Heuristic #2 – Match between system and real world

 

Registration field on the Enroll page

Figure 2: Registration field on the Enroll page.

Recommendations

The solution has three parts for this problem. 

  • First one involves showing the descriptive or clearer label for the field so that user can clearly understand about which card the system is asking for. 

  • Second one includes a place holder with an example of the text that user needs to enter in the field. 

  • Last but not the least, a validation to check the value is not garbage and it matches the username that has been entered by user in other fields like first name, middle name, and last name. Also, show the error message if the validation fails with the description of what the exact error is and what user needs to change in it to make it correct. 


3. Country selection dropdown does not perform any action.

If a user wants to change the currency of the tickets on the website, then he needs to change the country from the country dropdown list on the homepage as shown in figure 3. But when the user changes the country to the UK to get the ticket prices in pounds, either the page just refreshes or sometimes it navigates to the error page as displayed in figure 4. There is no feedback provided to the user when the page refreshes. If the user continues to search the flights, he/she does not see the prices in the expected currency.

This issue violates the following heuristics:

§  Heuristic #1 – Visibility of system status

§  Heuristic #5 –Error Prevention

§  Heuristic #9 – Help users recognize, diagnose, and recover from errors

 


Country dropdown menu on home page

Figure 3: Country dropdown  menu on home page


Error message on changing the country.

Figure 4: Error message on changing the country.

Recommendations

There can be 2 parts to the solution for this problem. 

  • First is to show a message with the name of the country it is changed to and the name of the country it is changed from when the country changes, along with displaying correct country flag as it is a part of their design. 

  • Other part is to display the prices of the flight tickets in the currency of the selected country when user searches for any flight. 

 

4.  The Navigation menu covers the entire screen.

The navigation menu displayed on the home page helps to provide relevant paths or links to the users for easier accessibility. But it also hinders the entire aesthetics of the website as well by covering the whole display of the screen as displayed in figure 5. Also, there is excessive information displayed in the dropdown along with wastage of a lot of space (highlighted in the figure) of the navigation menu which is not mandatory to be shown there. Also, the navigation menu contains huge images (highlighted in the figure) which should not be included in the menu structure.

This issue violates the following heuristics:

§  Heuristic #4 – Consistency and standards

§  Heuristic #8 – Aesthetic and minimalist design

 



Navigation menu on the home page

Figure 5: Navigation menu on the home page

Recommendations

There can be a solution for this problem, which involves reducing the content in the navigation menu. Only display relevant links in the list without additional information, irrelevant images, and excessive space. Also, the width and height of the navigation menu should also be minimized or adjusted as per the content so that it should not cover the entire screen.


5.       Flexible dates radio button does not perform any action.

When the user searches for a flight, the user needs to fill out some of the specification related to the flight on the home page like from (the place from where you want to take a flight), to (the place you want to go), and some other details as well as shown in figure 6. There is one radio button on the form labeled as flexible dates which are selected by default (highlighted in the figure). When the user clicks on the flexible dates radio button, nothing happens. It does not get unselected nor even shown as disabled. Also, no error message or feedback is provided to the user when it is clicked.

This issue violates the following heuristics:

§  Heuristic #1 – Visibility of system status

 


Flexible dates radio button in the booking area of the home page

Figure 6: Flexible dates radio button in the booking area of the home page

Recommendations

One such a solution for this problem can be done by making the flexible dates as a checkbox instead of a radio button. As there can be two options in this case the user wants to search with flexible dates, and he does not. For a field like that, a radio button should not be used. Radio buttons are more useful in case of multiple mutually exclusive options. Also, the radio button is unselected only when another mutually exclusive option is selected.

 Conclusions

The website "AirIndia.in" is used by millions of people all over the world. When anyone wants to fly, they connect to this system to book a ticket for their preferred flight. However, after conducting the heuristic evaluation and think-aloud user testing, it was discovered that the application has several issues that can impede the user experience. There were several problems on the home page itself, leading to the user's decision not to use the website based on their first impression. As a result, with the explanation of the problem in the above section, some suggestions for resolving certain issues have been given to make the job easier. To conclude, several other improvements are needed to make the “AirIndia.in” website more user-friendly and accessible.

 

References

  1. Air India Ltd, Air India, [Online]. Available: http://www.airindia.in/. [Accessed 15 February 2021]

  2. J. Nielson, "10 Usability Heuristics for User Interface Design," Nielsen Norman Group, 24 04 1994. [Online]. Available: https://www.nngroup.com/articles/ten-usability-heuristics/. [Accessed 12 02 2021].

  3. J. Nielson, "How to Conduct a Heuristic Evaluation," Nielsen Norman Group, 1 11 1994. [Online]. Available: https://www.nngroup.com/articles/how-to-conduct-a-heuristic-evaluation/. [Accessed 12 02 2021]

 

 

 

Monday, March 28, 2016


Usability Evaluation: Uber

By Rawan Bahmid

As most people know, Uber provides a enhanced form of taxi service for which anyone can be a driver. It provides private transportation options in such a way that benefits both consumers and drivers. The company uses multiple media to deliver its services [2].


We evaluated its consumer mobile application to asses its learnability, simplicity and discoverability. The evaluation was been performed on the Uber Android application version 3.93.4, which was the latest available version for Android 5.1.1 when the evaluation started. Two evaluation techniques were used, heuristic evaluation using Nielsen’s 1990 [1] principles and cognitive walkthrough.

The evaluation covered three important tasks, to determine the usability problems and difficulties that might face a user, to provide some solutions, and ultimately to improve the user’s experience.

Task 1: Request Uber
This feature allows the user to choose the car size, get the estimated fare and order a car.

Success scenario:
  1.  Enter pickup location
  2. Choose UberX or UberXL
  3. Check car capacity
  4. Enter destination
  5. Tap GET FARE ESTIMATE
  6. Request Uber
  7. Choose payment method
  8. Enter promo code (if any)
  9. Confirm the request
Failure scenario and recommendations:

Step 3, 4 & 5
Problem 1: the choices are hidden in the bottom of the page, one has to scroll down to find it, however, there is no sign or clue to scroll down. See Figure 1.
Figure 1 Request Uber: Hidden options

Issues of hidden options in Step 3, 4 & 5 could be solved by making clear to the user that there are more useful options in the bottom of the page. It would be better if the maximum car capacity of people is shown graphically. And if more expressive display of a currency sign is shown beside the text GET FARE ESTIMATE.

Step 6
Problem 2: The term SET PICKUP LOCATION is ambiguous and confuses the users. Should they enter the the pickup location again which means the first entering was not successful. But the address is in the PICKUP LOCATION field!! Or Is the entered location not correct? Or it might be for confirming the entered location.

Problem 3: In some times and places there are no available Uber cars. However, the user can request a car and keep waiting for a request that would never be confirmed. check Figure 2.
                                           
  Figure 2 Request Uber: No available car

Problem 4: In rush hours and when there is a lack of the available cars, a message would show that there will be a surge pricing. User could choose NOTIFY ME IF SURGE ENDS. However, user will not receive any kind of notifications even when the surge ends, see Figure 3.

Figure 3 Request Uber: Surge pricing


A clearer and meaningful term should be used such as “REQUEST Uber” or “REQUEST CAR”. Moreover, restrict the car requisitions to be used and activated only when cars are available. And provide feedback or message to the user explain the situation. Enhance the notification system as well.

Step 8
Problem 5: The option seems to be inactive because it is gray and users might think it is restricted and can not be used, see Figure 4.
 
           Figure 4 Request Uber: Promo code


Better to colour the outline of the text to show that it is active. And fill the text with a colour when a promo code is being used.

Problem 6: The cars’ slider may confuse users; they might use to enter the addresses because its like a path form a place to a place. They would first enter the Pickup location, move the car to the next point and enter the destination.

This could be solved by having radio button to chose the preferable car instead of the slider. Check Figure 5.
   
                       Figure 5 Request  Uber: Redesign


Problem 7: Beside all the analyzed issues, the application only supports portrait orientation. It does not allow page rotation, which is helpful when following the car’s movement. 

Task 2: Cancel a request
A car request can be canceled before and after the completion of the request. Scenario 1 illustrates the process of the cancelation before the request is being completed. Whereas scenario 2 states the situation of cancelation when the request has been completed.
Success scenario 1:
  1. Hold X button to cancel 
Failure scenario 1 and recommendations:

Step 1
Problem 8: The progress of the cancelation request is shown to the user, but it is not confirmed when completed. After cancelation the confirmation of car request page appears, which confuses the user as to whether or not the cancelation has been done.

To avoid this confusion, provide  descriptive feedback that states that the request has been successfully canceled. 

Success scenario 2:
  1.  Tap on CANCEL
  2. Confirm cancelation

Failure scenario 2 and recommendations:

Step 1
Problem 9: The CANCEL option is hidden. User has to scroll down to find it. However, there is no clue that there are some available options further down the page. See Figure 6.

Figure 6 Request Uber: Hidden CANCEL

Step 2
Problem 10: No feedback is provided when the request is canceled. Therefore, user has to go to the History page to make sure that the request has been canceled.

To allow users to use this feature correctly, make the CANCEL button visible and accessible by giving signal in the page that there are options when scrolling down. Moreover, make sure to provide useful descriptive feedback when the cancelation process is completed successfully.  



Task 3: Add an address to Places
This feature allows user to add their common to visit places to a list. Hence, they just type the shortcut in the destination field when want going there, instated of entering the full address.

Success scenario:
  1. Main menu
  2. Tap Settings
  3. Tap Add HOME or Add WORK
  4. Enter destination

Failure scenario and recommendations:

Step 3
Problem 11: The list is very limited, only two addresses could be added to it. Moreover, names of the places can not be changed. This is not expressive when adding, for instance, the address of the university under the name HOME and will require the user to remember each name is for what address. Check Figure 7.

          Figure 7 Add Places

Step 4
Problem 12: When the address is correctly added to the list, no feedback is shown to the user.
To make this feature more useful, allow the user to enter as many address as they need and name them based on their preferences. Furthermore, provide feedback when the entered address has been added to the list. Figure 8 states a recommended redesign of the PLACES.


Figure 8 Add Places: Redesign

Form the analysis we can conclude that the issues of the application are because of the invisible functions, limited options and the structural mistakes. 

References
  1. Nielsen, J. & Molich, R. (1990). Heuristic evaluation of user interfaces. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI '90), Jane Carrasco Chew and John Whiteside (Eds.). ACM, New York, NY, USA, 249-256.
  2. Uber (company). Wikipedia. Retrieved 20 March, 2016, from https://en.wikipedia.org/wiki/Uber_(company)