...

One thing we identified from User1 is that there should be some sort of progress bar or progress indicator in the tutorials.

User 2

User 2 is over 50 years of age but is surrounded by her technically literate children and husband. She is familiar with simple web browsing and can use a smartphone with some degree of efficiency. She however is far from an expert user, having had trouble navigating to her email using the new windows 8 (in an attempt to conduct this survey).

She discovered a bug with internet explorer that listed all of the tutorials at once, rather than hiding them until their header is pressed and called the page cluttered. When the error was pointed out, she was much happier with the layout. She also complained about the use of CC / BCC in one of the tutorial titles, claiming that the use of unexplained acronyms was particularly unclear (she also later made various criticisms about technical jargon).

From this, we might want to make a greater effort of simplifying our word choice, expanding acronyms, or at the very list providing annotations or explanations for technical terms that cannot be reduced as such.

(Perhaps we should also fix severe internet explorer issues, if we had a bit more time).

She also complained that the "fun facts" section only had 3 facts, and disputed a bunch of them. Perhaps fun facts are more of a distraction / unnecessary than fun.

In exploring the particular tutorials, she couldn't tell that the inactive and un-clickable previous/next navigation buttons were grayed out and suggested that they might as well not be there at all if they're not clickable - a great suggestion! She also was confused about the beginning slide's previous button and the ending slide's next button taking her to a different tutorial, having said acronyms / cc and bcc
"kind of busy" -> tabs?
cluttered on ie
previous,  not to previous tutorial
back to tutorial list, find where we were
"only 3 facts"
"Next doesn't do anything when I get to the end."
55+, 

cronyms / cc and bcc

"kind of busy" -> tabs?

\[\[cluttered on ie\]\]

previous,  not to previous tutorial

back to tutorial list, find where we were

"only 3 facts"

," which might either be developed into a feature, or simply remove the buttons when they're inactive in accordance with the previous observation.

Also, in watching her explore the website we noticed that while easy to explore from a subject to its pre-requirements, you first have to return to the tutorial listing and then re-find the tutorial you had left to return to it. Instead of having a back to tutorial listing button, or perhaps instead of the back to home button, we should have a back to previous page button (as presumably the browser's own back button isn't super familiar to our website's users). Additionally, it might be useful to have an additional field in the sidebar for the next "level" of tutorials."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 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 Paper prototyping was a cool technique to learn, and was particularly useful for developing a better idea of an appropriate layout, design, and page hierarchy that made sense without wasting a huge amount of time on unsuccessful iterations. We also found the canned prototype to be incredibly useful .  Paper prototyping was a cool technique to learnonce we had a narrower potential design space , as it escaped the issues users had with using their imaginations to explore the paper prototypes and gave us a better idea of the limitations we would face in implementation.

User testing the various 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.