INTERACT 2017 Mumbai, the 16th IFIP TC.13 International Conference on Human-Computer Interaction. September 25-29, 2017 in Mumbai, India. © IFIP INTERACT (Document generated on: Sep 21, 2017 04:52AM)

Case Studies

Print Page

Case Studies are an excellent opportunity to showcase the design, development, evaluation and adoption (or not) of an interactive product or a service, whether the product or service was ultimately deemed successful or not. Case Studies should be reflective and concise, and should offer actionable original insights relevant to the practice of interactive product or service design.

The list of accepted Case Studies is now available online

View Accepted Proposals

Quick Info

June 30, 2017
July 20, 2017
July 25, 2017 Extended
Participant Registration
August 20, 2017
Ravi Poovaiah, Elizabeth F. Churchill
No. of pages
2 - 4
Submission Link


A Case Study could illustrate, explore, report, analyze, summarize, challenge, or simply describe. The specific focus of the Case Study may vary. A Case Study submission could highlight the design process, the team’s operational issues, or the specific product or service solution A Case Study could, for example, focus, on the and of the following topics:

  • A significant innovation through research or design (disruptive or otherwise)
  • Design of a specific experience, discussing its rationale, any issues, and lessons learned
  • Domain-specific topics in lesser known domains of interest
  • Pilot studies preceding and informing larger-scale investigation
  • Development, application, critique, or evolution of a method, process, theory, or tool
  • Management and strategy of research and design in a particular organization

Case study submissions will not be constrained by traditional academic expectations, and do not require extensive literature review. Case Studies will be judged by their significant contribution to the field of interactive product or service design.

There are three keys to a successful Case Study. First, the Case Study should be based on real-world experiences. Second, the Case Study should be relevant to the conference focus and themes. Third, the Case Study should be detailed enough to be instructive for other members of the community, offering insights and clear lessons to inform their own practice.

Case study contributors could be interaction designers, information architects, usability experts, software developers, or other professionals from industry. We also welcome case studies from product developers, consultants/consultancies or funding agencies. Case studies could highlight collaborations and partnerships across different groups or between groups cooperating across geographical, political, or cultural boundaries.


Submissions should be a min. of 2 and a max. of 4 pages, and should be formatted in the Springer LNCS Format. Submissions should be uploaded in .PDF format, using the conference submission system (PCS) by June 30, 2017 - 23:59 PT. Accepted case studies will appear in the conference proceedings published by Springer in the LNCS Series.

Notification of acceptance will be on July 20, 2017. Final versions of accepted submissions are due on July 25, 2017 (Extended). Authors of accepted case studies will be expected to make a presentation at the Case Studies sessions at the conference.