While we’re on California, voters can look forward to LOTS of candidates in a couple of key races. How about we look at a #FieldGuide about ballot design and usability?
Here we go with Vol. 03, Testing ballots for usability. A thread.
7/ Test with what you have available. Test again when you have the final version.
-
-
8/ Voters for your usability tests are everywhere. Go to them.
Show this thread -
9/ To run a usability test: 1. Introduce the session. 2. Give the voter the ballot. 3. Watch the voter vote. 4. Listen for questions (don’t answer them) and comments (write them down). 5. Thank the voter profusely.
Show this thread -
10/ Watch and listen. Don’t teach. Don’t help. What is the role of the interviewer? As the interviewer, you guide the voter through the session, watch what the voter does, and take notes (if you can).
Show this thread -
11/ Watch for mistakes, listen to questions, look for hesitations.
Show this thread -
12/ Review what you saw and heard. Tally the types of problems voters had.
Show this thread -
That’s it! It’s easy to check on the usability of ballots (and other forms and notices used in elections). Just follow
#FieldGuide Vol. 03, Testing ballots for usability. Get yours here, for free: 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.