Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Export Recovery Key" instructions are too long #103

Open
crwood opened this issue Jun 21, 2018 · 1 comment
Open

"Export Recovery Key" instructions are too long #103

crwood opened this issue Jun 21, 2018 · 1 comment

Comments

@crwood
Copy link
Member

crwood commented Jun 21, 2018

From user testing sessions at RightsCon 2018:

export

Issues:
One person didn’t read the instructions; they were too long. They skipped the exporting a recovery key process altogether.
One person felt it would be useful to show the steps more visually, like an infographic: showing the key, showing where it can be saved

Suggestion
Make the recovery key creation visual.
Idea: short storyboard at the moment that user connects to grid (instead of image with ‘finish’ button)
Headline: Before we start…
Drawings: [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
[1] Newly minted unique key
[2] Ambulance with a key in it
[3] Key next to folders
[4] Image of key going into a safe
[5] Single stick figure smilingly embracing themselves
Text underneath each drawing:
[1] Create your very own recovery key
[2] In case something goes wrong (e.g., hardware failure, accidental data-loss)....
[3] … this key will help you restore uploaded folders
[4] Put it in a safe place, like an encrypted USB drive, or in your password manager.
[5] Be selfish: don’t give this key to anyone.

@crwood
Copy link
Member Author

crwood commented Jun 21, 2018

Note that increasing the number of steps/dialogs that the user needs to click through in order to accomplish a task may increase frustration-levels and/or make the process feel more laborious than it actually currently is (and thereby decrease the chances of users reading/understanding/following the various steps). It might therefore be useful in the future to test/prototype a variety of different approaches here (and a variety of different visual metaphors) so as to try to strike an appropriate balance between being too concise and being too overbearing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant