...
You're Maria/Joe and you're away on business. You want to check on how the family has been doing.
Observations
- Usability problems you discovered from the testing. Describe critical incidents encountered by the users, but don't record users' names. Record these as a series of high-level takeaways, focusing on the usability problems you saw, rather than what each participant did. For instance, you might describe how you had some learnability issues with your prototype, as evidenced by users B and C clicking all of the menus to try to find option X.
Prototype iteration
User 1
Task 1
This user tried to assign a task to a child, which isn’t possible in our system. He also tried to click on his own picture to log in. In our system, there isn’t a login system, since you only specify who you are when you complete a task. User also mentioned that the “Complete” label in each task row was confusing, since he didn’t know if it meant that the task was already completed.
Task 2
As a kid, the user didn’t feel particularly motivated to use this system. He also didn’t know when to interact with the page. He clicked on a task before even starting it. With our prototype, you only interact with the system after finishing a task. The user stated that it’s not clear how this is motivational for children. What is the positive feedback?
Task 3
The user completed the task correctly, but he was wondering if there was a way to say “good job” when looking at his sister’s task completion page.
Task 4
The task wasn’t very well defined and the user didn’t know what to do. We were hoping this task would lead to discovery of the “previous week” feature, but it didn’t happen.
User 2
Task 1
When completing the task, this user didn’t know what our camera icon did. He also wanted to add a task deadline but there is no way of doing that. He also didn’t think it was convenient to upload a task completion picture. He’d have to get a phone, somehow get the picture to the computer, and upload.
Task 2
The user wanted to start a task by clicking on it. In that prototype, you only interact with the task once it’s completed. Clicking on a task and seeing the completion dialog was a surprise to him. He actually noticed that adding a task completion picture is a three dialog process, which is annoying.
Task 3
User tried to click on a completed task to see who did it. Completed task rows should have a photo of who completed that task.
The user didn’t discover the ability to click on a person’s face to see what tasks they’ve done. User mentioned that the face pictures in the top right didn’t feel like sections to him..
Task 4
Wanted to see yesterday, but unable to view just yesterday. In our system, you see previous tasks group by week. He also didn’t know how the completed tasks were sorted. He wasn’t sure how to go back to the first page after reviewing the previous week.
In the end, the user liked the prospect of using this tool for managing a rebellious teenager. He mentioned the concept of task completion pictures was valuable, but that it wasn’t obvious from the user interface. The user interface didn’t convey any sense of importance, or an indication of how a user would get credit for work done.
User 3
Task 1
User wasn’t sure if the todo list was for him or for everybody. There is also no editing interface, so if there’s a typo in a task there’s no way to correct it. When completing a task, it wasn’t clear that the “who am i” section of the completion dialog was a button for him to indicate himself.
Task 2
The user wanted to pick a specific task before working on it. The prototype didn’t have that functionality. He also had trouble figuring out where to click the task in order to mark it complete. It seemed like clicking on the entire row would bring up the completion dialog.
Task 3
The user discovered the top right face buttons to check on his sister.
Task 4
User didn’t discover the feature to look at previous weeks.
In the end, the user wasn’t clear on what needed to happen when you wanted to help the family out. Does somebody just look at the list? click anywhere?
Prototype iteration
From our first user test, we learned:
- Users want to be able to click on a task and indicate they’re going to work on it before actually doing it.
- The fact that you don’t start out by choosing who you are is confusing.
- There need to be actual motivators for children, such as points or a “top helper” ranking list. The ability for a parent to indicate “good job” would be nice too.
- Reviewing previous weeks isn’t very discoverable, or interesting.
- Uploading a task completion picture is too cumbersome, with too many dialogs.
- The feature of adding an icon to a task isn’t discoverable at all.
- Overall the users liked the deadline sliderYou did two rounds of paper prototyping. Describe how your prototype changed between those two rounds.