Name of Interface Tagline if you have one (80 chars max, including spaces)

Name of InterfaceTagline if you have one(80 chars max, including spaces) Team member names and schools/yearsTeam member emails

The problem(s) • Describe the problem(s) your interface is designed to solve in one or more slides

Motivation • In one or more slides, describe how you identified the problem(s)

Surprise(s) • In one or more slides, talk about anything that surprised you about your users (i.e., what changed between your initial expectations and your final understandings of your users, based on your ethnography, reading, prototype testing, etc.

The best today • In one or more slides, describe the interfaces that already exist that are closest to what you have created • Describe why those interfaces fail to solve/address the problem(s) you have identified

Innovation • In one or more slides, summarize what is particularly new and exciting about your approach • Explain what helped you to figure out this novel solution; how did you come up with the idea?

(Add descriptive title) • Use the next set of slides to describe your interface ... Storyboard how it works. Using screenshots and/or real photos of people using your application, give a scenario showing how typical usage would solve the problem(s) you identified earlier.

Demo • Now switch to a live demo. You may not be able to show your whole interface, so focus on one part. Explain some design decisions. • You will be cutoff after 3 minutes, so take no longer than that. Please practice this so that you know you can make interesting points in the allocated time.

Demo • You must be able to project the demo on the screen, and it is your responsibility to make sure the transition between slides and demo goes smoothly and quickly.

(Add descriptive title) • Your presentation must be between 12-15 minutes long (in the 20s per slide format and including the 1-3 minute demo, as well as the 1-2 minute video, should you choose to include it) • You can decide where you need to allocate more or less slides to particular topics) • After each presentation we will have 6-8 minutes of Q&A

(Add descriptive title) • On all slides, do not change this font or use a smaller font size • Do not change the slide style or background. Focus on content! • Each slide should be 20s and auto advance, as we’ve done throughout the course.

(Add descriptive title) • Do not put too much text or more than 1-2 images on any given slide • You only have 20s per slide!

(Add descriptive title) • Images are strongly preferred to text when they can be used to illustrate a concept • But, avoid gratuitous clip art

(Add descriptive title) • Do not put text or images on the slide that people will not have time to read

(Add descriptive title) • There is no need for everyone on your team to present part of the presentation. You can do that if you wish, or you can pick the best presenter and have that person do it. • Look at your audience not the computer screen (because you know what you need to say because you have practiced!)

(Add descriptive title) • If you do not practice • And practice • And practice • At least 3 times, or you will get behind your slides and it will be painful to watch • You should pick the best presenter to present the project. Do not arbitrarily split up the presentation. All team members can answer questions.

Video • If you want to insert a user test video into your presentation, you can do that here. The only video you can show is this: • A video of a user testing your final interface. The video should be no longer than 2 minutes, and it should show something interesting that you can comment on as the video runs (e.g., a place where a user had trouble or a place were the interface use went very smoothly)

A UI challenge • Focus in on one specific UI challenge you encountered. In one or mores slides, show your initial idea for one part of the interface (e.g., a particular screen) and then describe the problems you discovered in testing and how you solved them. • In other words, step us through the evolution of your thinking.

Tricky programming problem • In one or more slides, describe one example where the UI design impacted your programming, or the programming impacted your UI design.

The future • Critique your interface. • What could still be better and why? • Why didn’t you fix the problem(s) or fix the concept?

Your future process • Based on everything you learned in the course, what would be the next steps you would take to design or redesign the interface? (NOT what would you do, but instead HOW would you go about doing it based on what you’ve learned about UI design?)

Acknowledgements • Give credit where credit is due for ANY borrowed code, borrowed images, borrowed sounds, etc. • If another team helped you out substantially, give them kudos

(Name of your interface) • Finally, on one slide, summarize what your interface does and the problem(s) it solves and why.

Name of Interface Tagline if you have one (80 chars max, including spaces)