You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

User Testing

Design

  • We

Implementation

  • We

Evaluation

Getting the users
  • We decided to use pairs of users to test our project. As the project involves someone creating a QR code and then another person accessing that QR code and responding to an RSVP, we figured it made more sense to use separate users and give them focused tasks instead of making them perform tasks as multiple people. We gathered three pairs of people where each pair consisted of an MIT poster maker (dorm, school, and sport) and an random MIT student. By getting three different types of poster makers and a small group of random MIT students we feel that this represents our target user population very well. The poster makers are exactly the types of users we were hoping to build out website for and the MIT students fit the role of event attendees very well.
Briefing the Users and User Tasks
  • After getting the users who would participate in the test, we told them that we created a website to help with the tracking of results for advertised events.
    • Poster Maker - You are in charge of publicizing for an event. Your first task is to use our site to create a QR code that prospective attendees can scan to send an RSVP for the event. Later on, you will be tasked with viewing the statistics for your event.
    • Prospective Attendee - Your task is simply to scan a QR code, RSVP 'yes', and choose to get an email reminder/add it to your calender.
Usability Problems and Solutions
  • We

Reflection

  • We
  • No labels