First, decide what features of your prototype, process, and research you want to communicate. What is the unique point of view that your design expresses? This is not a marketing spiel. It's about communicating a conceptual insight: what is your clear and novel value proposition? Do users know what they're there for, what they can do, and why your design hits a user need better that existing alternatives?
Consider the two visual deliverables you are creating, the slide and your poster, and how their content should differ. Your poster (and demo) should convey your design decisions, iterations, and what you learned from users. Take the core concepts and communicate them rather than explaining every detail. Your pitch should boil your work down to its essence. The slide is a high-level look to entice people to come and learn about your project, and it should show a screen (or two) of the user interface that you worked so hard to create.
Prepare for your slide and pitch by thinking about how you want to introduce your prototype for the first time. You have thirty seconds, and most of the audience has never seen your application before. How can you provide a high-level understanding of what your application does, or what needs it addresses? Find the "hook" that will interest people and persuade them to find your poster later on. Imagine you are trying to impress a new potential investor on a happenstance elevator ride. We recommend scripting your presentation and practicing it many times until it is smooth. We will have a timer running, and any presentation that goes over 30 seconds will be cut off.
The show opens with your pitches to give you a chance to share your work with all your fellow students, staff, and visitors. Make sure to share your key design insight.
How you are going to explain your prototype to people? Will you hand your mobile Web application to visitors to try, or will you walk them through a demo? Why did you make that decision? What are you going to say to them? What part of your design do you want to emphasize? Keep in mind that attendees don't have all the background and insight into your application. Present them with the user need first, show your solution, and explain why your work is unique. Your poster should stand on its own without explanation. There will be many people there and you will not be able to engage every single person who will look at your poster.
Finally, prepare a 1-minute demo of your prototype. Keep it short, while showing off all the features of your application. When jurors and visitors come to your poster, your quick demo should inspire them to pick up the phone and continue to play around with your app. It is important to have a demo rehearsed. There will be many people there and it is important to come across as prepared and knowledgeable to your visitors.
Each poster will be visited by two critics (staff and/or jurors).
Your poster will be kept by the staff for archival and display purposes.
Studio attendance is important this week, as you will be giving your rehearsed demo to your studio and studio leader, and you will be evaluated based on this.
Here are several student examples of slides and posters from previous years. These are electronic versions, but yours will be on butcher paper. Be sure to make it clear what your app actually does in your poster and demo.
|Presentation is unplanned and confusing.||Presentation sufficient to convey project concept.||Presentation had a good flow, was memorable and creative. People wanted to visit your poster||Presentation was very well planned and had unique and creative elements that made it stand out. The 30 seconds was memorable and the time carefully utilized. People clamored to visit your poster.|
|No poster created.||Poster is poorly made and sparsely communicates the basics of the application. The poster requires the team to be there to explain the details of the application.||Poster clearly communicates the key points of the application and the design process that led there. The poster can stand on it's own, but the visual layout and content do not sufficiently convey the point of view.||Poster creatively communicates the design process, the design goal, and conveys the point of view. The poster stands on its own and there is no filler content on the poster.|
|The demo wasn't shown to the TA or the demo hasn't been planned out or rehearsed. It is a total mess and doesn't present any useful information.||The demo has been planned out, but not rehearsed at all. The demo shows one of the following items: main point of the app, creative view point, and a compelling scenario.||The demo has been planned out, but is not well rehearsed. The demo shows two of the following items: main point of the app, creative view point, and a compelling scenario.||The demo has been clearly rehearsed and carefully planned out. The TA can immediately answer the following questions after your demo: What is the problem your app solves? Does your app take a creative point of view? Do you show a compelling scenario? Is your app different/better than other ways people could solve the same problem?|
|Prototype not submitted.||Prototype exists but has a few lingering bugs. Interface appears rough. Evolution of the application throughout the quarter is minimal.||Prototype functions smoothly, but may still have an "unfinished" feel. Clear progress has been made throughout the quarter to improve the interface.||Prototype is high quality and simulates the experience of a fully-formed application. The user experience is smooth and realistic. Significant progress has been throughout the quarter to improve the user experience and help the user accomplish the task at hand.|
||While the team articulates a user need, it isn't that compelling. It may be a gadget doesn't fill a real user need.||The pitch, demo, and poster clearly articulate a real user need, but the design doesn't fully address that need.||The pitch, demo, and poster clearly articulate a real user need, and the design elegantly addresses that need.|
|Point of View
|Unclear from the Pitch/Poster/Demo what the point of view is.||Pitch/Poster/Demo have a point of view, but it's run-of-the mill. It's not clear what's unique about this prototype.||The prototype has a clear point of view, but it doesn't quite line up with a user need or fill a hole unmet by similar applications.||The pitch, poster, and demo conveyed a clear and unique point of view. The point of view clearly conveys how the design differs from prior work.|
|Out of the Box2 pts||The pitch memorably and creatively conveyed a user need and value proposition. The poster and demo clearly showed how the ptototype achieves that user need. The idea has a unique point of view.|
During studio, click here to evaluate the Intro HCI Class. During studio, click here to evaluate the course using the cog sci form (even if you are not a cog sci student). During studio, click here to assess your group's work as a collective unit. During studio, click here to assess your own work and each of your team member's work. During studio, click here to give your views about learning.