Skip to content
This repository has been archived by the owner on Aug 13, 2024. It is now read-only.

File menu tests #31

Open
Hanastevenson opened this issue Jul 23, 2021 · 1 comment
Open

File menu tests #31

Hanastevenson opened this issue Jul 23, 2021 · 1 comment
Labels
👤 Research Role: UX research skill set ⏳ <12 hrs Size: 2 HfLA weeks or 2 traditional work days

Comments

@Hanastevenson
Copy link
Member

Hanastevenson commented Jul 23, 2021

Comment this template for each participant.

Facilitators and note-takers

## Participant `#`

Facilitator: @_________
Note-taker: @_________
Video recording link: https://docs.google.com/..........

### Before the session 

- [ ] #406 
- [ ] #415 
- [ ] Read about [what usability testing is](https://www.usability.gov/how-to-and-tools/methods/usability-testing.html)
- [ ] On the day of the session, send a reminder to the participant via Slack direct message.
- [ ] Note-takers, have your [note-taking template](https://docs.google.com/spreadsheets/d/1MGU7DhhZmj7pkX9RIv5e8JUfnu78EWPU/edit#gid=676557520) ready.
- [ ] Be present in the meeting room 10 minutes before. Wait 15 minutes if participant is late.
- [ ] Have Slack ready in the background. Note-takers, if you think of questions to ask the participant, send them in Slack to the facilitator.

### During the session
- [ ] Record the call
- [ ] Remain neutral – you are there to listen and watch. Do not jump in and help participants immediately and do not lead the participant. Facilitators: If the participant asks a question, reply with “What do you think?” or “I am interested in what you would do.” If the participant gives up and asks for help, you must decide whether to end the scenario, give a hint, or give more substantial help.
- [ ] Update [recruiting spreadsheet](https://docs.google.com/spreadsheets/d/1wrx3dQXbti8kHvRdQFHuarW34DVnj0LNBs5nr3HDfBg/edit#gid=0) when session is done
- [ ] Upload recording to [Google Drive](https://drive.google.com/drive/u/0/folders/1XmT-fMEY5L82acY3aQC98v7misBPmDXb), under the folder for the FF page that was tested

Analysis

# Participant `#`
Analyzed by: @_________ @_________ @_________ @_________
Analysis link: https://docs.google.com/..........

### Analysis
- [ ] Read [article on analyzing usability tests](https://www.usability.gov/how-to-and-tools/methods/reporting-usability-test-results.html)
- [ ] Watch the recording and observe participant behavior
- [ ] If the plan laid out quant metrics, use a spreadsheet to calculate the metrics. If the plan laid out qual metrics, use Figma to record observations.
- [ ] List problems and classify them as **critical** (If we do not fix this, users will not be able to complete the scenario), **serious** (many users will be frustrated if we do not fix this; they may give up) or **minor** (users are annoyed, but this does not keep them from completing the scenario)
- [ ] Revisit analysis findings as more people participate in the usability test
@kelenelee
Copy link
Contributor

closed due to stock template

@kelenelee kelenelee changed the title Recruit and identify user to interview File menu tests Apr 26, 2022
@kelenelee kelenelee added 👤 Research Role: UX research skill set ⏳ <12 hrs Size: 2 HfLA weeks or 2 traditional work days and removed z junk issue labels Apr 26, 2022
@kelenelee kelenelee added this to the Figma Foundations Usability Tests milestone Apr 26, 2022
@kelenelee kelenelee reopened this Apr 26, 2022
@kelenelee kelenelee removed this from the Figma Foundations Usability Tests milestone Apr 27, 2022
@github-project-automation github-project-automation bot moved this to 🚩New Issues Approval 🚩 in DS: Project Board Aug 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
👤 Research Role: UX research skill set ⏳ <12 hrs Size: 2 HfLA weeks or 2 traditional work days
Projects
No open projects
Status: 🚩New Issues Approval 🚩
Development

No branches or pull requests

2 participants