Week 12 To-Do’s

Lecture and reading

Attend the lecture to learn about this week’s topics and obtain extra information from this week’s reading list (short articles/videos to read/watch):

• Cognitive Walkthrough in User Interface Inspection Methods from User Interface Inspection Methods
• Turn User Goals into Task Scenarios for Usability Testing by Marieke McCloskey
• Heuristic Evaluation: How to Conduct a Heuristic Evaluation by Euphemia Wong
• How to Conduct a Cognitive Walkthrough
• Experimental Research in HCI by Darren Gergle and Desney S. Tan
• Survey Research in HCI by Hendrik Müller et al.

Conduct a high-fidelity prototype evaluation

Plan your high-fidelity prototype evaluation by including the following components in your design document:

1. Write down 3 high-level, scenario-based tasks. Explain why you chose to evaluate these tasks. All three tasks will be used in each of the two evaluation methods.
2. Plan for heuristic evaluation. Select at least 5 heuristics from Nielsen Heuristic evaluation worksheet that you want the evaluator to focus on. Write down the instructions that you will provide the evaluator including a link to your high-fidelity prototype, a list of tasks to do (without providing any explicit instructions on how to do them), and a worksheet (on which you will mark the heuristics you want the evaluator to focus on).
3. Plan for cognitive walkthrough. Write down the action sequence for each of the high-level tasks in a flow chart. For each action in the sequence, you will have the evaluator to ask four key questions. Write down the instructions you will give to the evaluators, which may include a brief introduction of your product, some background of your problem, how to perform the cognitive walkthrough, etc.
4. Conduct the evaluation. Recruit 2 evaluators for heuristic evaluations and 2 evaluators for cognitive walkthrough. Note that the evaluation can be done asynchronously while an in-person setting is preferred. For heuristic evaluation, the evaluators should be students in CS449/649 who are not in your team. For cognitive walkthrough, the evaluators should be a person outside the class. Try you best to find target users (e.g., people who fit the personas) to perform the evaluation. You must obtain consent from people participating in your evaluation if they are not a student in our CS449/649 class. Record and report your results from the evaluation.

Prepare for final project presentation

The presentation should be less than 8 minutes and recommended having 4 topics as shown below. Make sure the distinction among the four topics are clear enough in the presentation. More details are available on the Information page under Deliverable 3a. The presentation should be structured as follows:

• Topic 1: Introduce Your Problem (suggested duration: 1 min). What problem is your app trying to solve?
• Topic 2: Show a Quick Demo (suggested duration: 2 minutes). Show a video or a live demo of your Figma high-fidelity prototype in action. During the demo, explain lively the different features and functionality of your app, and the purpose they serve. No pre-recorded narration is allowed.
• Topic 3: Name 3 Surprises or Learned Lessons (suggested duration: 3 minutes). What are 3 most surprising things you learned during the design process? These can be your assumptions about the users, the problem, or the design that ended up being false.
• Topic 4: Your Hope for the Future (suggested duration: 1 minute). In the ideal world, what do you hope the impact of your app would be? What kind of future does your app help build?

The same as your design document, remember to include a final slide (non-presenting) with the contributions and task divisions among team members.

Team meeting and design document

Conduct this week’s activities during the studio time in class. When necessary, continue the team meeting and discussion out of class. Update your design document with the outcomes of this week’s activities. More details are available on the Information page under Deliverable 2a.

Carry out team reflection (Individual)

In the design document, each team member writes a paragraph describing (1) the most successful work practices of your team, (2) the challenges that your team faced in terms of communicating and coordinating with one another, (3) and what you would do differently if you were to restart the term. Be honest with your feedback to each other and use this as a learning opportunity. More details are available on the Information page under Deliverable 1c.