Experience reports are examples of HCI practice that are based on real world experience, described and generalized in a way to be of interest and instructive to other members of the community. Potential examples include:
Experience reports can be submitted to any of the following communities: Design, Education, Engineering, Management, and Usability. Cross community experience reports are encouraged; select one of the relevant communities to submit to and in your cover letter explain what other communities your proposal relates to. The proposal will be reviewed by members of all relevant communities.
Format of Submissions
The primary submission material consists of a 6 page extended abstract in the Conference Extended Abstracts Publication Format. This information must include the title, names and affiliations of the authors, an abstract of no more than 150 words, keywords for indexing, and classification keywords for inclusion the ACM digital library. Within the page constraints, describe the experience, focusing on the lessons you want readers to take away from the presentation. Your extended abstract must stand alone; readers must be able to understand the experience report with only this material.
You may augment the extended abstract with additional material that supports your thesis. The submission of any supporting material should take into account the demands of the reviewing process and neither be excessive in length nor require close scrutiny. Typical supporting materials will be documents (pictures, etc) or interactive media (e.g., flash prototypes) that have been produced for other purposes, which may help the reviewing committee to understand why this work is of interest to the CHI community. Supporting materials will not be the primary input to the decision-making process, but may be used in identifying suitable reviewers, resolving difficult decisions and for planning the conference program. Examples of suitable supporting materials might include product screenshots, product reviews, design process documentation, a usability report, a low fidelity prototype, etc. Our intent is to make submission of experience reports lightweight by allowing practitioners to leverage material created during the activity, without having to completely rewrite it for publication.
Please provide a manifest, in PDF, of the auxiliary documents in your submission. The manifest should explain the nature and purpose of each of the submitted items; if the report is relevant to multiple communities, include that information in your manifest. Then combine your files into a single zipped document.
CHI 2006 will try to provide mentors for individuals who have not been published at CHI before and would like assistance in preparing their experience report/interactivity submission. Please see Mentoring for more information. The deadline to request a mentor is 14 July 2005.
Experience reports offer narratives of the challenges of an activity, 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. Accepted submissions will be chosen on the merit and contribution of the report, not only on the quality of the outcome that it describes. This means that a valuable lesson learned from a poor outcome is just as acceptable as a valuable lesson learned from a good result.
Submissions will be reviewed independently by reviewers drawn from the relevant community(ies). The review criteria will be the extent to which the experience reported:
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, 22 April 2006. The supporting material will be kept confidential, though it is the expectation of the committee that much of it will be communicated in the presentation. The extended abstract should contain no information or materials that are proprietary at publication time.
At the Conference
Participants will present their report in a scheduled session. Please see Standard Technical Support for information about the kind of technical and A/V support that will be provided by the conference.
Experience Reports Submission Checklist