CHI 2005 April 2 through 7 Portland, OregonCHI 2005 Home

Conference Overview
Conference Committee
Exhibiting & Recruiting
About Portland

Our Sponsors

Conference Program

Conference Program

Presenting at CHI



Student Volunteers

Call For Participation

Submissions Overview
Archived CFPs
All submissions closed



Design Expo


Important Dates

Jonathan ArnowitzJonathan Arnowitz
SAP Labs

Mentor Request Deadline:
13 September 2004
Submission Deadline:
13 December 2004 [5:00 PM (1700) PST]
Notice of Acceptance:
31 January 2005
Additional Information

Boyd de GrootBoyd de Groot
Satama Interactive
The Netherlands / Finland

Aaron MarcusAaron Marcus
Aaron Marcus and Associates
Contact Us
Message from Boyd and Aaron, Co-Chairs
The Design Expo is a returning category for CHI 2005, which provides a forum to present design case studies to the entire CHI community with an explicit focus on the methodologies and final results of the design disciplines. An essential part of the Design Expo will be demonstrations of design case studies (based largely upon the DUX2003 submission format). Presentations will showcase designs and describe work from real design projects. The co-chairs particularly invite designers to submit case studies about converging technologies, industries, and design disciplines. Examples include user-interface/experience development for consumer products/services in mobile devices, vehicle systems, and appliances.

About the Design Expo

This will be the fifth installment/iteration of the Design Expo at CHI. This new edition will continue to formalize the design case study as a part of CHI, and establish a designer/practitioner&endash;friendly form of paper submissions. The Design Expo welcomes case studies from any domain of human-computer interaction and communication, including:
  • Web applications/Web sites
  • Software applications for all platforms
  • Mobile device user interfaces
  • Specialized applications (for example, installations, kiosks, CD-ROMs, etc.)
  • Games
  • Tangible user interfaces
  • Embedded computing user interfaces
  • Interactive data visualization
  • Pervasive/ubiquitous computing environments
  • Virtual reality
  • Multi-channel applications
  • Interactive television
  • Wearable computers

Submissions should illustrate best practices and analysis in the design process of successful products/services. Submissions should also detail designs and/or implementations of solutions to design problems in the user experience involving interactive systems (the user experience includes visual design interaction-, information-, and business-oriented design issues, including branding). Accepted applicants will demonstrate their designs to an audience at CHI 2005 and will publish their work online in the ACM Digital Library and potentially the AIGA Experience Design Case Study Archive (pending joint-society agreement). Exchanges of ideas among presenters and the audience will be an important part of the presentation/demonstration event.


Design Case Studies report on implemented designs and the methods and techniques people have used, specifying what worked, what did not work, and why. Case studies offer comprehensive and richly illustrated narratives of the challenges of development, the processes used, and the results achieved (good or bad), including the impact on all stakeholders, such as the user community, the sponsoring organization, and technology providers. Case Studies provide evidence of the quality of the user’s experience and the degree to which the design achieved the organization's goals. The design cases are 12-16 pages in length; the extra-long length allows for extensive illustration of the design. To assist in illustrating the design, an additional appendix of up to 6 pages may be included with the paper to explain/describe the design, process, and/or method. Keep in mind that this event is not a design competition; the focus of the case studies is on sharing your design experiences with the community and reflecting on achieving objectives and lessons learned: What repeatable methods or techniques did you use to get your successful design results? Accepted submissions will be chosen on the merit and contribution of the Case Study, not only on the quality of design that it describes. This means that a valuable lesson learned from a poor design is just as acceptable as a valuable lesson learned from a good design.

Design Case Studies can cover the following aspects of a project: the actual practice-project execution, methods used, or research conducted for the project, as long as the criteria outlined below are followed. Design Case Studies that do not cover the submission guidelines will not be accepted.

Special note to students and teachers: we are in the on-going process of formalizing the case study as a curriculum component. Therefore we strongly encourage teachers interested in getting their students to submit to the Design Expo (assuming the project fulfills the above requirements) to contact the Design Expo Co-Chairs to ask for a mentor or coach in the submission format.

How to Submit

What to Address in Your Submission

The following list should form the outline of your submission. The idea is to make cross submission comparisons easy, as well as to facilitate the concentration on your design, design methods, and techniques, instead of the structure of the case-study submission.

  1. Problem Statement
    Including industry, problem, objectives, and goals (business, market, users, technology), etc.
  2. Background
    a) Team members and their roles
    b) Project dates and duration
    c) History and context
  3. Challenge
    In real-world design pursuits, there are often constraints that make it difficult or impossible to follow ideal-path processes. Was there something in this project, e.g., a budgetary or time limitation, a technological constraint, a political challenge, a midstream change in priorities, etc., that would affect how the project was executed?
  4. Solution
    a) Process (methods, tools, procedures, influences), most notably:
    • What did you choose to do and why was this the most effective solution? In retrospect, were these choices effective?
    • What other best practices were considered but not used? Why were they not pursued?
    b) Solution details:
    • How did the design solution support project requirements?
    • How were end-constituents involved in the process?
    • What were the elements of the design strategy?
    • What is unique or convention-setting about the user experience(s)?
    • What were the constraints of the solution?
    • How was business and culture affected as a result?
    • What was the feedback -- the user response?
    • What was the impact on you and/or the end users?
    c) Results (measured against goals)
    • How did you measure success?
    • What was the impact on you and/or the end users?
    • What insights were gained?
    • What is repeatable, and what would you do differently?
    • What are the next steps in the work, anticipated growth and development of the study's concepts?
  5. Illustrations of the solution(s) (e.g., screenshots and other illustrative images of design solutions) embedded in the above sections as appropriate.

  • Your submission must be in English.
    If English is not your first language, we encourage you to have a fluent English speaker check your work, or to make use of our mentor program.
  • Your submission should contain no proprietary or confidential material and should cite no proprietary or confidential publications; responsibility for permission to use video, audio or pictures of identifiable people or systems rests with you, not CHI 2005.

Review Criteria

All submissions meeting the conference requirements will be peer-reviewed by a jury of user-interface/experience professionals. Your submission may be accepted for publication or presentation as is, or with minor edits. Please follow the submission guidelines and use the submission template to increase the possibility that it will be accepted. All accepted submissions will be listed in the CHI Conference program, be presented as part of the Design Expo, and will be distributed to conference attendees via CD-ROM.

Acceptance Criteria: How will my contribution be reviewed?
Reviewers will judge how well the contribution meets the goals of the conference, whether the content outlined above section is included, etc.:

Clarity of Exposition
  • Is the written submission well structured?
  • Are arguments used in support of assertions?
  • Is previous similar work cited in a way that shows the authors have considered past experience or literature in this area?
  • Are there sufficient illustrations included to describe the work visually and the user's experience?
Claims and Outcomes
  • Is there a clear statement of impact on the user?
  • Are further prospects for use or continued use of the project stated?
  • Are the claims valid and substantiated, with statistical or anecdotal data?
  • Is it clear how other practitioners can make use of the results?
  • Is this work novel or original in a way that adds value to the body of published work in this area
  • Does it add something new and meaningful to what the design community already knows and understands?
  • Applicability to the conference theme
  • Contribution to the field of human-computer interaction and communication
  • Suitability for presentation in this category

Submission Format

Well in advance of the deadline, a submission kit will be uploaded for you to use in writing your submissions. Your design case study is limited to sixteen pages, US letter size or A4, inclusive of all illustrations and citations and additional six pages of supplemental illustrations will be allowed, but please note the supplement can only contain pictures with short captions. Sufficient illustrations are required to convey an actual design to the audience; web links or other supplementary material may complement but not replace in-line illustrations. Please submit supplementary material (e.g., video, audio, interactive demos) as MPEG or QuickTime movies, Flash or Director Projectors, MP3 or AVI. In our experience, some reviewers may have trouble opening some formats or have difficulty downloading large files. Please note this risk, that some reviewers may not be able to access the supplementary materials.

The proceedings are full-color PDFs that will be published in the ACM Digital Library. Please limit your submission to a final archive data size of 10MB.

Packaging Your Submission

  • Cover sheet (single page): Include the name and full contact address (surface, fax, email) of the individual responsible for submitting and receiving inquiries about your submission.
  • Title
  • Author(s) and contact info
  • Abstract of 150 words or less
  • Keywords
  • Content described in How to Submit

You will upload your PDF files to the CHI 2005 submission web site (

Note: These submission formats are part of the ongoing process of developing a body of user experience design case studies that have been embodied in our on-going cooperation with SIGGRAPH and the AIGA's Experience Design Group, as most recently developed for the successful Designing for User Experience Conference (DUX2003) conference. Every effort will be made to get members of SIGGRAPH and the AIGA Experience Design Community included in the review process, as well as to link this track with the proposed DUX2005 conference.

Confidentiality of Submissions

Confidentiality of submissions is maintained during the review process. All rejected submissions will be kept confidential in perpetuity. All submitted materials for accepted submissions will be kept confidential until the start of the conference, 2 April 2005. Submissions should contain no information or materials that are proprietary at publication time.

At the Conference

Authors will present their work in a scheduled session with other papers. Presentations of papers are 15 minutes long (a 10-minute talk with 5 minutes for questions). Only standard technology support (overhead projector and data projector) is provided for Design Expo. If you are using a data projector, you must supply your own laptop computer. CHI 2005 cannot cover added costs for presentations.

CHI 2005April 2 - 7Portland, Oregon, USA SIGCHIBack to Top SIGCHI