GR3 - Paper Prototyping
Prototype Photos
Design 1
|
|
|
|
|
|
Prototype Iteration
- Icon Changes:
- Question Queue: Pack of People -> Question Mark
- General Stats/FAQ: Question Mark -> Histogram
- Events: Starburst/Asterisk -> Flip Calendar
- Experiment with new design direction that focuses on a map-based view.
- Make tour guide's name more prominent and persistent.
- Added tour completion time estimates.
Design 2
|
|
|
|
Briefing
Problem:
- College tourists often have trouble finding campus events/activities, accessing current students for more specific inquiries.
- Tour Guides have to spend time repeatedly answering common questions from tourists which detracts time from the tour.
Goal of the Application:
- Find out about events on campus
- Facilitate interaction between tour guides and tourists
- Facilitate student-tourist interactions
- Find out about general stats/frequently asked general questions easily
Information about you, the User:
- You are a prospective student at CollegeTech University using the application as a tourist.
- You are about to check in/go on a tour at the university.
Scenario Tasks
- Check in to a tour and Ask a question to the tour guide.
- Find out the percent of undergraduates that are African-American at the University.
- Find a greek related event happening today or tomorrow.
- Find a story relevant to business school and schedule a meetup with a student who wrote a story.
- Leave feedback for your tour guide.
Observations
Round 1
User 1
User 2
User 3
Round 2
User 1
Task 1
- Forgot to click ok on the initial popup the first time around, then remembered and saw to click there
- Confused about the redrawn pins and what they mean
- On the Tour page, didn't realize that the questions were text and not clickable. Also didn't realize that the list of questions was a queue.
Task 2
- Instead of looking to the General Stats/FAQs page, wanted to ask everything to the tour guide through the Tour page
- Found General Stats wording ambiguous
- Clicked on dots underneath graph rather than swiping through the graphs
Task 3
- Found what he wanted easily
Task 4
- Was unclear that the pins were indicators of stories. Only clicked on pins when he'd explored everything else on the site.
- Unfortunately pin for management school got covered by the side bar (paper prototype didn't allow for looking around the map irregardless of the side bar).
Task 5
- Found what he wanted easily
General Feedback
- Wanted to know that pins at the beginning were a way to get stories
User 2
Task 1
- Clicked on a question in the queue without realized the questions were text and not clickable
- Didn't realize that the list of questions was a queue: highlighted one question, copied it, and pasted it into the text box to type a question. Only when it appeared at the bottom of the list did he realize that the tour guide would be asked the same question twice.
Task 2
-would ask a question through the question component
-would then revert to direct personal interaction -- raise question and ask her
-clicked on her picture to see if that would “get her attention”
-when he realized that it took it to a user profile, clicked the x
-said by now he would be done
- (said he would be likely to use this after a tour because he would get too distracted)
-when he got a hint about the icons, got general stats and easily saw the circle affordance and found data
Task 3
- clicked the x to get out of the side panel
-clicked on the schedule icon (confused that it showed the wrong date data)
-looked to scroll events but couldnt
-so then clicked right arrow to see events for tomorrow and found it!!
-clicked event, and expected it to highlight where it was on map
Task 4
-x out of side panel
-clicked on the feedback icon just to see what would happen. Not what he was looking for. So exited out of the side panel
-thought the pins were tours, saw there was “a tour near the sloan school of management” and clicked on it to see what would happen
-stories popped up
-clicked on a picture of aaron to schedule a meeting, clicked on the button to schedule a meet up
-tried to click refresh to see where current location was so he could set up a meet up near his location
-entered in information, didn’t want to put in phone number (because not even student at school yet, and wanted to just meet them) → would try to submit without it, and if it wouldn’t let him he would give it
Task 5
-knew to use sliders
-missed stars first time, saw them second time (would see them if they were half filled)
- would still want to click on things and see information
- wanted to see search function for the maps
GENERAL THOUGHTS
-”ask a question” rather than just “question”
-specify what you’re giving feedback to
-general stats was cool interface
-for the tour interface => wasn’t sure of what was going on. Would never type a question in, would raise his hand....tours he’s been on were never crowded so that he couldn’t ask a question. But maybe if he was intimidated would use the interface to ask a question
-felt that map was so central that it should play an even bigger role in the interface
-color coding buildings (by majors), or by type of building would be kind of cool
-didn’t get the difference in the pins from the beginning to the end
-would be cool to hear sound recordings of a guide giving a tour
-would be cool to see a virtual replay of the tour (if wrong time, or w/e....would be cool for leading his own tour)
-when there’s a person in front of me, wouldn’t want to use the interfa