Usability tests of first-time use (Round 1)
We haven't done usability tests of the entire process of using Tails for the first time since 2015. We should do that again!
Checklist
-
Screening -
Create screening survey -
Test screening survey -
Send link to screening survey -
Select participants using screening spreadsheet in ux/private
-
-
Preparation -
Adapt research information sheet -
Adapt consent form -
Adapt checklist -
Get mouse and keyboard -
Test the recording setup -
Prepare incentives -
Print research information sheet and consent forms
-
-
Analysis -
Create rainbow table: https://gitlab.tails.boum.org/tails/ux/-/raw/master/first-time/rainbow_table.fods?inline=false -
Prioritize work together with the developers -
Share highlights on tails-dev -
Save candidates in email database -
Add to achievements.mdwn -
Get reimbursed for travel, incentives, etc. -
Improve checklist
-
Top priority fixes
- Report findings from usability tests to Etcher (#18783 - closed)
- Improve instructions to start on Mac (#18782 - closed)
- Link to installation instructions from "Start o... (#18779 - closed)
- Document the error when opening the USB image f... (#18777 - closed)
- Explain better the verification (#18776 - closed)
- Improve searchability of Persistent Storage cre... (#18775 - closed)
- Improve steps in installation overview (#18774 - closed)
- Improve Spanish translation on critical path (#18767 - closed)
Low-hanging fruits
- "Start in macOS" is confusing when obvious (#18764 - closed)
- QR code in steps is unclear (#18765 - closed)
- Add screenshot of Plymouth to installation steps (#18771 - closed)
- Update time estimates in overview (#18773 - closed)
- Stop explaining why we removed the OpenPGP veri... (#18437 - closed)
Big and important
Other things @sajolida can do on his own
Work with @anhdres