...

Design

Implementation

Evaluation

We presented users with the following Briefing and tasks list, and also had the user explore the site afterwards.

Briefing

You will be using TechWizard, a site designed to help people who aren't good with computers become good with computers.

As TechWizard is still being prototyped, most tutorials aren't yet written.  Many buttons on the site will redirect you to a functioning page, don't be alarmed if this happens.
Imagine that you want to learn everything there is to getting an email account and writing emails.

Tasks

Find the first tutorial in the sequence on emails

Read the following tutorials in order

...

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

User 2

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"

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

User 3

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.