What email address or phone number would you like to use to sign in to Docs.com?
If you already have an account that you use with Office or other Microsoft services, enter it here.
Or sign in with:
Signing in allows you to download and like content, and it provides the authors analytical data about your interactions with their content.
Embed code for: 2013 Design Expo Guidelines
Select a size
Microsoft Research Design Expo 2013 1 Guidelines for MSR Design Expo Redmond, Washington July 14-16, 2013 Microsoft is pleased to announce Design Expo 2013 and welcomes your participation. Design Expo showcases exceptional design process and ideas from schools around the world. As part of a semester long course, students are asked to form interdisciplinary teams of 2-4 students, consider people’s real needs and respond with a user experience prototype, and narrative that explains their thinking. A representative team from each school will be selected to attend and be featured in a presentation at the 2010 Microsoft Faculty Summit July 14-16, 2013 in Redmond, Washington. The Design Expo creates a forum for spotlighting design, encouraging “out of the box” thinking, by exploring students' visions for the future of computing as well as honing their presentation skills and engaging with students from other design teams from around the world to see how they approached this year’s theme. Students often form lasting relationships with other students and this informal network has persisted from Design Expos over the years. This year your Co-Chairs for the Expo are Lili Cheng (email@example.com) and Michael (firstname.lastname@example.org) Table of Contents The Design Challenge: (TBD) Example Scenarios Design Process Project Stages Investigation & Conceptualization Prototype Presentation & Demo Key Design Points Microsoft Research Goals for Design Expo 2013 Design Expo 2013 Agreement to participate Participation Grant Visit by Liaison Project Assessment Assessment Criteria Submission Requirements Publicity & Ownership Important Dates Contacts Microsoft Research Design Expo 2013 2 The 2013 Design Challenge: Making Data Useful: Improving your life, community, and world Increasingly we live in a world alive with sensors and data. The big data, sensor networks and transparency movements have left us with a supply-side glut of potential useful free data that is lying fallow. How can we use this to improve life, local community and the world at large? People and devices collect and share data both passively-monitoring environmental change, and actively-explicitly capturing and sharing information, combining data with other information and using in unexpected ways. Today, we are only at the beginning discovering how to put this data to work to improve our lives and the world around us. How might data, particularly information that makes civic society run – bus schedules, election cycles, political information, first-hand reporting, volunteer logistics, sporting and media events – make for a better and more community oriented place to live? How might this data help us understand the past, the present and predict the future with more precision, and how might an individual’s personal data be used to help filter and make information more relevant in different contexts or situations. What are key problems this data can be used to help solve, what new troubles can we anticipate it creates? --------------------------------------------------------------------------------------------------- Overall Process Communicate your design by first explaining the situation (via background research, interviews with your users, and describing the local culture and work environment), and then explaining your design solutions (through scenarios, innovative designs and interface simulations/prototypes). We encourage you to think beyond traditional software, toward solutions such as lightweight user interfaces for inputting (entering) and outputting (disseminating information) which integrate with everyday life. Examples Because this is a very broad topic, it will be critical for you to focus in on a particular community, type of data, and problem you feel has impact. Also, as you work thru the project, using real data and designing the flow of data is critical. Below are some types scenarios and data you might begin with to narrow in on a particular project: Physical objects. Imagine physical objects with sensors: a door that knows when it’s opened; a refrigerator that knows the ambient temperature of the kitchen; a car that knows when it was turned off and on, and how far it traveled; shoes recorded with speed and GPS data; a television that allow you to tell it what you like and what you don’t. With all this data from my personal objects, how might it actually improve my life in a holistic way? Public community data. Local data about my city-- Bank transactions, communications with friends, media consumption patterns, travel and commute patterns, consumption patterns, health information and weather information. How can these swaths of data be combined in innovative ways to add value to our individual lives? What would make things easier? Better? More enjoyable? City life, City data As I walk down a city street, cameras are tracking my movement, automobile traffic, and the surrounding environment. We know about neighborhoods and local politics and news. Citizens share Microsoft Research Design Expo 2013 3 and report events using social networks. How might a city partner with a group of local residents to solve a particular local problem? Family Tree of Life In the old days, people used the family tree metaphor to record family history. What might a family tree do and how might it represent personal past, present and future— Collection and curation of stuff I care about There is so much information flowing in real-time today, we spend less time and effort personally organizing and collecting information. As all my information spreads out, and information I care about spreads out, how can we better collect, curate and share what’s important? Design Process The goal is not to have all projects address the same problem and this is not a competition about who has the “best” solution to a focused problem. It is more important for the students to interpret the theme according to what they feel is important while still achieving the goals that the professor has for the class. The resulting spectrum of design solutions will provide a number of unique and innovative views on the potential future real time data transmission and seamless connectivity technologies. Project Stages Each class will divide into teams of 2-5 students, who will all consider the theme and context. In an ideal process, student teams will first understand the problem, decide on an audience to address, develop scenarios and design solutions that address the needs, iterate on the solutions and finally develop a prototype and presentation that tells the story of their process and highlights their solution. Team work Assemble as broadly based interdisciplinary team as possible, aim to include different skill sets—graphic designers, film-makers, psychologists, anthropologists, programmers, musicians, marketers etc. Recognize that by virtue of the fact that the team is from different backgrounds they will disagree and argue, so the design solution will have to evolve. Investigation & Conceptualization In order to understand your specific design problem, it is essential you research previous work in the topic area to prevent “re-inventing the wheel.” Interview real users to understand their point of view and their specific situation, issues and problems to prevent “designing for yourself.” Remember you are not the user. Get feedback on “paper prototypes” as soon as possible to “learn from your mistakes early”. Design is an iterative process and the professors will work with the students through iterations of the ideation phases to continually refine the scenarios and concepts to get progressively more tangible form (e.g.: storyboards, video sketches, etc.) or other artifacts as chosen by the professor. Your Microsoft liaison will work with you throughout the process to ensure sufficient progress is being made. The purpose of this is to allow time for iteration and feedback, and to avoid all of the work happening in the last week before everything is to be completed. Prototypes Once scenarios are refined, the teams will focus on building a design prototype, interaction and user experience. Ideally if the design solution involves software, students should mock up what a user would see and do, thinking through the interface, the context of the user and how their needs have been addressed. Students should feel free to use whatever tools they feel comfortable with in doing this kind of work. In prior years, students have used tools such as Flash, Silverlight, Html5 or other programming Microsoft Research Design Expo 2013 4 tools to help create the illusion of the experience. Others have made movies of part of the experience to set the context. Think beyond traditional software, toward solutions such as lightweight user interfaces and designing user interaction for your particular scenario and solution. The interfaces and interactions should be designed more to communicate what is unique about the experience. That may be done more effectively with designing an interactive prototype (even if it is a scripted click through) that demonstrates the thinking behind the experience and the interaction design. The goal of the prototype is to create a vehicle which best communicates the tangible experience of the design solution. The Microsoft liaison will work with the professor to determine the practical milestone date for the prototype completion and the nature of what makes and appropriate prototype. Additional design process suggestions Establish a design process with a schedule and use it to help meet your project goals and to mediate your design decisions. Often too much time is spent reaching consensus and brainstorming up front, then too little is left to be spent on the final design aspects of the final project. Decide up front who and what will be documented throughout—do not document after the prototype is ‘finished’. This work in progress should be posted often to the Web site for your team’s project. Describe and meet your “ultimate” real users. Then interview these users to find out their problems, needs and desires. Study existing products, markets and research findings, so you do not re-invent some existing work. Prototype your ideas often and in rough ways and forms. Use these to gain feedback from your users, before you start building or designing anything more complete. Do not forget to keep a log of your prototype for later inclusion in your design story. Consider how your design concepts relate to other situations. We think it is useful to design prototype concepts that can be adapted to suit other people for different purposes and with different life styles. This can help to lengthen the product cycle and allow users to customize and personalize their own devices. Simulate the look and feel of the user’s tasks or sequences of operations with any available prototyping tools such as Flash, Silverlight, etc. Please try to make sure you can show your work/presentations on Windows and/or Internet Explorer. This will make remote feedback and presentation setup much easier. If you need additional Microsoft Software (Visual Studio, C#, SQL, etc.) to build your prototypes please let your liaison know and we will try to get you this software. Repeat your cycle of design with users several times and show how you changed your product and interaction design directions. Make physical mock-ups of the devices, wherever appropriate. Document any design evolution stages to include later in your presentations. Send or link to a final copy of your presentation so we can share with others Project Selection Prior to the final selection date (May 6, 2013) the professor, other relevant faculty at the school and a MS liaison will evaluate all the student projects and select one team to represent the school at the Faculty Summit in Redmond, WA. Presentation & Demo The final presentations will be made by the student(s) and are typically approximately 10 minutes long covering the problem definition, research findings, scenario, design process (including user feedback), Microsoft Research Design Expo 2013 5 and the design solution. Presentations in the past have been done in PowerPoint, Keynote or Flash and have often included other media or demonstrations of concept prototypes to help illustrate the point. Additional Presentation tips Practice your talk including all your props. This can be usefully done alone, with team members, and with novice audiences. Video tape yourself for practice, it is a great learning experience. Time your talk to get a better feeling for how long it takes to describe things clearly to a novice audience. Never underestimate how little the audience knows about what is so interesting about your project. The audience will engage more if you are enthusiastic and engaging. You’ve put a lot of effort into your work, so speak with enthusiasm and energy. Make slides visible from the back of a large room (try them out!) Do not talk over any audio in your presentation. Give a copy of your final presentation to your liaison. Presentation slide topics to include WHO—team members’ backgrounds WHAT—what was designed and for whom? What is the design point of view you took? WHY—why is this an important/useful need or problem to address? HOW—describe the design processed used DESIGN—show highlights of the prototyping process. Show iterations of the design evolution (what worked what did not work) Show specific details that demonstrate how well you understood and solved the problem CHALLENGES—what were the problems encountered? What did you learn and what would you do differently? WHAT’S NEXT—what are your next steps? Where would you take your design if you had a year to work on it? Key design considerations Make sure to consider the balance of effort students make at the different stages of the design process. Too often the majority of time is spent in the early stages of research and conceptualization leaving little time at the end for the prototype and presentation. If you think of the ~10 minutes that you have at the Faculty Summit Design Expo Presentation session as the final deliverable, consider each task of the process on how it will contribute to that final result in lieu of the time spent. This is analogous to film students only focusing on elements that will end up in the final edit of the film and spending less time on things that don’t. Another aspect of the presentation is to show not just the final result but to communicate the arc of the problem definition, research, design considerations, prototyping and thinking behind how the final solution and presentation was created. Great design is an iterative process and that process should be reflected in the presentation as well. Designs should include user interface interactions as part of the user experience demonstration. Make sure not to gloss over the actual user interface design. In addition to screen and interaction design, we are interested in illustrating how the interactive language may be extended to seamlessly integrate physical design pieces. Solutions should be thought through from multiple perspectives to understand the user’s experience, instructor (if applicable), family and friends, learning community, etc. Microsoft Research Design Expo 2013 6 Designs should address particular needs & desires of users, ideally coming from diverse economic, professional and cultural backgrounds. It is important to not design for yourself and to remember that ‘others’ do not have your background. The final project should not include only users who share your own perspective, terminology or experience. Choose users and scenarios that extend beyond what is comfortable to you and consider scenarios outside your economic, geographic, cultural and social circles. Learn from observing and studying actual users. Remember that student teams are coming from different countries. We encourage you to represent local culture, making sure to explain the context of your learning system in your design presentation. Take a point of view and be clear what your user scenario is addressing & what not. It is important to describe a real user scenario and then try out such premises with the user you are designing for. A walk through scenario often shows why the prototype is a good idea and helps those unfamiliar more quickly gain an appreciation of the need or use. Take a stance with your design, commit yourself to a challenge, but also be clear about what you are and what you are not trying to solve. Consider how to leverage existing infrastructures in new ways to provide innovative solutions at less cost to the individual. Validate your designs with actual user feedback. Involving real users iteratively within the design cycle helps shape product design. This should be done at the very beginning of concept development and evolve into more precise user feedback when the prototype is more ‘finished’. Involve a variety of potential users early and often throughout the design cycle. Demofest Student representatives will also be showcasing their work at the Expo Demofest alongside other university research projects as well as Microsoft Researchers and product groups demonstrating emerging technologies. Teams prepare posters and other communication materials to explain their work at Demofest. Students in the past have commented that the presentations and Demofest have been particularly rewarding parts of their experience at the Expo and learn from the questions and refining their presentation skills to communicate their project process and design solution. Previous Design Expo projects can be viewed here: http://research.microsoft.com/en-us/events/fs2012/designexpo.aspx The Design Expo is a Microsoft Research forum where the top graduate design institutions showcase their prototype interaction design ideas. Microsoft Research sponsors a semester-long class at leading interdisciplinary design schools and invites the top class projects to present their ideas as part of the Faculty Summit. It is essential that this guideline document should be shared with the students in the class, which will help to answer their questions about the project and presentation at the Expo. Design Expo School Liaisons Please contact your school liaison from Microsoft, and either Lili or Michael with any questions or comments about these guidelines, etc. This year we are again fortunate to have Mike Kasprow, from Trapeze helping us with design critiques and process coordination. Mike has many years as a creative and design director and will be working closely with Lili. In emails, please cc both email@example.com & firstname.lastname@example.org . Each of the universities will have a Microsoft liaison and possibly a backup, who will be the primary contact person(s) for each school. We are trying to get this guide out as early as we can to provide early Microsoft Research Design Expo 2013 7 guidance to schools starting early but we fully expect this guide to be revised as the schedule, events and other details get locked down. This document is meant to serve as a set of general guidelines for Design Expo 2013, as opposed to being strict rules for compliance or a legal agreement. We expect these guidelines will be adapted as needed over the course of the semester, by each school to accomplish their own class goals while maintaining some connection to the theme. Microsoft Research Goals for the Design Expo Provide a forum for students from around the world to learn from exploring a particular design related theme and build ongoing relationships between schools. Enable a group of students to learn from students in other design programs around the world about how they approach design solutions Provide a voice for design schools within the Faculty Summit to present their students’ work and raise the awareness and importance of design Raise student, faculty and design schools awareness of the value of interaction design in the software development process. Raise the awareness within Microsoft of the capabilities of design schools and their students. Create memorable and fun experiences for students that foster the creation of informative connections among design students from the participating schools. Summary Students work on the theme in small teams (2-4) during the spring 2013 semester. Given specific guidelines (described later in this document), students will research a design problem which is related to the theme this year, define a scenario, ideate design solutions, select one idea to prototype, and study the impact on real users. The best team project, as identified by the professors with some feedback from liaisons, will be invited to attend the Faculty Summit at Microsoft which is the venue for Design Expo. The Design Expo is part of a larger event called the Faculty Summit. For more info on the Microsoft Re- search Faculty Summit, click here: http://research.microsoft.com/en-us/events/fs2012/default.aspx Microsoft Research Design Expo 2013 8 Design Expo 2012 Participation Process 1. Notification of Participation Microsoft needs to be notified in writing (email is fine) of your willingness to participate by December 1, 2011 to email@example.com and cc’ing your Microsoft liaison. 2. Participation Grant Microsoft will donate $10,000 per university. This is an unconditional grant and there are no restrictions placed on the use of these funds. 3. Design Expo travel costs Airfare For schools not located in the Seattle Area, Microsoft PROVIDES A TRAVEL STIPEND to schools which is intended to supplement the cost of airfare for one faculty member and two students to attend the Faculty Summit. Some schools have chosen to utilize some or all of the grant money to cover the cost of bringing all the students in the selected team and that is their choice. Travel arrangements are made by the schools from the funds allotted. Each school is responsible for making their own transportation arrangements for faculty and students who are attending and no additional funds beyond the stipend will be provided for travel. Domestic (US) Travel Stipend- $1,500.00 (USD) Non-US Travel Stipend- $3,000.00 (USD) Hotel Microsoft will cover the cost of hotel accommodations for one faculty member and two hotel rooms or based on double occupancy, two-four students. Students of the same gender will be expected share a room with two Queen beds. Faculty will be given a room to themselves with a king bed. Microsoft will provide up to 3 rooms per school for 4 nights (dates subject to change TBD Saturday July 13 by 1pm departing Wednesday July 17, 2013). International schools may need to arrive a day earlier given availability of flights and should let us know to see if we can arrange for you to check into the hotel a day earlier. In that situation, students and faculty will be responsible for the additional nights at the hotel. Each school is responsible for providing us with the details of the faculty and student arrival and departure dates/time. If your school brings more than one faculty member and more than four students and/or decides to stay longer than the four nights covered by Microsoft, if you contact us early enough, we may be able to help get additional rooms and/or nights at the discounted rate for the Expo. (Silver Cloud Hotel, Bellevue Washington http://silvercloud.com/bellevue.htm) We book a block of rooms and need to release the rooms that will not be used by July 1, 2013. If you do not plan ahead and let us know, the rooms may not be available. July is one of the busiest months in Seattle so open hotel rooms will be difficult to find or very expensive to find on short notice. Faculty Member- One Single King Room/4 nights Students- Two Double Queen Rooms/4 nights Other transportation costs Microsoft will provide you with a voucher for a specific Taxi company for your transportation to/from the Seattle Tacoma airport to the Silver Cloud Hotel. Other transportation costs at you city of origin or travel while in Seattle area, are the responsibility of the individuals. Microsoft Research Design Expo 2013 9 Food Microsoft will provide meals for the majority of the duration of the Design Expo. The hotel has a complimentary breakfast and box lunches and dinners will be provided at the Faculty Summit or other events. Liaison visits A liaison from Microsoft will visit each university at a mutually agreed to date early in the process in order to provide the best opportunity to collaborate with the faculty and students to kick off the project. Monthly follow up video conferences by the Microsoft Liaison to track progress will help keep the project on track. The second visit by the Liaison(s) will occur near the end of the term when they sit down with the faculty to decide which project will be selected to represent the school at the Design Expo. Project Assessment Each university should try to have at least 2 to 5 team projects running within the class. Each of the project teams will be independently evaluated before one is chosen to show at the final July Design Expo. Each project should include students with different backgrounds in their design team, computer science, product design, marketing, psychology etc. Faculty members should not be part of the team. Each project assessment will be made internally by the university using peer and instructor feedback. The university and Microsoft liaison should select one project that they think best illustrates the project brief concepts/goals and best represents them at Microsoft. The MS liaisons can also be used to help make the final project selection. Selection should be based on the following criteria and the ability to complete the final documentation. Assessment Criteria Interdisciplinary collaboration the prototype designs reflect the contributions of members of different disciplines Originality the prototype designs show unique and new interface designs along with new applications Practicality the prototypes are based on what is most realistically likely to happen with technology in the context proposed Design point of view the design takes a clear stance and addresses a real user need Design validation & user feedback the prototype and presentation show how user involvement evolved the design concepts. (Working with real users and incorporating their feedback) Degree of finish the prototypes should be understandable and clearly described, but need not be ‘implemented’ or built to a final detail level. It is important you actually design the user inter-face and we will look at the UI for degree of finish. Presentation skills the project team is capable of being able to present in an engaging and crisp manner about the project goals; ideas and process of design (see later tips). Microsoft Research Design Expo 2013 10 Design process the prototype shows how user involvement was used directly to evolve the design concepts. This means showing how you used real users and incorporated their feedback Submission Requirements We are assuming that all class projects and their associated work in progress are posted to a university area related to the school web site. Please send the URL details to Lili & Michael and your school liaison by end of January. This Web site will be used for review purposes by both the MS liaisons and the project coordinators. It is important to send email to the project coordinators when significant additional or new in-formation has been uploaded for review. When the class is ready for their mid-term review, please send an email to both project coordinators/liaisons. Every school will receive feedback and recommendations on all their projects both at the mid-point of the class and around the final or end of the course. We expect to give this feedback to each school within a week of receiving an update request from the schools. After the professor, liaison and project coordinators have selected one project by June 2013 to represent the school at the Microsoft Design Expo, we need to review the selected project’s final presentation be-fore your visit. Submission checklist for the selected project Project summary and contact information: Each project should have a completed project information form – including the student’s names, majors, and the professor names, your URL and your final presentation and project on a flash drive (or uploaded to the design expo site), along with any system requirements that are needed to run the design prototype. One paragraph abstract for announcements of project work: A written summary that describes the project briefly and that we can use for announcements the work Interactive presentation (for Design Expo presentation): The project presentation should take about 10 minutes and include a high-level overview slide. The electronic form of this presentation should be clear to a non-team person and should be self-explanatory. All software fonts, applications etc. need to be included with the submission. This will be used as the basis of what will be used for the dry runs in Redmond, Washington at Microsoft. User research (as part of your Design Expo presentation): Short highlights of any user study interviews could be included (if some unique insightful moment occurs) within the presentation to demonstrate how users influenced the project design direction. If you interview people for the user studies make sure to get their written permission in order to use their comments. One page project summary handout to distribute during the presentation: A one pager should include the school with your names, and you should summarize the goals and solutions of the project. It is worth sending a draft of this with your slides for some additional feedback. This hand out should explain in concise compelling sentences what, how and why you designed what you designed. A few small pictures are helpful, so readers with no more than this one pager can understand the general product ideas and the overall project goals. When you come to Microsoft, in addition to the items above, please also bring with you the following: Supporting materials for demo booth and presentation: Additional print outs of sketches; photos or models can be provided. One day of the design expo will include showing your project in a demo booth with the students from the other school. Please bring any signage or demo materials with you. Microsoft Research Design Expo 2013 11 Please bring editable (source) materials with you to Microsoft. Most people tend to revise their presentations after getting feedback, and it is easier to edit if you bring original images, etc. Large images and project name of ALL the projects not selected. Unfortunately we can’t bring more than one project per school out to Microsoft. We would like to show large images & titles of projects not selected during the presentation to the audience. Please keep this in mind and make the images available on the web for all projects. It is critical that this material be submitted to us by early June so we can ensure that information about all projects and students working on those projects NOT selected are included in an introductory presentation at the Design Expo. Publicity Microsoft will try and provide some avenues for the students to talk to the press about their work and meet Microsoft researchers, designers, and design recruiters. The Design Expo will be held in coordination with the Microsoft Faculty Summit. Approximately 300 faculty from the US, India, and Latin America will be on campus to meet one another and find out more about Microsoft Research. We will also invite these attendees, along with the Microsoft design community to attend the Design Expo. The Design Expo is one event and part of the Faculty Summit. Ownership and Commercialization The work and curriculum of the course should follow ownership and commercialization policy of each individual university. Microsoft does not own any of this work, nor requires any first right of refusal. We would like to post the recorded presentations on the Microsoft Research website for Design Expo and we will ask speakers to sign a speaker presentation form. We will also ask you to release content in the talk (including any third party content such as images of other projects) to the public domain, so others can use content for free without further restrictions on use or redistribution. Schedule and Important Dates (subject to change) Nov 30, 2012 Design Expo 2013 Project Brief will be distributed Dec 15, 2012 Notification of acceptance must be sent to firstname.lastname@example.org and your liaison. Jan 11, 2013 Schedule visits for liaison at mutually agreeable date Jan 31, 2013 Send URL of class project sites to Lili Michael and your MS liaison. March 2013 Liaisons will coordinate with schools on initial project progress. April 2013 Mid-term progress reviews given via email feedback May 3, 2013 Final project submissions of all students class projects. Final project feedback given via email on all projects. Note: Any visa requests must be made ASAP, as required. Do not wait to do this! May 17, 2013 Presentation with ONE page visual of EACH PROJECT along with a second page describing in 1 or 2 paragraphs a summary each project. Microsoft Research Design Expo 2013 12 May 17, 2013 Notify MSR and project liaisons of the one project selected from each university to represent the school to present at the Faculty Summit. Send professor and student attendee names with their email contact details to Lili & Michael. May 24, 2013 Draft of chosen project student presentations (10-min) and description of all projects with team member names are sent to Lili & Michael and your liaison June 3-7, 2013 Feedback on final MSR school presentation from Lili & Michael. MSR Design Expo Schedule in Redmond WA (subject to change) Saturday July 13: Arrival & Design Expo Kick-off Activity/Dinner in Seattle 6:00pm-9:30pm Sunday July 14: Dry Run Presentations 9am-5pm Dry Run presentations with feedback from Lili & Michael, 45 minutes for each school, followed by 30 minute tech walkthrough Students and faculty arrive in time to do a dry run of the presentation. Each school will walk through their presentation in the Conference Center & get feedback on their presentation from project coordinators, faculty and their liaison. The schedule is fairly tight, so come prepared with your laptop and presentation. Monday July 1: Work day with your team & liaison to incorporate feedback Evening Faculty Summit Cruise Note: this is Faculty Summit Day 1 (Optional 9-5) Tuesday July 16: Demo Fest and Design Expo formal presentations. 9:00am-4:00pm Afternoon debriefing and awards. 4:00pm-6:00pm Closing party 7:00-10:00 Note: this is Faculty Summit Day 2 (Required 9-5). The Design Expo has traditionally been on Tuesday, Day 2 of the Faculty Summit. We are still finalizing the schedule. Wednesday July 17: Social event in Seattle (TBD), and Faculty/Students departure ilable on the web for all projects. It is critical that this material be submitted to us by early June so we can ensure that information about all projects and students working on those projects NOT selected are included in an introductory presentation at the Design Expo. Publicity Microsoft will try and provide some avenues for the students to talk to the press about their work and meet Microsoft researchers, designers, and design recruiters. The Design Expo will be held in coordination with the Microsoft Faculty Summit. Approximately 300 faculty from the US, India, and Latin America will be on campus to meet one another and find out more about Microsoft Research. We will also invite these attendees, along with the Microsoft design community to attend the Design Expo. The Design Expo is one event and part of the Faculty Summit. Ownership and Commercialization The work and curriculum of the course should follow ownership and commercialization policy of each individual university. Microsoft does not own any of this work, nor requires any first right of refusal. We would like to post the recorded presentations on the Microsoft Research website for Design Expo and we will ask speakers to sign a speaker presentation form. We will also ask you to release content in the talk (including any third party content such as images of other projects) to the public domain, so others can use content for free without further restrictions on use or redistr