Embedded Files
Personas
When creating our personas we first laid out our work roles and user class. Our work role was tourists in Heraklion which then divided into 4 subgroups: group travelers, solo travelers, repeat visitors, and first-time visitors. Since group versus solo travelers and repeat versus first-time visitors are mutually exclusive groups, all users will be characterized by two user classes. We deemed this as important because we assume both characteristics change the way travelers interact with Heraklion and other people in the city. For example, repeat vistors are typically less interested in the tourist hotspots and more likely to be visiting because of the culture and enviroment, thus would search for different locations and use the app more to help others than to learn. This of course is an assumption because unfortunately we did not have any opportunites to validate this when creating user classes.
We decided on two personas, Gabby Franklin and Travis Rubberduckington, which represented a first-time group traveler and a solo repeat travler to Heraklion. These combinations arose out of assumpstions, thinking tourists are more likely to travel alone to Heraklion if they had previous trips here and are comfortable navigating than first-time vistors. After research we found that roughly only 16% travelers go solo on their journeys (Condor Ferris), meaning it is important to represent them but our primary persona is Gabby since her user classes are far more common.
Our User Journey Map demonstrates the current interactions tourists have with other websites, people, and other environment factors when finding activities to do Heraklion. Through our interviews with travelers and personal experiences with our peers we decided to have four stages: awareness, consideration decision, and review. We noticed most of the issues arises when travelers are researching and considering what to, Heraklion is a place with plenty of activities and restruants to try so we found that most people don't have time to do everything forcing them to rank what is most important for them to visit. This leads them to seek out review sites like trip advisor or talking to others to find what experience they want the most. Of course if this stage goes badly it is likely going to hider the potential for enjoyment in the later stages. Our system should focus on this stage of traveling since it has the most potential to upset the traveler.
Scenario I
Scenarios are meant to show an example of our primary persona interacting with our system, hopefully providing a better experience than the current work practice. Ours takes us through Gabby and her friend's experince while using our system and having a great night!
Gabby is on her graduation trip with three of her friends. She was not the main planner for this trip, since her friends like to plan and usually make the itinerary for the whole group. However, Gabby is recovering from a recent breakup, and so she wants to look for a nice bar where she can get a good drink. Meanwhile, her friends are tired from traveling and would prefer a more relaxing activity. Gabby wants to go out for a drink really badly, so she wants to find a place enticing enough to convince her friends to go with her. She downloads <our app> after seeing it in an Instagram ad. When she opens the app, she uses the filter system to sort for bars and restaurants. After some searching, she finds a sit-down bar with a game going on as of a few minutes ago. She sees a picture posted by another group, which shows a cocktail menu with drinks named after dinosaurs. She sees the group's selfie, where everyone is smiling or laughing. Gabby shows the post to her friends, and they are persuaded to try the bar with her since the people in the selfie look so joyful, and the vibe of the bar seems relaxing. Eventually, everyone in the group is satisfied and they share a memorable night. They decide to share their good night on Face It with a group selfie where everyone is smiling and a rear-facing camera picture of their dino drinks. They add the dinosaur, the "cheers", and the yellow heart emojis.
Storyboard (Interaction perspective)
We created a paper storyboard based on requirement extraction from last week.
Wireframe
Design Refinement
To refine our design we began eliciting feedback from our peers, our client, Kostos, as well as other clients at Bizrupt. First we design a script and two tasks, one to navigate through the app to find a screen that shows a view of posts for one location and the other was simply making a post. Our script is listed below, it was dynamically changed to work with individuals, for example some people needed a bit more guidance so we walked through the tutorial with them. We got plenty of feedback from both groups with a summary being listed below.
Peer Feedback
unclear icons
unclear what items are clickable and which ones aren't
unclear system status (where a user is in the app)
unclear goal of the app
Peer Feedback
unclear icons
unclear what items are clickable and which
unclear system status (where a user is in the app)
unclear goal of the app
Testing Script (for Client and Users)
Task 1: Tutorial
To familiarize yourself with the app, please click through the tutotial pages. Stop once you get to the home screen where you are presented with a feed of recent posts with the little of "Face it". *Please note much of our content is not real, they are clip art to imitate real posts, feel free to ask if you are ever confused by these images.
Q1: How engaging is this tutorial?
Q2: Do you understand what the goal of the app is?
Task 2: Feel free to navigate to different screens for a moment. Once ready please try to navigate to a page of reviews about [one location].
Q3: How informative were these reviews?
Task 3: Imagine you're a tourist at Mount Ida. You want to show the world the beautiful view and how excited it makes you feel. Create a post to share your reaction
Q4: Was this flow intuitive?
Q5: Do you feel like posts of this nature helpful for you exploring the city?
Q6: Do you see yourself leaving wordless reviews with your face?
Usability Issues
Task 1 - Find a location based page
Users go to the filter page first
Users clicked on the picture rather than the location name
confusion about single post at a location vs page of posts about a location
Everyone naturally gravitated to nav bar
Requested help button
Task 2 - Making a post
Didn't want to share face across platform
Unclear that the front and rear view cameras were taken at the same time
User wanted to save image to camera roll
Tutorial
Most testers just clicked through the tutorial and didn't absorb the info
Misc.
Change iconography for filter page/change filter page to act more like a search page
People think the pictures are clickable along with the emojis
Confusion on how to use filter system - many requested personalized feeds based on type of location
Confusion on navigation overall - requests for help button
Request for flexibility in privacy setting (public / in-group / private posts)
Prioritization
Page updated
Google Sites
Report abuse