Message from Verena and Tom, Co-Chairs Tutorials provide conference participants with the opportunity to gain new insights, knowledge, and skills in a broad range of areas in the field of HCI. Tutorial topics range from practical guidelines and standards to research issues and theory. Tutorial participants include user interface designers and users, software developers, managers of human-computer interface projects, human factors practitioners, interface evaluators and testers, industrial designers, teachers of HCI, researchers in human-computer interaction, and professionals in other areas seeking to gain an understanding of how HCI relates to their specialties.
Each tutorial is designed to be a half-day or full-day in duration. Half-day tutorials are three hours long (not including breaks). Full-day tutorials are six hours long (not including breaks). Also of interest will be coordinated proposals for half day tutorials which can be taken either independently or as a sequence of half day tutorials, depending upon attendee needs. For example, a half day on the theoretical base for and design examples of some special purpose system (for example, Geographical Information Systems, Problem Solving Environments, Networked Design Environments, and so on), coordinated with a half day on the business case for, lessons learned from, and/or the management of such systems. Proposers of coordinated tutorials should clearly indicate this in their submission materials.
The assumed background of attendees should be described explicitly and in detail in the proposal. Include any prerequisites such as knowledge of HCI content, processes, and procedures. State any skills that are needed to understand tutorial content or to complete the exercises. If possible describe or identify those for whom the tutorial would not be needed or appropriate. Also, specify whether the tutorial is intended to introduce participants to an area, or to further develop the expertise of knowledgeable participants.
Tutorials cover a wide range of HCI-related topics. Possible topics include but are not limited to:
Introductory or core topics in HCI.
Requirements capture and analysis techniques.
User interface development software.
Theories, practices, and/or methodologies for design, cognitive engineering, usability engineering, and so on.
Information visualization, retrieval, personalization and filtering.
Multimodal, multi-sensory and multichannel interfaces.
Design for non-traditional desktop systems, for example, games.
Web design and applications emphasizing features unique to the web.
User Interfaces for home, for mobility, or for special user groups (for example, assistive technology, rehabilitation, and so on).
HCI in corporate settings.
New contributing disciplines, advancing multi-disciplinary work in HCI, and so on.
Submissions on emerging new topics are encouraged, as are submission for "master" class audiences.
Tutorial proposals will be evaluated on the basis of their relevance, suitability, timeliness, importance, audience appeal, attendance limits, presentation methods, and past experiences and qualifications of instructors. They will also be considered for their fit within the overall distribution of topics, approaches, audience experience levels, and specialties of the intended audiences.
CHI2004 will use a new model for compensation of tutorial instructors.
The instructor(s) of a half day tutorial will receive a base honorarium of $1000 if that tutorial is conducted at the conference.
The instructor(s) of a full day tutorial will receive a base honorarium of $1500 if that tutorial is conducted at the conference.
Each tutorial (half or full day), regardless of the number of instructors, is offered one complimentary registration to the Conference.
The instructor(s) of a tutorial conducted at the conference (half or full day) will be paid a per capita bonus for each person registered for their tutorial. (Currently, that bonus is expected to be approximately $10.00 per registrant.)
It is the responsibility of the lead instructor for each tutorial to inform the conference committee at least one month in advance of the conference:
The name of the instructor who will be using the complimentary registration.
How any honorarium and bonus monies are to be allocated among the instructor(s) of the tutorial.
CHI2004 reserves the right to cancel any tutorial which is under-subscribed. At this time it is expected that a tutorial with fewer than seven registrants will be canceled.
In the event of cancellation of a tutorial, no fees will be paid to the instructor(s) but the instructor(s) will still be entitled to the single complimentary registration. In the event of cancellation of a tutorial, registrants for that tutorial will be offered either their choice of another tutorial or a refund of their tutorial registration fees for the canceled tutorial.
Tutorial submissions must include three documents: a proposal, a description for the CHI2004 Advance Program, and a requirements list. Submissions are to be sent to email@example.com in electronic form. Document names should contain the lead proposer's last name as the first word and should be sent as either PDF or Word files. If these formats create serious difficulty or are impossible, contact the co-chairs to see if alternate arrangements are possible. No fax submissions are accepted.
The proposal, no longer than 10 pages, describes the learning objectives, the material covered to justify the tutorial for a CHI audience, and explains how the tutorial will be conducted. The proposal also needs to provide samples of materials that will be included in the tutorial notes. Tutorials will be accepted contingent upon receipt of high-quality tutorial notes. The notes should serve as reference materials for attendees and support the presentation of material during the tutorial.
The description for the CHI2004 Advance Program should be no more than 1500 characters.
The requirements list includes materials needed to run the tutorial. It should include any supplies required for each participant, restrictions or conditions on offering the tutorial such as an attendance limit, nonstandard technology support requests and other information that the review committee should know in considering the proposal.
Submission Format and Requirements
A tutorial proposal submission must include a list of applicable categories and three documents:
A description for the CHI 2004 Advance Program, and
A requirements list.
Proposal Prepare a PDF format or Word document of the proposal, no longer than 10 pages, for review purposes. It must have several distinct sections:
Indicate the duration of your tutorial.
Describe the learning objectives of the tutorial.
Describe in detail the material that will be covered in the course.
Describe the assumed background of attendees.
Justify the tutorial for a CHI audience.
Explain how the tutorial will be conducted.
Give a schedule of events with time allocations.
Describe and provide samples of materials to be included in the tutorial notes in cases of multiple instructors, indicate role and percentage involvement of each instructor.
If the proposed tutorial has been given previously, the proposal should include where the tutorial has been given and how it will be modified for CHI 2004. If the tutorial has been given at a previous CHI conference, describe how changes to the tutorial will address comments from previous attendees. Additional materials may be submitted, but will not necessarily be included in the review process.
In describing the target attendee background, include any prerequisites such as knowledge of HCI content, processes, and procedures. State any skills that are needed to understand tutorial content or to complete the exercises. Also, specify whether the tutorial is intended to introduce participants to an area, or to further develop the expertise of knowledgeable participants.
Description for the CHI 2004 Advance Program Prepare an Advance Program description as a plain text file. This description should be no more than 1500 characters. Longer descriptions will be cut. The Advance Program description should contain the following sections:
Title of the tutorial, up to 60 characters.
Names and affiliations of the instructors.
Benefits: The benefit statement should contain a summary of what skills and knowledge the attendees will gain as a result of attending this tutorial.
Origins: The origins should state the history of this tutorial (for example, whether it was given at past CHI conferences or related venues).
Features: The features should consist of a bulleted list. The items in this list should include the educational goals and/or major elements of the tutorial content.
Audience: The audience should be described in terms that include any background required to understand the tutorial. State the disciplines and/or organizational roles of attendees who would be interested in your tutorial (see first paragraph of call for a list of roles).
Presentation: List the various presentation forms used in the tutorial, for example, lectures, demonstration, exercises, videos, group discussions, and/or case studies.
Instructor background: List the background for each instructor, including current employment and activities, previous professional activities, and relevant publications.
Requirements Document The requirements list includes any materials or conditions needed to run the tutorial. It should include any supplies required for each participant, restrictions or conditions on offering the tutorial such as an attendance limit, non-standard technology support requests and other information that the review committee should know in considering the proposal.
Submitting Your Proposal Prepare the proposal for review in PDF or Word format. Prepare the Advance Program description, as described above, in plain-text format. Prepare a requirements list, as described above. Submit the materials electronically to firstname.lastname@example.org. If you anticipate difficulties with electronic submission, then contact the tutorials chairs as early as possible to see if alternate arrangements are possible.
Instructors will be notified of acceptance or rejection by 1 December, 2003. Offering of the tutorial at the conference will be contingent upon the instructor meeting conference deadlines and requirements.
Before the Conference
Tutorials are accepted upon the assumption that the instructors will provide a set of high-quality notes in a timely fashion so that they can be reproduced for dissemination to attendees. The notes should serve as reference materials for attendees and should support the presentation of the material during the tutorial. CHI2004 reserves the right to cancel the offering of any tutorial where high-quality notes are not provided in a timely fashion.
Instructors of accepted tutorials will receive detailed format requirements for preparation of a publication-ready version of their tutorial notes. Instructors must prepare course material (tutorial and notes) specifically for the CHI2004 tutorial session. Presentation materials used by the instructor for other courses or projects must be reworked within the guidelines described in format requirements.
Tutorial notes should include:
an introduction to the topic
copies of all overhead transparencies and slides
an annotated bibliography
copies of relevant background material or scholarly papers (for which the instructors have obtained any necessary reprint permission)
tutorial exercises, as appropriate
Instructors must sign a release form giving CHI2004 one-time-only permission to utilize the notes for tutorial participants and to sell notes at the conference.
At the Conference
Presenters are encouraged to bring their own laptops for their presentation. CHI2004 will identify local vendors for on-site rental equipment at presenters' expense (details forthcoming) but due to budget constraints will not be able to provide computer support in every session. A digital projector (800x600 or better) will be provided for Macintosh or PC laptop projection.
Tutorial Submission Checklist
Please review the following checklist to help ensure completeness of your tutorial proposal submission.
Prepare the tutorial submission proposal for review in the appropriate format.
Prepare the Advance Program description, as described above, in plain-text format.
Prepare a requirements list, as described above.
Be sure the document names contain the lead proposer’s last name as the first word in the document name.