...
- Usability problems you discovered from the testing. Describe what users did, but don't record users' names.
Prototype iteration
...
We had a fairly successful first iteration in terms user feedback and task completion rate. Ironically, that left us in a bit of a difficult situation for determining what changes to make for the second iteration. The first thing we decided was to include additional features to our prototype by incorporating groups and notifications. We then created a few additional tasks to test these features, shown in tasks 5-7, above. Also, we added the use of sticky notes to our paper prototype to dynamically show updates that occurred to a given page and for notifications.
Overall, I think we learned more in building the paper prototypes and identifying what tasks to test for then we learned from user feedback. Part of the reason for this is because we had come up with three very different designs in GR2, so the process of making design decisions and compromises really helped us settle on a single vision for the project. The other major reason is because we had tested the tasks on each other before we ever showed the prototype to a user in class. This meant that we had already worked through a lot of the design kinks that our original designs in GR2 did not handle. That said, we did get some great insights during testing in class, especially with regard to spatial placement of different elements on the page and the some page navigation approaches that none of the team members had really considered.