-
- Observations & Interviews. Give a narrative of the three people that you observed and interviewed. Don't use their names. Don't identify the users by name, but do describe who they were. Each narrative should include a particularly interesting moment -- a breakdown or workaround that exhibits a feature of the problem you're aiming to solve.
- User Classes. Describe the user classes that you have identified, and their major characteristics.
- Needs & Goals. Describe the goals that you have identified, with reference to the observations you made.
- Ballot Counters:
- Because ballot counters have a cap on the number of hours they can work, they want to get the votes counted as quickly as possible. They would like to record votes both by race and by ballot. As a result, they need an efficient system which supports this functionality.
- This is a task for which accuracy and reliability are very important. As a result, the users aim to have a perfectly accurate ballot counting. They need a system which allows them to easily correct mistakes.
- Elections have very important results, so the users would like to clearly view running totals.
- Many of the users are new to this job and don't have much time to learn it. Hence they need a system which is easy to learn and repeat.
- Elections have varying numbers of candidates. Users want to be able to handle a large number of candidates easily.
- Wardens:
- The wardens are responsible for making sure information is being entered accurately. As a result, they would like to check the total number of votes entered on both precinct and county levels.
- They will need to be able to add totals to make sure information is accurate.
- Wardens are paid per election, so they would like this process to be fast and efficient.
- Ballot Counters:
Overview
Content Tools
Activity