It’s Field Guide Friday! Our team is doing a lot of usability testing these days, so, let’s do Vol. 03, Testing ballots for usability!
Show this thread
-
3/ Test when you know what is going to be on the ballot or when something has changed.
Show this thread
4/ Usability testing answers questions about how and why voters will use the ballot. Know why you are conducting a usability test.
-
-
5/ Start testing early with a few voters trying out the first versions of the ballot, one at a time.
Show this thread -
6/ Test with what you have available. Test again when you have the final version.
Show this thread -
7/ Voters for your usability tests are everywhere. Go to them.
Show this thread -
8/ Follow these steps to run each session of a usability test. 1. Introduce the session. 2. Watch the voter vote. 3. Listen for questions (don’t answer them) & comments (write them down). 4. When they are done voting, ask to walk through what they did and why. 5. Say thank you.
Show this thread -
9/ Watch and listen. Don’t teach. Don’t help.
Show this thread -
10/ Watch for mistakes, listen to questions, look for hesitations.
Show this thread -
11/ Review what you saw and heard. Tally the types of problems voters had.
Show this thread -
12/ That’s it! Simple, direct observation of people interacting with something you made. Get your Field Guide here: https://civicdesign.org/fieldguides/testing-ballots-for-usability/ …
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.