RScanVP


Group Members


Problem Statement

  • When someone sees a poster conveying a message, it takes time to record the details of that poster. This makes it inconvenient and usually results on poor response from those intending to attend an event. Most students, who see a poster in passing, rarely have the time to stop and fully read the information on a poster, determine what is important, and record the necessary details into their calendar. Thus, putting QR codes on these posters would allow viewers to scan the QR code and have all of the information added to their calendar in an efficient and reliable way. Further, it would allow poster makers to gather data about who and how many people intend to attend their event.

GR1 - User and Task Analysis


GR2 - Designs


GR3 - Paper Prototyping


GR4 - Computer Prototyping


GR5 - Implementation


GR6 - User Testing


  • No labels

4 Comments

  1. GR2:

    "Adding to calendar" was included as an important task but missing in first design. Point of this exercise was to attempt to create 3 completely different designs (aka no need to iterate just yet). Suggestion for presentation improvement: try utilizing the whitespaces surrounding an image so that both the image and its contextual text can be viewed simultaneously.. It is sometimes difficult to follow what you're saying with what you're showing if the reader has to keep scrolling up and down.

  2. GR3:

    Be nice to see the rationale behind changes made between iterations to demonstrate what was learned. Clear and high level tasks. Captions under photos would help provide context. Unclear if 6 users were actually tested.

  3. gr4:

    "Fidelity: Prototype does not look like it will in final implementation. Text font sizes and style on welcome page should be better thought out. 
    Usability: On Edit Event Details page, AM/PM button not clear which one is selected.
    "

  4. Solid report for GR6! Found it both insightful and thorough. One comment is while having bullet points is great for readibility, writing long paragraphs per bullet kind of defeats the purpose of having bulets in the first place. I would also point out that while I think you guys improved a lot from iteration to iteration, the final implementation seemed to fall a bit short of what I would consider the optimal usability for your UI. In my experience, the best UI require absolutely no thinking on the user's part and i'll admit this is rather hard to accomplish (perhaps A/B testing would help, but definitely more iterations with more users as you pointed out would help). Nevertheless, it was a pleasure working with you guys.