...
User Testing Round 1 Observations
- "I wish Two testers said they wished the system knew which bin the package was packages were supposed to go in and autopopulated the field as soon as I they typed the recipient's name". This is a usability issue.
- All of the testers said they Users weren’t fully comfortable using the sidebar at first because they were new to the system---they said they preferred to return to the homepage where every button had a caption, but that they would use the sidebar once they got used to the system. This is a learnability issue but it's not a big issue.
- Every tester tried to add the vacuum cleaner to the system instead of making a note. This is a usability issue.
- Two testers
- Some users tried to click at the bottom of the spreadsheet to add a new row
- “I wish I Two testers said they wished they could edit a pre-existing package or item”item. This is a usability issue.
- Two many testers typed room numbers of package recipients into the location field instead of bin numbers. This is a learnability issue.
User Testing Round 2 Prototype Photos
...
User Testing Round 2 Observations
- One tester said the following: "Why is the button to pick up a package marked 'check out'? It's not like they're going to check it back in. It should say 'pick up.'"
- Testers didn't like the pop up modal dialog upon login that told them they had new notes. They wanted a nonintrusive notification like on facebook.
- One tester suggested that we notify deskworkerd desk workers of added new calendar events in addition to new notes. This is a safety issue because there are some important events that desk workers need to know about.
- During task 4.55 multiple two testers checked out the incorrectly addressed package and then registered a new package with the correct name. Afterward, testers suggested an edit button on every row. This is a usability/learnability problem.
- Testers liked the sidebar icons and the but big buttons with pictures on them because they were easy to find and their functionality was obvious. This is a learnability pro!
- One tester Testers wondered why the search bar was so prominent and big.
- Testers like liked the specificity of the specialized search bars on each page and were glad there wasn't an omni search bar on every page
Usability problems you discovered from the testing. Describe what users did, 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
You did two rounds of paper prototyping. Describe how your prototype changed between those two rounds.
Usability problems you discovered from the testing. Describe what users did, 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.
...
- Two testers asked for undo capabilities like in gmail (an undo button that appears for 5 seconds after an action). This is a safety issue.
- One tester wasn't sure if he should remove notes after he read them or if he should do something about the notes. This poses a safety problem because if users delete the notes, it will delete them on every desk worker's account.
- Testers weren't sure what the sticky note in the bottom righthand corner would do so they didn't click it but, when asked, they correctly guessed what it did (brought up a dialog to create a new note). This feature was learnable but users didn't use the system long enough to learn it.
Prototype Iteration
You did two rounds of paper prototyping. Describe how your prototype changed between those two rounds.