måndag 16 mars 2015

Think aloud

Yesterday i met with Kalle, a friend of mine to do a think aloud test of our application. Kalle is 22 years old and lives in Stockholm. However, he's only lived in Stockholm for about 6 months, originally being from the northern parts of Sweden. Because of this i figured he could maybe fit in to one of our target groups, tourists.

I started off by explaining what the application is all about, that you can find different types of museums based off interests & also find routes inside the museums, with the main focus to simplify the searching and also have all the information you need to plan a museum visit in one place.
I then told him to try out the prototype and also keep an open dialogue with me explaining his thoughts throughout the usage.


He started off being a little bit confused as to what the different icons meant, and tried looking for information on the different icons but couldnt find any. He then proceeded to click one of the icons and got taken to the next page (the convenience page). Here he told me that he kind of understood what we were trying to do and didnt seem confused at all. He said that liked that we had an estimated time function (but that it could use some more information and some better graphics), seeing as in this city, you really have to spare on time.

He then proceeded to the page with the suggested museums and said that this was the page that he liked the best and the one he understood the best.

All in all he gave me mostly positive feedback, he liked the idea alot and said that he thought it could be very useful, especially for someone who isn't familiar with Stockholm or is new in town.

I think that this think aloud and the feedback it gave did good and will help us (it was also very fun to do and interesting!), but at the same time it feels like we already knew these problems and that we already had plans to fix them. It was also useful just observing someones workflow with the application. I think that this way of gathering data from observations could be as important as actively asking questions and 'giving instructions' just because you get to see the user in their normal state, just how they would have used the application on their own.