...
User 2: MIT senior who also fits the target demographic and has no previous experience with EventHub. User was briefed on tasks and was able to complete them all successfully without any need for guidance. As with User 1, User 2 had a number of questions regarding unimplemented features like the RSVP button that toggles and the Friends tab that does not show any people. User mentioned that he really likes the idea for the site and liked the "feel" of the site.
User 3Task 1: Log in! -- User successfully logged in with google credentials
Task 2: RSVP for the event “Awesome Event” taking place on 5/12/11
- user :MIT junior who fits the target demographic and has no previous experience with EventHub. User looked at list of events quickly searching for 'Awesome Event', after a couple seconds, user searched for event in search bar, found awesome event, and successfully RSVP’ed. says He mentioned that events didn’t clearly display the date (they are labeled, today, tomorrow, etc.)
Task 3: Uh oh, you’re going to be late for “Awesome Event”. Leave a comment letting people know.
- user was already in my calendar, clicked awesome event, and left a comment.
Task 4: You want to play chess this afternoon. Create a chess game event for 4:00pm today.
- user first moves mouse around page seemingly searching for a button, doesn’t find one, then looks in toolbar, clicks create, fills in necessary information.
Task 5: Log out.
- user immediately moves to ‘logout’ button in header.Thoughts on User 3: dates in list of events unclear, and we should probably use a calendar box like we do in the event page itself next to each event. Search bar has great visibility, though. Perhaps putting ‘Create Event’ in header with all the other tabs isn’t the best choice. More user testing would be required to find the best place The search bar was definitely visible, though. Perhaps we should use a calendar box next to each of the events to make the date more clear. User also experienced delay when in looking for the 'Create' button -- it wasn't significant, but you could tell that they didn't immediately remember where it was. More testing would be required to find a better location for it.
Reflection
The biggest thing we learned was that making a good implementation takes a lot longer than we expected. Everything was moving very smoothly for us until it came time for implementation. We had initially come up with a big idea for our project and over the course of GR1 through GR3 we narrowed our vision into something that seemed like a good idea and very achievable. The team seemed very optimistic about working together and everyone was communicating well and making compromises to their ideas in order to accommodate other’s ideas into the prototyping. Unfortunately, the biggest issues for us seemed to focus around coming together as a group on an aesthetic vision for the site and then implementing.
...