

TESTING
During these sessions: the design team will allow these participants to engage with the prototype, answering questions regarding the prototypes as needed. At least 2 team members of the design team will be present, 1 to engage with the participants in the testing of the prototypes and another to observe and take notes, regarding the participants experience with the prototype. The latter design team member will be sure to capture key issues the design team will need to address as well as any changes to the design the participants makes. The former, that is design team member engaging the participant, will provide "let's pretend scenarios" and also will allow the participant to physically alter the prototype. This will provide for a "co-design" of the final product with the participants.
The design team will meet after all testing sessions are complete to discuss findings from the 'testing" sessions and evaluate the viability of the two prototypes based on the feedback received. The design team will summarize findings from the testing sessions and make changes to the current designs based on feedback, potentially scrap one or both of the designs. If the latter, the team will consider proposing additional design ideas. Although it may not be possible for this class, the design team would envision meeting with another round of participants/or would-be users to test any alterations made to the design based on the participants in this cohort.
​
-
What are the users initial reaction to the design?
-
Do they believe the proposed design would be useful to them in answering questions they have or have had about sexual health topics? If not, why? If so, why?
-
What feedback do they have regarding the designs as proposed?
-
Do they like aspects of the proposed design? If so, what aspects?
-
Do they not like certain aspects of the design? If so, what do they not like?
-
Is it usable?
-
Is it aesthetically pleasing?
-
Is it intuitive?
-
How do they feel about the data organization?
-
What additional features or alternative designs might they propose?
-
Do we have unnecessary features?
plan
The design team intends to test the two prototypes currently developed and hopes that during these testing sessions that the following questions will be answered:

user
testing

We tested our prototypes with 1-2 users and plan to do additional user testing. We employed “let’s pretend scenarios” to ensure users tested every aspect of our prototypes. we walked through the navigation of our product and asked users to comment, and mark up ideal changes for best usability.
Overall users endorsed both concepts and liked the opportunity to discuss questions and concerns with sexual health professionals (AMA).They also liked avatar support during information quests for anonymity. Lastly, the like the quick concise links to resources in area.
​

key
insights
The following are insights gathered after user testing:
​
•Site needs to achieve balance between Anonymity & identity of users
​
•Users need to have enough anonymity to ask questions they are afraid to ask anywhere else; but,not so anonymous undesirable activities occur: worry about “creepy guys” on site
​
•Users may not want to exchange with other users on site: Don’t want this forum to be a “Pick up” site
​
•Some terms on home page not clear
​
•Character, graphic & tone selection critical
​
Design Revaluation. Actions to take moving forward:
​
•Remove user exchange options
​
•Rename items on home page
​
•Conduct user testing on graphics , character & tone selections
​
character & tone selections