Back to
Schedule
Design Notebook Entry for CR
In the design notebook entry, list at least 5 feedback (that you received from design critique session) that your team decided to act on. Describe what your team has changed in your design based on those feedback, and include screenshots of your design changes.
After the design critique,
all students must submit rating forms. Any student who has attended another team's presentation will need to individually submit a
presenter rating form for that team. Each student must also individually submit a
critiquer rating form for each team that critiqued their team's design (even if they were not the presenters and did not interact with the critiquers directly), based on the design critique forms that their team received.
PO1: User Interviews - Prototype Evaluation
As a team, find a user or two---
someone who is not a student in CS449/649 class---to interview. Follow the same ethics guidelines as the ones provided in
week 3, but
make sure that you are now using the consent forms for prototype evaluation, instead of the ones for informational interviews.
For this week, show the user your
completely interactive hi-fidelity prototype (i.e., users can interact with all parts of the interfaces) on the phone, and ask them for some feedback on the design and functionality of your app. For each interview, add a section to the design notebook to capture a summary of your findings.
P11: Prepare for Next Studio (Hi-Fidelity Prototype Evaluation)
This week, further develop your app on Figma into a fully interactive high-fidelity prototype, including all the screens as well as all the user interactions, as specified in the user flow for each feature.
During next week's studio lab, you will conduct two types of high-fidelity prototype evaluations, namely heuristic evaluation and cognitive walkthrough. In the design notebook, include a writeup about the following preparation:
(1)
Describe your goals for the high fidelity prototype evaluation. What type of information do you expect to get and why do you need it? What questions do you want to answer through this evaluation? Write down 3 high-level, scenario-based tasks and explain why you chose to evaluate these tasks. You will use these scenario-based tasks for both heuristic evaluation and cognitive walkthrough.
(2)
Plan for heuristic evaluation. Select at least 5 heuristics from Nielson that you want the evaluator to focus on. Explain why you chose these heuristics and how they would help achieve your evaluation goals. The evaluator will additionally select 1 extra heuristic to evaluate. During the evaluation, you will share (1) your Figma prototype with the evaluator on a phone, (2) a list of tasks to do without providing any explicit instructions on how to do them, and (3) a worksheet (that the instructor will provide) on which you will mark the heuristics you want the evaluator to focus on.
(3)
Plan for cognitive walkthrough. Write down the verbal instructions you will give to the evaluators and the action sequence for each of the scenario-based tasks. During the evaluation, you will give the evaluator a task without any explicit instructions, observe the evaluator doing that task, and compare your list of detailed steps for completing the task to how the evaluator is doing it. Record observations of when the evaluator failed at or skipped particular steps.
Complete Course Perception and Team Evaluation Survey
Course Perception Survey: Each student should complete the
course perception survey. In the comments, please leave constructive and actionable feedback in the "I like...", "I wish...", "What if..." format.
Team Evaluation Survey: Each student should complete the
team evaluation survey to rate the relative contribution of each team member in your team, including yourself. This information will be taken into account in the final grading.
Extra: Thinking Ahead
Think ahead and do some prep work for the final products, which include a final prototype (PO2a), Demo Video (PO2b), Final Poster+Demo Presentation (PO2c) and Design Portfolio (PO2d). As a team, you can make some decisions about how to tackle the upcoming work. The details are in
Week 12 To-Do Instructions, which has been released early for your benefits.