week 10 NUDC: User Testing

Hello Again,

This week we had meetings with our stakeholder, Ali Lamb, as well as our technical adviser and academic mentor. Before they started testing our prototype, there were a few points we had to mention; the fact that they keyboard was not fully functioning, only an image, there were aspects we already knew we wanted to add such as the ‘rating other comments’ page and we also asked the users to think a loud throughout their testing. During our meeting with Ali, she noticed some alterations we could make to further improve our prototype, but also the details that she liked, for example the fact that the reward sticker reinforces brand identity for Streets 4 People. Her suggestions for improvement included changing the language we used on our introduction page from “there will be” to “one idea is” to suggest that the plans are still negotiable and to add more images of the before and after photos from different perspectives to give the user a clearer idea of the changes. She suggested having overlayed before and after photos and having a ‘slider’ function to make the changes more obvious. From our observations of her use of the prototype, we noticed she did not see the zoom button on the before/after photos which we later pointed out to her. In our meeting with the technical adviser, Delvin Varghese, we mentioned this issue and he recommended making our buttons look more ‘clickable’ by giving them an embossed look.

Other alterations Delvin suggested included changing the colour of the blue text on our introduction page as over the green part of the background it gets less readable, rephrasing the text about stickers and the age question to be clearer and using an ios layout as people already know where to look for back/exit buttons etc making it more easily navigated by first time users. One important point that Delvin got us to think about was the sustainability of our product, where does the data go to, how can the JRA use it to benefit them and can it be adapted in future.

In our meeting with Sean, he initially presumed that the product was meant to be an app as we were presenting it on an ipad; this is something we noted to specify in our final presentation, that the finished product would be on a larger screen attached to a plinth. Aside from this, we carried on discussions about sustainability and what questions we may be asked at the end of our presentation but Sean didn’t have any new suggestions for changes.

In future, during user testing we could think about writing a script for an introduction to the prototype, however, in this situation we already knew the users and they had heard what our prototype was. We had agreed not to given them too much information beforehand what the prototype would ask or how to use it as we wanted to make sure the instructions were clear and it was easy to use.

 

Week 5 NUDC: Mid-term Presentation

Hello again,

This week started with our mid-term presentation in front of the rest of the class. With some mishaps while presenting we pinpointed things that we should remember for our final presentation in January. We got good response for our example research and were told that we should limit our key requirements a bit. Thinking about this we have now discussed and decided upon our most important requirements to be: easy to use and understand; time efficient and enticing; informational and provide opportunity to give feedback on the planned changes in Jesmond.

For this week’s seminar we continued with a bit more example research but later began talking about gamification which means adding game elements in order to evoke more interest in the users. Gamification is something we talked quite a bit about during our Tuesday meeting and that we want to implement in our final product. One of our biggest obstacles with this thought, however, is the risk of getting poor but high-quantity feedback instead of quality feedback. We tried keeping this in mind when we started sketching out ideas for the design.

One of our earliest design ideas was very basic and not really interesting enough to evoke interest in the users. It basically just showed users the changes and were given an opportunity to comment on them if they wanted to. This of course is the main objective with our product but it isn’t really anything new since it is very similar to Commonplace.

After discussing a lot and sketching out ideas we landed, after many iterations, on a design rather similar to our first one but a bit more enticing and different. As a way to encourage users we introduced the concept of giving out stickers when they were finished using the product. These stickers are both meant as an reward but also a means to spread the word about the Streets for People project as well as our product.

Also during our group meeting, we started creating a user experience flow chart so that we could have a clear idea in our heads of the whole feedback process. This is the most basic visualisation of our concept and from here on we need to start focusing on the small details such as colourways, sizing, stickers etc.