Usability Testing for Low/Mid Fidelity Prototypes

[ElizabethWarninger]

Overview

Create a plan and conduct usability tests for both the mobile and desktop versions of the low/mid fidelity prototypes.

Dependencies

• Low/Mid Fidelity Website Wireframes  #37

Action Items

• Research best practices for usability testing

Create a usability research plan detailing:

• Usability task flows based on the goals of MVP 1
• Determine the method of the usability test (structured, moderated, guerrilla, etc.)
• Determine test metrics (i.e. task completion, or qualitative data)
• Create a plan for recruitment of participants (likely HFLA slack community)
• Decide on the number of participants
• Determine the method of analysis for the usability tests
• Get feedback from the team on the usability test plan

Collaborative team feedback

• Brainstorm ideas for effective team feedback sessions
• Conduct a feedback session with the team for the prototype
• Make changes to the prototype based on team feedback

Conduct usability tests

• Send out a recruitment message based on the prior recruitment plan
• Conduct Usability Tests

Analyze and report findings

• Analyze findings based on prior determined methods (Affinity Map FigJam)
• Create report of findings

Resources/Instructions

Usability Testing 101 - NNG
From Research Goals to Usability-Testing Scenarios: A 7-Step Method
How to run a feedback session
Planning a Usability Test
How we conduct design reviews

Files

Figma Design file to Wireframes + Usability Testing Protocols
Figma Jam file for Wireframe Team Review Party
Google Sheets: Observation Notes
Debrief FigJam - Affinity Map
Slide deck of Results

[abryant35]

@ElizabethWarninger Please add update using this template (even if you have a pull request)

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #access-the-data channel.

[ElizabethWarninger]

Progress: Tasks, recruitment copy, script, and evaluation methodologies have been created by @melissamurphy and @joanna-pham on the Low/Mid Fidelity Figma Page.. Currently working on the issue to see what is left to finish and preparing for a group critique.
Blockers: Allocating time since our last meeting.
Availability: About 4 hours today. And an hour tomorrow evening.
ETA: Usability prepping should be finalized by the end of the week. A group critique will be during our working session on Wednesday or Thursday. This issue will not be resolved until testing is complete and results analyzed.
Pictures: See above Figma file.

[melissamurphy]

Progress: The first checklist step--creating usability task flows based on the goals of MVP 1--were drafted by Joanna and me (see Elizabeth's update) and commented upon by others on the team in the Figma and Wednesday meeting 10/27. Next step is to finalize the test details (script, metrics) and confirm with UX team.
Blockers: Testing can begin once script & metrics are settled.
Availability: I spent 6 hours this week so far. My understanding (correct me if I'm wrong) is @mathhomework and @joanna-pham will be finalizing it for tomorrow, so, I am switching my available time over to help UX writing/content frames
ETA: Usability test design finalized by tomorrow Thurs 10/28 5 PM ?; testing commences on Hack for LA members immediately upon completion

[melissamurphy]

Added Affinity Map from Monday 11/1/21 group debrief FigJam to the issue description

[ExperimentsInHonesty]

@mathhomework @joanna-pham Please add update using this template (even if you have a pull request)

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #access-the-data channel.

[joanna-pham]

Closing issue. Usability testing for mobile mid-fi wireframes has been completed. Issue has been updated with links to materials and results of testing.