INST 776 / Final Report /

Final Project Report INST 776 - HCIM Capstone

The final project report and artifact make up 40% of the total grade. The artifact (in most cases code) needs to be submitted with the final version of the report, but not with earlier drafts. Reports may differ slightly in format based on the exact project, so follow the outline that I approved based on your midterm progress report. Regardless of the exact format you use, all applicable points described below need to be addressed somehow.


Submit a PDF of your draft report to me by email by 9am on Monday, April 8th. Make sure your writing is easy to read: ensure it is clear and concise, use section headings, make liberal use of whitespace, and proofread. Other formatting requirements:

General Structure

Introduction (and/or Motivation)

This section should give a clear description of what your project is about. What problem are you addressing? Make sure you explicitly state it. Why is it interesting and worth working on? How are you contributing to knowledge by doing it? Include a brief overview of your solution. Overall, the introduction should provide context for the rest of the report.

Note, if you wish you may continue to follow the format of the proposal, where the Research Problem / Objective is in its own separate section.

Related Work

This section should cover all the relevant existing literature. Use this to establish the importance of your problem and to illustrate the open space where you are working. Follow the guidance provided during our literature review session at the beginning of the semester. Synthesize, identify gaps in the literature, demonstrate the basis for your own contribution. Consider academic sources and, if appropriate, competing commercial products.

Design Approach

Projects where the design is a primary contribution need to have an explicit description of the design approach used.


Describe the prototype. Make appropriate use of screenshots and other illustrations to communicate your interface.



The discussion is an opportunity to reflect on the project and findings more broadly. Interpret the findings; for example, if Interface A is faster than Interface B, why is that interesting? What does it matter? Who will care? How should we design interfaces differently in the future because of this result? Is there anything that was surprising? If so, why do you think that is? Is there anything that didn't go well in the study? While the findings have to be a straightforward reporting of the data, the discussion section allows for interpretation and, in some cases, proposals of new theories that may help explain your findings--obviously these are theories that would need to be tested in future work.


Every project has limitations. What choices did you have to make for practical reasons but that introduced limitations? What are the implications of those choices? Any other limitations of the work?

Future Work

Insightful ideas for future work based on your in-depth understanding of the problem area. What do you think are the most important areas for future work? What are the next few steps people should work on in this space?


Final words, takeaway message for the reader.


Appendices (if appropriate)

Include study instruments such as questionnaires or interview questions, extra screenshots that you think are important but don't fit well in the main body of the report, and any other supplementary material you think would be useful to help a reader fully understand your project.