Week 7 To-Dos

Back to Schedule

Week 7 Objectives:


(1) lectures
(2) reading
(3) set up Figma
(4) paper prototype evaluation
(5) work models
(6) challenge report #3
(7) prepare for HCI bootcamp
(8) updates to final presentation time/format

Week 7 To-Dos

1. Lectures
Watch the week 7 lecture videos.

2. Reading
Choose 1-2 of the videos or articles from the reading list this week. Enter your reading reflection (250 word max) into the week 7 entry of the design notebook. Put your full name in bracket after the reading reflection paragraph. More details are available under Deliverable 1.c.

3. Set up Figma
If you haven't done so already, sign up for an account for Figma using your uWaterloo email, and apply for their Education plan.

4. Paper Prototype Evaluation
Each team member should (1) improve the paper prototype for their feature and the evaluation procedures based on last week's mock evaluation feedback, (2) run a paper prototype evaluation with 3 people. One of the 3 people can be a target user for your application, e.g., people who fit the personas, whom you have previously interviewed or plan to interview. Besides target users, you can conduct in-person evaluation with people whom you live with (e.g., roommates, family members), or remote interviews with people whom you do not live with, e.g., CS449 students who are NOT in your team or buddy team (you can use the #prototype-evaluation channel or your theme channel to coordinate), other students who are outside of this class, friends / acquaintances / extended family, etc. If circumstances permit, try in-person evaluations! Evaluations, when done in person, are often more convenient, informative and revealing, since you can observe users' facial expressions and body postures more closely. You must obtain consent from people participating in your evaluation if they are not a student in our CS449/649 class.

For each evaluation, specify whether the evaluation is with a target user, and document the key findings, including:
1. any points of confusion or hesitation from the user (with the user's consent, include closeup photos/screenshots of the user performing the action on the prototype at these points of confusion/hesitation; the photos and screenshots should not have any identifying information)
2. your questions to the user and their responses
3. how you think your feature can be re-designed based on these findings

In addition to the key findings, also include in the design notebook (1) photos / description of your final paper prototype, including any improvements/modification from last week (2) scripts, (3) the list of people who took on the role of wizard, facilitator and observer for your evaluation.

5. Work Models
As a team, produce 2 different types of consolidated work models based on all the informational interviews you have done before this stage since week 3 (e.g., where you ask the user questions about their processes, problems and needs). Although there are 5 types of work models, sequence, flow and cultural models are most applicable/relevant to most projects, so choose 2 out of these 3. For each type of work models, start by sketching out a work model for each interviewee, then create a consolidated model that combines the individual work models. Name and describe the themes and breakdowns that you have identified in the consolidated models. As a team, discuss what the work models suggest in terms of new / modified features for the app. In the design notebook, include (1) photos/screenshots of the two consolidated models, (2) a writeup about the themes and breakdowns for each consolidated model, and (3) a description of your discussion about new / modified features.

6. Challenge Report #3
Complete challenge report #3 in the design notebook. This challenge report focuses on your assumptions about the features that you have chosen to include in the initial paper prototype, what you hypothesized about these features in terms of their usability and utility to the users, and what you have learned through the prototype evaluations that challenge these assumptions. Make sure you gather the necessary information from the prototype evaluations in order to answer the questions in the challenge report.

7. Prepare for HCI Bootcamp
As mentioned in the Slack #announcements channel, during week 11, on July 21 (Wednesday) 10:30-12pm, we will be hosting a HCI Bootcamp to talk about academia, HCI research and graduate school. We will be using an online platform called Ohyay, and the Ohyay link will be posted on Slack by Monday July 19. When you click on the link, there is a simple registration/login step; you can use either gmail or any other email addresses to register. During the bootcamp, we will be meeting first at the "amphitheatre" for a panel discussion. Then, we will go into 5 different breakout rooms for a more in-depth discussion of different topics. In preparation for the HCI Bootcamp, please prepare 1-2 questions about academic/research careers, HCI research and graduate school that you'd like to ask the panelists. We reserved 1.5 hours, but we might finish by 11:30am, depending on how the discussion goes.

8. Updates to Final Presentation Time/Format
As mentioned in the Slack #announcements channel, the final presentation time and format has changed. We will hold the final presentation on July 28 (Wednesday) from 10:30-12pm, again on Ohyay (using the same link as the HCI Bootcamp). We reserved 1.5 hours, but if there is no delays, we can finish within the hour by 11:30am. Each team is assigned their own room and a 10-minute timeslot; the room and presentation time assignment is posted on Slack, and pinned to both the #announcements and #presentations channel. Teams should only start presenting when the TA arrives and gives a go-ahead.

Beyond presentation, each student is required to attend 2 other presentations of your choice, and provide feedback to the presenting team using a form (to be released later). When you are not presenting, you can do one of 3 things -- hang out with your team in your room, go to a firepit to socialize with other students, or attend a presentation.

Due Friday (June 25)
● Design Notebook Entry (1.c, 3.b) - the entry should capture your attendance to team meeting, your individual reflection, the documentation of your design activities (including paper prototype evaluations and work models).
● Challenge Report #3 (3.c) - complete the writeup in the design notebook.