CSE 481p Winter 2024: Research Project

The assignment prompt is subject to minor changes, so please check back when time gets closer!

G1: User Research Report

Canvas link
Due: Jan 23 at 11:30am

This is the user research phase of your project. Based on the project ideas that you’ve discussed as a group, narrow down to a target topic area and target audience for your project. For instance, perhaps you wish to do something to combat vaccine misinformation on social media, and thus, you want to target people that inadvertently (as opposed to on purpose) share vaccine misinformation. Or, say you wish to focus on improving online dating during COVID, and you want to target college students on the UW campus. Notice that we’re not talking about solutions yet. 

Given your narrowed focus and audience, plan a series of research activities that will help you know more about your target user(s), their goals and needs, and the environment they are in. These activities can include semi-structured interviews, participant observation, fly on the wall observation, questionnaire, and more.

Use the AEIOU framework to help organize your data collection and data analysis. AEIOU means that you will attend to each of these elements during your observations and interviews:

  • Activities are goal-directed sets of actions.
  • Environments include the entire arena in which activities take place.
  • Interactions are between a person and someone or something else, and are the building blocks of activities.
  • Objects are the building blocks of the environment, key elements sometimes put to complex or even unintended uses, possibly changing their function, meaning, and context.
  • Users are the people whose behaviors, preferences, and needs are being observed.

Use the AEIOU framework to present your findings from the user research you have done. You can use text, quotes, photos, diagrams, etc. to convey your findings, while keeping your user study participants anonymous. Don’t forget to explain what method you used to collect your data.

As a result of AEIOU, identify your takeaways from this research, including design challenges and opportunities that you might be able to build on for the rest of the quarter.

Submission:

Format your report as a 1-2 page blog post targeted towards a public general audience. Use a new Google Docs file within your Google Drive folder we’ve created for this class. Start the blog post with an overview of your project direction and target audience before diving in to your user research method and why you chose that method. Summarize who your eventual participants/data were. Finally, describe your findings according to the AEIOU framework, along with your takeaways for your project. Submit the link to the Google Doc on Canvas. After we’ve left comments on the document, you will transfer the contents to your project website as a new blog post.

In addition, each individual in the group must submit a private contribution statement at the following Google Forms link: [link]. The statement should include (1): your estimate of the percent of group work completed by you, and (2) a summary of the work you did. For example, your statement could be: “40%, researched the background of the problem, outlined the content of the document, wrote the first version of one paragraph, also selected the images to be included.”

Grading Criteria:

This assignment is worth 5 points towards your final grade.

  • 2 points: Quantity and appropriateness of participants, and appropriateness of the choice of method in relation to the participants.
  • 3 points: Quality of the insights - this includes need identified, findings based on user research, and how it identifies design challenges and opportunities

G2: Pitch Presentation

Canvas link
Due: Jan 25 at 11:30am

Now that your user research is completed, given that you know more about your target audience and topic, you should be able to come up with better and more specific ideas for projects than before. Revisit some of your project ideas in light of your newly acquired knowledge and brainstorm new project ideas. Perhaps at this point, you’ve converged as a group on a fuzzy solution or you’re still deciding between a few different solution directions, either is fine. However, you should be on your way now to converging on a problem space and developing a compelling story based on your user research as to the importance of your problem space.

In light of this project milestone, your assignment is to prepare a 3-5 minute pitch presentation to your classmates. This presentation should introduce your problem space and convince your audience of why this problem space is important, and/or why it is timely to address today. The presentation should also give the audience a deeper understanding of the problem and the people who experience this problem that you are targeting. You can talk through information from your user research as well as any additional information you’ve uncovered on the internet. Finally, end with some directions for solutions you are considering. This is a good point to ask any specific feedback questions you may have from your classmates. In class, we will dedicate up to 5 minutes per group to audience questions and feedback.

To make your pitch more compelling, consider the following tips:

  • Describe information in the form of a hypothetical story, scenario, or day-in-the-life. You could even make it a skit!
  • Share personal anecdotes from your user research participants, or direct quotes, screenshots, etc. (while keeping them anonymous)
  • If it’s relevant to them, ask your audience to think of how they experience this problem.

Submission:

Create a slide deck for your presentation in Google Slides in your group’s Google Drive folder. Submit the link to the Google Slides presentation on Canvas. You will give this pitch in class on Tues, Jan 25th. All group members should participate in giving the presentation.

In addition, each individual in the group must submit a private contribution statement at the following Google Forms link: [link]. The statement should include (1): your estimate of the percent of group work completed by you, and (2) a summary of the work you did. For example, your statement could be: “40%, researched the background of the problem, outlined the content of the document, wrote the first version of one paragraph, also selected the images to be included.”

Grading Criteria:

This assignment is worth 3 points towards your final grade.

  • 1 point: Quality and thought put into slide design and presentation
  • 2 points: Content of the pitch, including clear definition of problem, compelling motivation, and interesting and deep contextualization of target audience and problem space. 

G3: Low Fidelity Prototype

Canvas link
Due: Feb 1 at 11:30am

Produce a low-fidelity prototype that is clear enough to allow you to conduct a “wizard of oz” experiment with participants. It doesn’t have to actually work, but you need to be able to make your participants sufficiently experience it as if it is working. Your goal is to test the experience of using/engaging with your proposed design.

You will test your low-fidelity prototype on Tuesday, Feb 1 in class, so you’ll need to have the prototype ready by then. 

After testing, write up a blog post on your low-fidelity prototype and wizard of oz session. It should include 3 parts:

A- Description of your low-fidelity prototype

  • What are the components?
  • What are the parts that are ‘wizardry’? (what parts are you ‘faking’ for now but that will later be implemented)

B- screenshots, drawings, or photos (or other) of the prototype:

  • Include visual representations of your prototype (or several) that shows how people can interact with it.

C- Findings from the wizard of oz testing

  • What were your goals with this wizard of oz session: what did you want to learn and measure?
  • What did you learn in the wizard of oz session?
  • Are the findings promising enough that you would like to go ahead with the project? (If yes, describe why, if no, describe what changes you are proposing to make.)
  • What elements will you keep in your next iteration of the design?
  • What elements do you need to revise? Why?

Submission:

Format your report as a 1-2 page blog post targeted towards a public general audience. Use a new Google Docs file within your Google Drive folder we’ve created for this class. Submit the link to the Google Doc on Canvas. After we’ve left comments on the document, you will transfer the contents to your project website as a new blog post.

In addition, each individual in the group must submit a private contribution statement at the following Google Forms link: [link]. The statement should include (1): your estimate of the percent of group work completed by you, and (2) a summary of the work you did. For example, your statement could be: “40%, researched the background of the problem, outlined the content of the document, wrote the first version of one paragraph, also selected the images to be included.”

Grading Criteria:

This assignment is worth 10 points towards your final grade.

  • 3 points: Part A, which aspects were wizardry, which were not, why.
  • 2 points: Part B, visuals that are useful and well captions
  • 5 points: Part C, goals, appropriate methods used, evaluation of outcome

G4: Code and Design Specification

Canvas link
Due: Feb 13 at 11:30am

The Design and Code Specification report should contain the following components:

(1) Requirements document: Identify the requirements for the project. What will your high-fidelity prototype have to fulfill and be able to do? What user interactions will it have to support? For example: 

  • a haptic experience for users 
  • a physical component (tangible objects, IoT, a kiosk that prints...)
  • a sensing component (movement/temperature/light sensor…)
  • multiple interfaces or systems communicating with each other (API access…)
  • an inference component (machine learning, data collection…)
  • people interacting in the same physical space and/or the same time (synchronous vs asynchronous coordination…)

While your solution needs to have at least one fully implemented component, any physical parts and/or sensing components can be simulated as part of your design vision. 

(2) Storyboard: Use a storyboard to outline the complete experience of using your system, from the first interaction with the system, to initialization and completion of a social activity. Make sure it creates a cohesive experience and that each step is connected to a functionality need. Create 2 or 3 storyboard flows that show different ways of interacting with your interface (e.g. different groups of people; different task flows; different goals; etc.). 

(3) Architectural design: Identify the different subsystems and components of your project, how and when they will need to interact. You should include a figure (diagram) showing how the different systems and components are connected and how they interact and exchange data. Add a list of all the components required for each subsystem. Please also describe the figure in one paragraph. 

(4) Explain in one paragraph how your system description in (3) enables the requirements described in (1) and (2). If there are holes, iterate until (1)-(4) fit together as a whole story (do this before you submit this assignment!). 

Submission:

Format your report as a 1-2 page blog post (not including images) targeted towards a public general audience. Use a new Google Docs file within your Google Drive folder we’ve created for this class. Submit the link to the Google Doc on Canvas. After we’ve left comments on the document, you will transfer the contents to your project website as a new blog post.

In addition, each individual in the group must submit a private contribution statement at the following Google Forms link: [link]. The statement should include (1): your estimate of the percent of group work completed by you, and (2) a summary of the work you did. For example, your statement could be: “40%, researched the background of the problem, outlined the content of the document, wrote the first version of one paragraph, also selected the images to be included.”

Grading Criteria:

This assignment is worth 10 points towards your final grade.

  • 3 points: Requirements doc
  • 3 points: Storyboard
  • 3 points: Architectural design
  • 1 point: Paragraph on how requirements match system description

G5: Midterm Presentation

Canvas link
Due: Feb 15 at 11:30am

At this point in your project, you have a concrete idea of what you plan to build. You will now give a 3-5 minute presentation of your project to the rest of the class. The goal for this midterm presentation of your project to your classmates is twofold: (1) iterate on improving and fleshing out your pitch of your project (you can now incorporate more of your solution!), building from what you did in G2 to tell a compelling story and looking forward to what you will create for G8’s demo video and the final public showcase, and (2) giving an update to your classmates on your project thus far and where you intend to go, including a summary of your code and design specification, and getting class feedback on your proposed direction. This is a good point to ask any specific feedback questions you may have from your classmates. In class, we will dedicate up to 5 minutes per group to audience questions and feedback.

Submission:

Create a slide deck for your presentation in Google Slides in your group’s Google Drive folder. Submit the link to the Google Slides presentation on Canvas. You will give this presentation in class on Tues, Feb 15th. All group members should participate in giving the presentation.

In addition, each individual in the group must submit a private contribution statement at the following Google Forms link: [link]. The statement should include (1): your estimate of the percent of group work completed by you, and (2) a summary of the work you did. For example, your statement could be: “40%, researched the background of the problem, outlined the content of the document, wrote the first version of one paragraph, also selected the images to be included.”

Grading Criteria:

This assignment is worth 3 points towards your final grade.

  • 1 point: Quality and thought put into slide design and presentation
  • 2 points: Content of the pitch and summary of code and design plans

G6: User Testing

Canvas link
Due: Feb 27 at 11:30am

To prepare for user testing, please build a medium-fidelity prototype of your concept. Following the agile software development approach, implement (code) at least 2 functionalities of your system to test. It is up to you to decide what functionalities you implement.

Be prepared to have others test your system in class (on Tues, Feb 22) and also arrange for people (can be your friends or family) to test it at other times. 

What you will test:

  • Your user testing should test the implementation of at least 2 coded functionalities of your prototype. This means that you should test if a user is able to accomplish the task you planned for them with these functionalities.
  • Please have at least 3 separate user testing sessions. You can choose to organize each user testing session the way you would like. If you are not sure, we suggest splitting each participant session into 2 parts:
    • Observe them using your system. Ask them to follow a think-aloud protocol.
    • Conduct a very brief semi-structured interview to ask about specific questions you might have. You should have the semi-structured interview scripted beforehand, following specific questions that help you to learn whether your prototype meets your goals and to learn more about the user experience of your prototype. 

After your user testing sessions, write a blog post report answering the following prompts:

A- Description of your medium-fidelity prototype

  • What are the 2 functionalities you implemented (coded)? Where in your GitHub repository can we find the code for it and what Github issues address those functionalities?
  • How did you prototype the other functionalities? (Did you omit them, or wizard-of-oz them?)

B- Screenshot/photo of the prototype:

  • Include a screenshot or a few screenshots of your prototype.

C- Findings from the user testing sessions

  • What did you learn in the user testing sessions?
  • Are the findings promising enough that you would like to go ahead with the current functionality of the prototype? (If yes, describe why, if no, describe what changes you are proposing to make.)
  • What are the next functionalities that you will implement in your prototype?

Submission:

Format your report as a 1-2 page blog post (not including images) targeted towards a public general audience. Use a new Google Docs file within your Google Drive folder we’ve created for this class. Submit the link to the Google Doc on Canvas. After we’ve left comments on the document, you will transfer the contents to your project website as a new blog post.

In addition, each individual in the group must submit a private contribution statement at the following Google Forms link: [link]. The statement should include (1): your estimate of the percent of group work completed by you, and (2) a summary of the work you did. For example, your statement could be: “40%, researched the background of the problem, outlined the content of the document, wrote the first version of one paragraph, also selected the images to be included.”

Grading Criteria:

This assignment is worth 9 points towards your final grade.

  • 2 points: Part A: description
  • 2 points: Part B: screenshots that are useful and well captions
  • 5 points: Part C: findings from the session

G7: Digital Prototype

Canvas link
Due: Mar 5 at 11:30am

Your final blog post and high-fidelity prototype submission will contain 2 parts.

A-Blog post report:

This is the final summative blog post in your project’s blog series. Remind the audience of your problem or need you saw as well as the population/audience you are targeting. Present a description of your final prototype, both from a design and a technical perspective. Discuss any technical issues that came up during your implementation phase and also discuss any pivots you took due to technical issues or findings from testing. Provide your audience with a link for where to access your prototype and encourage them to try it out! Also, provide a link to your Github repository. Please include high-quality screenshots of your prototype. The screenshots should communicate well what the prototype is about for people who have not seen it in action.

B-Implementation of a high-fidelity working prototype 

In addition to your blog post, we will assess the level of finish (both in terms of design and implementation) of your high-fidelity prototype. Make sure that your design is usable in a way that a stakeholder could test it out. This also includes good documentation of your code and a read-me file in your repository that tells people how to install/use it.

Submission:

Format your report as a 1-2 page blog post (not including images) targeted towards a public general audience. Use a new Google Docs file within your Google Drive folder we’ve created for this class. Submit the link to the Google Doc on Canvas. After we’ve left comments on the document, you will transfer the contents to your project website as a new blog post.

In addition, each individual in the group must submit a private contribution statement at the following Google Forms link: [link]. The statement should include (1): your estimate of the percent of group work completed by you, and (2) a summary of the work you did. For example, your statement could be: “40%, researched the background of the problem, outlined the content of the document, wrote the first version of one paragraph, also selected the images to be included.”

Grading Criteria:

This assignment is worth 20 points towards your final grade.

  • 5 points: Final blog post
  • 12 points: Quality, usability of the final prototype, completeness according to code and design spec
  • 3 points: Quality of organization in Github repo, including documentation of code, quality of documentation in issues, commits, pull requests

G8: Video Demo

Canvas link
Due: Mar 7 at 11:30am

Building on the two more formal presentations you’ve given in class, you will now produce a video demo of your product of no more than 5 minutes. The video demo must include two components:

(1) A compelling motivation of the problem and the solution. Remember our tips from earlier and “show not tell”. Think about what it is about short videos you’ve watched, such as on social media or on TV, that make them compelling. This should be an evolution of what you’ve already done for G2 and G5 (can even reuse some of the slides perhaps).

(2) A live recorded demonstration of your digital prototype in action. Depending on your system, this can sometimes be better as a screenshare or a video recording. The demo should go through all the main tasks and scenarios your tool supports. You can use voiceover and text captions, labels, or arrows in the video to help explain what is going on. 

Conclude with a final takeaway message for your audience.

Submission:

Upload your video to YouTube. Submit the link to the YouTube video on Canvas. After we’ve provided comments, you will add the video to your project website as an embedded video.

In addition, each individual in the group must submit a private contribution statement at the following Google Forms link: [link]. The statement should include (1): your estimate of the percent of group work completed by you, and (2) a summary of the work you did. For example, your statement could be: “40%, researched the background of the problem, outlined the content of the document, wrote the first version of one paragraph, also selected the images to be included.”

Grading Criteria:

This assignment is worth 8 points towards your final grade.

  • 3 points: Compelling motivation of problem and solution
  • 3 points: Video demonstration of prototype
  • 2 points: Quality of presentation

G9: Website

Canvas link
Due: Mar 14 at 11:30am

The last thing for this project is to put the finishing touches on your project website. If you’ve been updating the website over the course of the quarter like we asked, you should have very little to do at this point. This website will serve as the splash page/landing page for your finished product, and something you can point to in your portfolio. Thus, you will want to carefully consider the design of the main page. Think about your favorite software apps and tools and go to their homepage (not logged in) for inspiration on how to design a landing page.

The website should include the following information:

  • Logo, name, tagline, etc.
  • Information about you (photos, names, contact info, roles…)
  • Video demo
  • Blog posts
  • Link to final digital prototype
  • (potentially, depending on your vision for this landing page) screenshots or descriptions of your final prototype, images or tidbits from the design process, or anything else you want to bring out of your blog posts to spotlight on this page

Submission:

Nothing to submit as we already have your website URL.

In addition, each individual in the group must submit a private contribution statement at the following Google Forms link: [link]. The statement should include (1): your estimate of the percent of group work completed by you, and (2) a summary of the work you did. For example, your statement could be: “40%, researched the background of the problem, outlined the content of the document, wrote the first version of one paragraph, also selected the images to be included.”

Grading Criteria:

This assignment is worth 4 points towards your final grade.

  • 2 points: Website content
  • 2 points: Website presentation