Week 11 To-Dos

Back to Schedule

Week 11 Objectives:


(1) lectures
(2) reading
(3) high-fidelity prototype evaluation
(4) start prepping for the final presentation
(5) join us at the research bootcamp (optional)

Week 11 To-Dos

1. Lectures
Watch the week 11 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 11 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. High-Fidelity Prototype Evaluation
Conduct the high-fidelity prototype evaluation, including heuristic evaluation and cognitive walkthrough, using the procedure developed for your mock interview last week. For heuristic evaluation, the evaluators should be students in CS449/649 who are not in your team/buddy team. For cognitive walkthrough, the evaluators can be people you live with (i.e., in-person evaluation), or family, friends, target users, or other students whom you do not live with (i.e., remote evaluation). Heuristic evaluation can be done asynchronously, while cognitive walkthrough must be done synchronously. If conducted remotely, cognitive walkthrough is best done by joining a zoom meeting with your evaluator, and having them share their screen while interacting with your prototype. If the evaluator is not a student in this class, have him/her sign a consent form. As a team, you need 4 evaluators in total, 2 for heuristic evaluation and 2 for cognitive walkthrough.

In the design notebook, include the following information in your writeup. For heuristic evaluation, include a screenshot of the completed worksheet from each evaluator, and describe at least 3 things you will improve in the final prototype based on what you learned from the heuristic evaluation. For cognitive evaluation, (1) record success and failure stories observed during the evaluation, (2) summarize the design suggestions from the evaluators, (3) describe your initial assumptions about the user/task/prototype and any surprises that challenge these assumptions, (4) describe at least 3 things you will improve in the final prototype based on what you learned.

4. Start prepping for the final presentation
After the hi-fi prototype evaluation, spend some time improving/refining your high-fidelity prototype based on the feedback from the heuristic evaluation and cognitive walkthrough. After completing the final version of the high-fidelity prototype, as a team, create a 3 min (max) video (Deliverable 4.b) demonstrating your final product (i.e., high-fi prototype). Keep in mind that the video can be used for your final project presentation, so think about how it might integrate with the rest of the presentation. You should have supporting comments in the video to explain what is being shown. You can also include any other aspects of work you have done, if you would like to and if time on the video allows you to; for example, you can show your paper prototype briefly to illustrate the progression of the design. To see some examples of hi-fi prototype demo videos, visit the CS449 Spring 2019 website (click on "Project").

For the final presentation (July 28), designate two people from your team to present. The presentation should be 6 min sharp and 4 slides max, with no discussion. The presentation will be graded by a randomly assigned TA, and informal feedback will be provided by students attending the presentations using a form (more details to come). Each student is required to attend 2 other presentations of your choice.

The presentation should be structured as follows:
● Slide 1: Introduce Your Problem (suggested duration: 30 seconds). What problem is your app trying to solve?
● Slide 2: Show a Quick Demo (suggested duration: 1 minute 30 seconds). Show a video of your high-fidelity prototype in action. As the video is playing, explain the different features and functionality of your app, and the purpose they serve. You can reuse part of your demo video, as you see fit.
● Slide 3: Name 3 Surprises (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.
● Slide 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?

5. Join us at the Research Bootcamp (Optional)
On July 21 (Wednesday) 10:30-11:30am, we will be hosting a Research 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. You will be doing the final presentation in the same Ohyay space, so if you are curious what that looks like, feel free to log in and explore! Just come to the bootcamp with a question that you are curious about, and we will answer them during the panel discussion. We will meet at the "Amphitheatre".

Due Friday (July 23)
● 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 high-fidelity prototype evaluation).

Due Next Wednesday (July 28)
● Final Prototype (4.a) - include link in the design notebook.
● Demo Video (4.b) - include link in the design notebook.