...

"Next doesn't do anything when I get to the end."

User 3

User 3 is an M.D. who works at an administrative level in his Department at the County.

User 3 is reasonably competent with computers, but has issues with things he has never seen before and seemed like a good member of the target population that was much more competent than User 1 and User 2.

User 3 jumped straight to the correct category and tutorial and was able to find the tutorials asked for fairly quickly.  They did stumble when trying to find out about internet, instead checking the email tutorial category listing exhaustively before going back to TechWizard home.  However, they may have been trying to be extra pedantic given that they were "user testing."

User 3 likes the layout and relative simplicity of each page.  However, they disliked the technical terms such as "Mail Client", suggesting "client" should be replaced by "provider" or another more identifiable term, and the technical term be placed in parenthesis near by.  The buttons for the tutorials, while big and easy to see, did not immediately suggest to them that one was a heading and one was a link to another location.

Reflection

We found the canned prototype to be incredibly useful.  Paper prototyping was a cool technique to learn

User testing the prototypes also rapidly revealed design issues that we hadn't though of, in particular many things seemed obvious to users that were not obvious to us.Discuss what you learned over the course of the iterative design process. If you did it again, what would you do differently? Focus in this part not on the specific design decisions of your project (which you already discussed in the Design section), but instead on the meta-level decisions about your design process: your risk assessments, your decisions about what features to prototype and which prototype techniques to use, and how you evaluated the results of your observations.