Design Project 6: Project Showcase
Project Showcase: 12:30-2:15pm on 6/22 (Mon), slide by 11am
Final Submission: 11:59pm on 7/6 (Mon)
15% toward your total grade
What do we do?
Finally, it's time to present your design process and the resulting interface to the entire class, both orally and visually. During our final project showcase, each team will give a 1-minute "madness" presentation in front of the whole class. In addition, you'll create a maximum 2-minute video clip that captures user needs, tasks, and an interface walkthrough.
- Studio: There's no studio session for DP6. If you want to get feedback or talk to your TA about the final presentation or report, please contact your TA individually.
- Final Pitch & Demo:
In the project showcase session, each team will give a 1-minute pitch of their project
and do a live demo + interactive Q&A in breakout rooms.
Part 1. 1-minute pitch: Decide what part of the design process you want to convey to the audience, in 1 minute. Which part do you think is most exciting and strongest? What is your unique point of view on the problem, and why is your UI a usable and useful solution to the problem? You won't have time to explain details, so focus on the main points and lessons.
You should assume that the audience knows nothing about the problem space and your solution. Also keep in mind that we'll be listening to over 20 talks non-stop in class: think how your presentation could stand out. Make sure to include a hook that will get people excited about your project. Avoid using much text and actively use visual artifacts from various stages of the design process.
You are allowed to use one slide for your pitch.
NOTE: You may use animations and embedded videos in your one slide. But we won't be manually advancing them on behalf of you. This means that everything should automatically advance/play. We will start your slide and move to the slide after 1 minute.
Part 2. Demo:
After the madness presentation, we will put you into a few breakout rooms organized by theme of your interface. This means (ideally) teams that are working in similar problem areas would be put together. In this session, each team will be given 5 minutes to show a live demo of their interface to the audience followed by 3 minutes of Q&A. You can share a link to your working prototype if you want others to live test it. Your team will get 8 minutes total.
After the pitches and the demo session, we'll hand out a few awards based on different categories, such as "most extreme user", "best implementation", "people's choice", etc.
- Video: Record a 2-minute video that captures the user context and the killer features of your UI. Be creative in how you plan, structure, and record the video! Here's an example. Also look at last year's CS374 project gallery. Revisit your storyboards, as they capture the rich usage context. You need to set the stage by starting with users and their problem. Avoid using slides and try to capture realistic context, and don't hesitate to "act". Do not show the UI from the beginning. You need to show parts of your final prototype to demonstrate how the user might perform the task using your system. Rather than describe all the features you implemented, focus on the flow of the task.
NOTE: Make sure to connect the user scenario and the solution. A common antipattern is to make the UI description too generic, not about solving the particular user problem captured earlier in the video.
NOTE: Due to the pandemic, we recognize it'd be near impossible to record a video of multiple humans interacting. In grading the videos, we will not focus on interaction between characters. Feel free to use animated characters, split screens with multiple characters captured separately, etc. to creatively communicate the idea behind your interface. We will not focus on the production quality regarding this aspect of your video.
- Final Report: The final report will be brief. You need to simply include the following:
- Final Interface
- Representative screenshots: Include a few most important screenshots that showcase the uniqueness of your application. Add callouts, annotations, or captions.
- Quality arguments (limit: 500 words): Make convincing arguments for what makes your interface "great". Add comments from users, UI screenshots, etc. that could support your arguments. Depending on your interface, you may focus on different aspects: neat features, visual design, usability, novel UI components you designed, hardcore implementation, etc. This is your chance to convince us that what you created is a high quality user interface.
- Iteration (limit: 300 words): How did you spend the DP6 period for iteration? Why? What changes did you make? Show concrete examples and data whenever applicable. What did you learn?
- Individual reflection (limit: 500 words per person): Each member should write this part on their own, reflecting on their personal experience. Merge all members' mini-reports in the final report. Please answer the following questions:
- What part of the UI implementation did you contribute to? Be concrete and honest, please.
- What worked well and not in your team? How did you overcome any hurdle in teamwork? What lesson about teamwork did you learn that you might apply to your next team project?
- Through the team-based design project experience, what did you learn about the user-centered design process and web-based GUI implementation?
Final Pitch and Demo (20%)
- Pitch: How engaging, creative, and effective is the overall pitch?
- Demo: Is the demo working well and are people able to try it out?
- 2 minutes or under?
- Overall organization and flow of the story?
- Quality and variety of shots and rhythm?
- User needs well captured?
- UI introduced convincingly but not as dry list of features?
- Engaging and creative?
Team Report (30%)
Quality of the Final Interface (15%)
- Convincing arguments with supporting evidence?
- Is it overall a high quality interface? We will look at a variety of aspects such as completeness, novelty, feasibility, UI-level contribution, etc.
- 500 words or less?
Iteration Report (5%)
- Iteration period is spent efficiently and effectively?
- Justification is convincing?
- 300 words or less?
Individual Reflections (10%) -- graded individually
- Individual contribution clearly specified?
- Teamwork discussion includes both the good and the bad?
- Teamwork discussion has enough depth and insight?
- Design process discussion has enough depth and insight?
- 500 words or less?
Final pitch slides are due by 11am on 6/22 (Mon), 1.5 hours before the final showcase. Video and the team report are due by 11:59pm on 7/6 (Mon).
: For a smooth transition between presentations, we'll require all teams to use Google Slides for presentation, just like in studios. Each team will receive a link to a Google Slides presentation from the TA. During the final showcase, we will open your slides from our computer, and your team will have exactly 1 minute to present. Please note that there will be a hard stop after 1 minute
: unfinished presentations will be cut off. We recommend that you rehearse in your team in advance. Not every team member has to present
but we still expect everyone to present in the live demo and interact with other students after the pitches.
: (guidelines adopted from CHI 2017 Video Showcase
, which also has links to many inspiring videos)
- Encoded as an MP4 using the H.264 codec. No exceptions!
- You'll upload your video file on YouTube. Include the URL of your posted video in your final report.
- All spoken dialog must be closed captioned (subtitled) to improve accessibility.
- Resolution of at least 1280px x 720px.
- The 16:9 aspect ratio is recommended.
: One report per team. Your report should be submitted as a zip file. The main report should be written in Markdown
(please use the .md
extension). Also include your original video MP4 file in the zip file as well.
Name the file with your team name, and submit it by visiting this link
. You can submit multiple times until the deadline, and we'll use the most recent version for grading.