What we did ?
After we developed the sequential flow of
activities within the application through well-defined flow charts and
sketching storyboards we carried out a guerilla test to determine the user
ability of our application, based on their ability to navigate through the
application and accomplish user goals.
The Guerilla Test Setup
The test was executed with a designer present
taking important notes from the user while administering the test. The designer
asked specific questions and received good feedback and also additional
explanation where needed. Most importantly the users were allowed to “think out
loud” to process the sketches and give logical reasoning for making choices or
decisions to accomplish goals. The test was recorded and the team analyzed
results.
Guerilla Test#1
https://drive.google.com/file/d/0B8nDbyWKpofid0NacTlZVFhYQmM/view?usp=sharing
Guerilla Test #2
https://drive.google.com/file/d/0B8nDbyWKpofiYVIyUnlaVUw1dUU/view?usp=sharing
https://drive.google.com/file/d/0B8nDbyWKpofid0NacTlZVFhYQmM/view?usp=sharing
Guerilla Test #2
https://drive.google.com/file/d/0B8nDbyWKpofiYVIyUnlaVUw1dUU/view?usp=sharing
Guerilla Test Findings
Generally the application paper prototypes were well understood by our users during the test. They were able to move from one user interface screen to another and perform actions with good reasoning and judgment. Most of the users were able to go through the application from start to finish with just a few exceptions
Observations
Problems found
The team has decided that making the “done “button inactive before and order is placed and inactive if the ordered items are empty. Also the “done” button will show a popup message informing the user if he/she wants to proceed to checkout and only redirect to the “MyOrder” page.
Generally the application paper prototypes were well understood by our users during the test. They were able to move from one user interface screen to another and perform actions with good reasoning and judgment. Most of the users were able to go through the application from start to finish with just a few exceptions
Observations
Problems found
-
Some users used the “done” button for the wrong function. They pressed the button
before they wanted to switch to another menu (e.g. food, drink).
-
The users recognized that the edit button at the button of the home screen
performed the same function as done because they both lead to the “MyOrder”
screen where items could be also edited.
-
So of the users missed the specials menu and only went to food and drinks and
proceeded to checkout.
The team has decided that making the “done “button inactive before and order is placed and inactive if the ordered items are empty. Also the “done” button will show a popup message informing the user if he/she wants to proceed to checkout and only redirect to the “MyOrder” page.
-
The “edit” button will be removed from the home screen so that the users are not
confused but the “edit” button in the “MyOrder” page will remain to help user
remove items from their order.
-
We think that relocating the specials menu in a more significant location on the
screen might increase the chances of selecting form the special deals apart from
ordering only from food and drinks.
No comments:
Post a Comment