Back to
Schedule
Design Notebook Entry for D3
In D3, your team analyzed the interview data collected so far by creating an affiniity diagram and a consolidated work model. In the design notebook, first, include a photo of the affinity diagram that you created in the studio lab, and a 1-2 paragraph description of the key themes and insights extracted from the interviews. Second, include a photo of the consolidated work model that you created during the studio lab, and a 1-2 paragraph description of the themes and breakdowns in the consolidated model. Finally, write 1 paragraph to compare the findings from the affinity diagram and the consolidated work model. What are the similarities and differences?
Transfer your affinity diagram into Miro. You can sign up for a Miro account using your uWaterloo email, and apply for their
Education plan. You will be updating the affinity diagram after each user interview.
PO1: User Interviews - Informational Interview
Find 1-2 users to interview;
someone who is not a student in CS449/649 class. Follow the same instructions and ethics guidelines as the ones provided in
week 3. Remember that if you learned something new during the interview, you can refine your interview questions to dig deeper into these new aspects of the problem.
In the design notebook, you will summarize your findings from each interview. For each interview, add a section to the design notebook to capture (1) a summary of your findings, (2) a description of any changes to your interview questions or procedures that you plan to introduce in future interviews based on what you learned.
Update the affinity diagram on Miro based on the new interview data, and include a screenshot of the updated affinity diagram in the design notebook.
T3: Team Building Exercise #2
Complete this
activity from the d.school book "Creative Acts for Curious People". This will prep you for next week's studio lab activities. Specifically, each team member should individually make two stick figure drawings: (1) one drawing representing how they feel about CS449, (2) one drawing representing one of the interviewees and how they feel about their problem. Combine your drawings together to make two collages (i.e., put the stick figures side by side)---one that represents how your team collectively feel about CS449, and another that represents how different interviewees feel about their problem. Include a screenshot of these two collages in the design notebook. There are no right or wrong answers; have fun with sketching!
P5: Brainstorm Features
First, watch lecture video on "Design Arguments", "iPhone Design Argument". Then, as a team, complete the following 4 steps to brainstorm a set of features for your app. You can do this in-person using real sticky notes, or online using Miro.
1.
Individual: Close your eyes and imagine a target user for your application. What goal is this user trying to achieve? What are the obstacles that are in his/her way?
2.
Individual: Come up with ideas of app features that you think will help this particular user overcome his/her obstacles. Put one sticky note per feature. Include your name on the sticky notes. Write down as many features as possible. Do not judge the ideas that are popping up in your mind.
3.
Team: After everyone has contributed feature ideas, hold a team meeting to vote on the features. Without consulting with each other, each team member should put a star symbol next to 2 ideas that he/she likes the most. The number of stars on each sticky note indicates how much that feature is liked by the team as a whole. As a team, choose 4-5 features you all like best, and discuss why you like them the best.
4.
Team: For each of the 4-5 chosen features, write down the design argument for that feature, using the format on slide 8 of the "Design Arguments" lecture.
In the design notebook, include (1) a screenshot of the sticky notes from different team members, and star symbols indicating which features are most liked, (2) a writeup describing the list of 4-5 chosen features, why your team likes them the best, and the design argument for each feature.
CH1: Challenge Report - Notes
The challenge report, due in week 8, documents how your team has challenged your assumptions each week. To build up to that, record some notes about how you have challenged your assumptions this week. Be specific, and describe the concrete actions your team took to test assumptions. Complete the CH1 section of the design notebook.