...
User 1: MIT senior, fits target audience as a college student in the Cambridge area. Has no user interface experience. User was briefed as described above and given the tasks above one at a time. The test went smoothly: the user completed all tasks without problem; the only intervention required was to explain how things should work if they had been fully implemented (in this case, the RSVP button on the "Awesome Event" page didn't visually toggle like it was supposed to). User was unsure about the difference between the Calendar and Browse Events tab; perhaps we should change the title of the Calendar tab to "My Events" or something more descriptive.
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.
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.
...