Let me explain my experience in a super market. I went to Trinetra super market recently where I noticed one of the staff members innocently obeying to the system‘s bad behavior. I was standing in queue to get my turn but he was taking more time than usual. So I went to see what’s wrong with him.
The barcode (RFID) device was not functioning; therefore he was manually entering all the items in his system to print the bill. The application was punishing him for not having the RFID devise working. He had a touch screen monitor so he was not feeling the pain with multiple touches he was doing with it, but as an Interaction Designer the bad behavior of the tool grabbed my attention.
He has to invoke the calculator (1 touch), enter the item number (10+ touches) then price and quantity (few touches) and submitting it to the list of items (final touch) then he could see it in item list. He has to repeat the same process from the beginning to the end for adding remaining items. Calculator window should ideally stay after adding an item to the list for allowing him to add another, but makers have thought that RFID device would fail to recognize items when the item is not stored in their database. In this context it is absolutely correct. But what if RFID device doesn’t function? This context maker might not have thought I guess, so user and customers has to scarify their valuable time. Therefore Usability Test is very crucial to find such missing gaps in the product. This is just one finding. We can arrive at many more interesting findings while conducting usability test in a real scenario by observing user performing their tasks.
The barcode (RFID) device was not functioning; therefore he was manually entering all the items in his system to print the bill. The application was punishing him for not having the RFID devise working. He had a touch screen monitor so he was not feeling the pain with multiple touches he was doing with it, but as an Interaction Designer the bad behavior of the tool grabbed my attention.
He has to invoke the calculator (1 touch), enter the item number (10+ touches) then price and quantity (few touches) and submitting it to the list of items (final touch) then he could see it in item list. He has to repeat the same process from the beginning to the end for adding remaining items. Calculator window should ideally stay after adding an item to the list for allowing him to add another, but makers have thought that RFID device would fail to recognize items when the item is not stored in their database. In this context it is absolutely correct. But what if RFID device doesn’t function? This context maker might not have thought I guess, so user and customers has to scarify their valuable time. Therefore Usability Test is very crucial to find such missing gaps in the product. This is just one finding. We can arrive at many more interesting findings while conducting usability test in a real scenario by observing user performing their tasks.
1 comment:
Hello. This post is likeable, and your blog is very interesting, congratulations :-). I will add in my blogroll =). If possible gives a last there on my blog, it is about the GPS, I hope you enjoy. The address is http://gps-brasil.blogspot.com. A hug.
Post a Comment