Final Presentations

Due: Saturday, May 11th, 8-10AM (during our finals slot)

Assignment Overview
In this assignment, you and your teammates have an opportunity to show off the hard work you've done in this class. You will present your final projects to the class in seven minutes followed by two minutes of questions. As before,
We will be timing the presentations and will cut you off if you go over so you mustrehearse beforehand. Seven minutes is short. Seriously short. You need to rehearse. If you don’t, I can almost guarantee you that you will go over time, and we will be forced cut you off. You do not want this to happen.

Your presentation should include a live demo of your prototype or a pre-recorded video of the prototype (or both). You could also include video of your usability testing sessions (as long as the video does not reveal the identity of the participants).

As before, you are welcome to have just one or two team members to present the content if you think it will make the presentation go smoother.

Talk Breakdown

The talks will be seven minute presentations plus two minutes Q/A. You must use my laptop to mitigate transaction costs between switching teams. Unlike last time, we will not be video recording the talks (for two main reasons: (i) my video camcorder came to an early demise and (ii) though I think it's also edifying to watch yourself give a talk, it's the end of the semester and I'm sure you all just want to enjoy your summer).

I'll be fairly flexible in how you present. As usual, I will reward creativity and risk taking. In addition, though I would like at least 30% of the presentation to be live, the rest can be a prepared video. Alternatively, the entire presentation can be live including the demo. It's up to you.

I will not enforce an ordering requirement, so the following list is suggestive. However, this is the content that be in there:
  1. A title with tagline
  2. Problem motivation
  3. Problem description
  4. Quick overview of solution
  5. Differentiate from past solutions to problem
  6. Your design process
    1. Include brief description of the three tasks your prototype was designed to support
    2. Overview of sketching -> lo-fidelity -> interactive prototype evolution
  7. Study method
  8. The results from your usability tests
  9. Live demo or video-recorded demo
  10. Areas for future work
  11. Summary and conclusion

It might be easiest to split up the "Study method" and "Results from usability tests" into two parts: one dedicated to the lo-fidelity prototype testing and results and the other dedicated to the interactive prototype testing and results. Brainstorm and discuss with your team on how you want to do this.

Talk Example

So, for example, let's imagine that we worked on Professor Leah Findlater's project WalkType--an adaptive keyboard system that attempts to improve typing while walking--and we have to prepare a seven minute presentation. Here's what it might look like. Note, I have included the number of slides I would create and the total amount of time I would spend on each topic if I were giving the presentation. These are only estimates. The timing format: (time on topic | total running time in presentation).
  1. Title/Tagline (1 Slide) : ~10 seconds | 10s
    1. Title: WalkType: Using Accelerometers to Improve Typing
    2. Tagline: Doing Two Things At Once Just Got Easier
  2. Problem Motivation (1-2 slides): ~20 seconds | 30s
    1. Slide 1: slide showing growth of touchscreens across the world; make point that touch screen devices are now the dominant platform in mobile computing
    2. Slide 2: slide showing people using touchscreens in a variety of contexts. Key point: computing has shifted off the desktop to pervade nearly all aspects of our lives... but...
  3. Problem Description (1-3 slides): ~30 seconds | 1min
    1. Slide 1: the lack of tactile feedback on touchscreens requires a high level of visual attention to select targets accurately
    2. Slide 2: input is particularly challenging when the user is in motion (callback to slide 2; maybe pop up one of the same pictures). These active states can be thought of as causing "situational impairments," which may be caused by divided attention, diverted gaze, awkward posture, cold temperature, glare, etc
  4. Quick Intro Of Solution (1-2 slides): ~30 seconds | 1:30
    1. Slide 1: In this presentation, we will provide an overview of one solution to address this problem. We are building a better touch entry system for walking that automatically adapts to the user's movement. We call this system WalkType.
    2. Slide 2: WalkType works by sensing a user's movement using a smartphone's built in accelerometer and automatically adapting the key press inference model
  5. Related Work (1 - 3 slides): ~30 seconds | 2:00
    1. Slide 1: quick overview of other specialized keyboards/interfaces for walking (e.g., Mizobuchi et al., Kane et al.); close with differentiating statement (e.g., most of this work is preliminary and no one has explored automatic adaptiation of keyboards from accelerometer input)
    2. Slide 2: quick overview of adaptive keyboards; again close with differentiating statement.
  6. Design Process (1 - 3 slides): ~30 seconds | 2:30
    1. Slides 1 - 3: High-level overview of design process: e.g., we used an iterative-design process. Briefly show sketches evolving to mid-fidelity evolving to interactive prototype
  7. Study Method (1 slide): ~30 seconds | 3:00
    1. Slide 1: Describe usability testing method with lo-fidelity and interactive prototypes (e.g., how many users, what setup was used, what methods). In WalkType's case, they recruited 16 participants (8 male, 8 female) for a within subjects design. Participants used the WalkType keyboard and the default smartphone keyboard (the control) in two counterbalanced conditions: walking and sitting.
  8. Study Results (1-4 slides): 60 seconds | 4:00
    1. Slide 1-4: First present results from lo-fidelity testing (e.g., we learned X and Y) and then the results from interactive prototype testing (e.g., we learned X and Y). Could also show video of usability tests if quick and participant identities masked. In the case of WalkType, the WalkType keyboard improved typing speed regardless of whether the user was sitting or walking: on average 31.1 words-per-minute (WPM) compared to 28.3 WPM. Also include subjective comments from participants (e.g., participants felt that the WalkType keyboard felt more natural--even though there was no visual distinction between the WalkType keyboard and the control)
  9. Live Demo or Video-recorded Demo of Final Interactive Prototype: 60-120 seconds | 6:00
    1. Slide 1: in the case of WalkType, could show a version of the software that highlights the key press inference model and visualizes the accelerometer as each key is pressed
  10. Future Work (1 - 3 slides): ~30 seconds | 6:30
    1. Slide 1: Based on our studies, we identified X and Y limitations, which we hope to address in future work.
    2. Slide 2: We also plan on releasing the source code to github. Go to <project website> to find out more.
  11. Conclusion (1 slide)
    1. Slide 1: We built and tested the first adaptive keyboard that uses sensed accelerometer data to automatically adapt the keypress model.

Grading Rubric

Here is the grading rubric for the final presentations (link).

Presentation Tips

  • You can use any presentation medium you prefer except for Prezi. Last time, many of you chose to use Google Docs; I think this is fine but please make sure the slides don't look thrown together at the last minute with randomly placed clip-art and long bullet point lists.
  • To reduce delays between presentations, we will be presenting off of one single laptop. Thus, if you use a custom font in PowerPoint or Keynote, please make sure that this is loaded onto the presentation laptop.