...
- We added a select kid modal before being able to give feedback. Users were confused that they didn't tell the application who they were.
- We experimented with a scoring system that only allowed positive ratings. We thought this might help users make scoring decision, but we found this actually confused them.
User Testing Feedback
...
First Iteration Feedback
User 1
Task 1:
Successes:
- User looked for pasta, and pressed the pasta button on the Ricky button instead of typing it himself.
- Used the “Print button” for the recipe.
- Used the time and hoped that it would ring/notify when time was up.
...
- Search box was confusing- users didn’t know what they could search for specifically
...
Second Iteration Feedback
User 1
Task 1:
Successes:
- Wrote pasta in the text box and chose the first option
- First wants to go shopping, and will checkmark all of the ingredients when she’s done.
- First clicks on boil water and is surprised by the timer, but hits start and waits for it to be done.
...
- Maybe all the kids should be selected at the beginning.
- Search bar is confusing since the destination isn’t obvious.
- Make the search box say “Search for meals”.
- Get rid of recommended ingredients because they are confusing.
Moving forward
- Work on making sure there are obvious affordances for the kids’ faces being buttons
- Evaluate whether the “recommended ingredients” list is really necessary
- Make sure the search box’s function is obvious
- Figure out what most users do and tailor the pre-selections accordingly
- Make sure kids only have the option to give feedback on the feedback page (no room to really explore around)
- Figure out a way to rank the recipe selections (and make it obvious). Do we want to have a new recipe at the top always? Or the one that they make the most?
- Work on a page that will show the kids’ preferences (could be useful in future tasks)