1. Lectures
Watch the week 6 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 6 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. Create Paper Protoypes
Each team member will pick ONE of the 4-5 features and create a paper prototype for that feature. This involves creating one solid base, sketches of individual screens required for that feature, input elements (drawn or printed), as well as components that demonstrate state changes (e.g., overlays, highlights, etc). Your prototype can have some high-level content, but should still look and feel like a sketch, i.e., roughly drawn and has minimal colors. Include screenshots of each paper prototype in the design notebook, and detailed description of the screenshots in the captions.
As with the sketches, you may be making different versions of the same screen; for example, different students may draw their own home screen. Don't worry about making consistent/coherent designs across teammates yet. It will be an interesting exercise in later weeks, to compare all your individual sketches/prototypes with each other and come up with a coherent design.
4. Plan for Paper Prototype Evaluation
Each team member will plan for his/her own paper prototype evaluation. There are 4 parts to this planning process: (1) Come up with a test plan. For each feature, what tasks you will ask people to do with your paper prototype? Why these tasks? (2) Create a script of instructions for the facilitator, wizard, participants. For the facilitator, write down a list of questions that the facilitator may ask the user during an evaluation session. For the wizard, outline the list of user actions and the appropriate system responses for each action. For the participants, write down the list of tasks they will be asked to perform and some instructions that will explain to them what they will be doing during the paper prototype evaluation session (e.g., think aloud, etc) and why. (3) Write down the general procedure that the wizard should follow to properly respond to input from a participant. For example, what should the wizard do if the participant does something unexpected? How long should the wizard wait in silence without offering help, when a user is stuck at a particular step, unable to proceed? (4)
Decide on the roles each team member will play during the evaluation - facilitator, wizard or observer. You can perform all 3 roles yourself, or elicit the help of another team member, e.g., to be an observer and take notes. Include a writeup in the design notebook to describe the 4 parts of the planning process.
5. Buddy Team Feedback - Mock Evaluation (Low-Fi Prototype)
After planning the paper prototype evaluation for your feature, exchange a remote mock evaluation with someone from the buddy team. The instructions on how to run a remote mock evaluation is included in the "paper prototype testing using video chats" lecture. Try your best to have a somewhat complete paper prototype for your feature in time for the mock evaluation. The main objective of this activity is to prepare for the actual paper prototype evaluation in week 7, by testing out the equipment and remote setup and by working out any procedural issues. Write down any findings/observations that you discovered about your team's own prototypes.
Based on the mock evaluation of your buddy team's prototypes, provide your buddy team with 5 recommendations on how their lo-fi prototype and evaluation procedures can be improved. The receiving team should describe which recommendation they find useful and might incorporate. Details are available under Deliverable 3.d. The writeup should go into the week 6 entry of the design notebook.
6. Prepare for Challenge Report #2 Presentation
The first challenge report presentation is next Wednesday (June 16). If you are presenting, prepare a 5-10 minute presentation, and include a link to your slidedeck (10 slides at most) on the #presentations channel by midnight the day before the presentation. Two people from each team should present. In the challenge report presentations, be specific. For example, in describing how you went about testing assumptions, don't just say that you did interviews. Be more specific and talk about the types of questions that help to break/verify your assumptions. Give concrete examples whenever you can. Make the presentation interesting, informative, and something that other students can benefit learning from.
If you are not presenting, you need to sign up (via Calendly) to attend one of the presentations. You are expected to participate in the discussions, e.g., ask questions and provide suggestions (see Deliverable 2.b). We do monitor attendance. During discussion, keep yourself mute but turn on the webcam if you are comfortable with it. It is much more fun/natural for presenters to be talking to an audience, instead of a bunch of black screens. Also, in Zoom, there is a "raise hand" and "lower hand" functionality under "Reactions", which you can use during discussion to indicate that you have questions to ask or suggestions to give.
Due Friday (June 18)
● Design Notebook Entry (1.c, 3.b, 3.d) - the entry should capture your attendance to team meeting, your individual reflection, the documentation of your design activities (including paper prototype, paper prototype evaluation plan / mock evaluation observations, and buddy team feedback)