Closed ElizabethWarninger closed 2 years ago
@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.
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.
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
Added Affinity Map from Monday 11/1/21 group debrief FigJam to the issue description
@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.
Closing issue. Usability testing for mobile mid-fi wireframes has been completed. Issue has been updated with links to materials and results of testing.
Overview
Create a plan and conduct usability tests for both the mobile and desktop versions of the low/mid fidelity prototypes.
Dependencies
Action Items
Create a usability research plan detailing:
Collaborative team feedback
Conduct usability tests
Analyze and report 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