An HCI development report is more than a collection of findings — it is a document that a reader who was not part of your project should be able to pick up and follow from problem statement to design decisions to evaluation results. That readability comes from structure: a predictable sequence of sections (introduction, methods, findings, discussion, conclusion, references, appendices), each doing a distinct job, with transitions that carry a single argument across them. In this course, your project report is the main artefact that records what you designed, why you designed it that way, and what users told you.
Two supporting skills make that report credible. The first is referencing: when you claim that your layout follows a usability heuristic or that your task-completion metric is a standard measure, you must point to the source, both in the text and in a reference list. The second is presentation — consistent headings, readable typography, properly numbered and captioned figures, screenshots, wireframes, and tables that are referred to in the prose rather than dropped in silently.
The three videos below cover these skills from complementary angles: general report structure, APA formatting of a full document, and the mechanics of in-text citation. While watching, note the function of each section rather than just its name, and pay attention to the small conventions — caption placement, citation punctuation, heading levels — that distinguish a professional report from a rough draft. Also check your assignment brief, since your instructor may specify a referencing style or section list that differs from the examples shown.
A six-minute Scribbr walkthrough of formatting a complete paper in APA 7th edition, covering the title page, running head and page numbers, abstract, body text, headings, and the reference list. It demonstrates the formatting choices concretely rather than just describing them.
It maps onto the Presentation and Formatting Standards subtopic by showing a full document being formatted consistently end to end, which is exactly the level of polish expected in a submitted HCI report.
A focused Scribbr explainer on APA in-text citations: what information an in-text citation must contain, where it goes within a sentence, and how to handle awkward cases such as missing authors or dates. It also illustrates the relationship between the in-text citation and the full reference entry.
Accurate in-text citation is the core mechanic of the Academic Referencing subtopic, and Scribbr is a widely used, reliable source for current APA 7th edition rules.
A short tutorial from a university study-skills team walking through the key sections of an academic or technical report and what each one is for. Based on its title and description, it covers the standard structure students are expected to follow — elements such as the title page, introduction, main body, conclusions and recommendations, references, and appendices — and how the sections fit together.
It directly addresses the Standard Report Structure and cohesive-narrative subtopics, and comes from a university learning service, so the conventions it presents are the ones assessors typically expect.
Together these videos give you the writing conventions needed to turn project work into a submittable document. The report-structure tutorial supports MO1 and MO2 by showing where requirements, design decisions, evaluation findings, and iteration history belong within a conventional section sequence. The APA formatting video reinforces MO2 by modelling consistent, professional presentation across a whole document, including headings and reference lists. The in-text citation video supports MO3, since justifying design choices against HCI principles and published guidance requires you to cite those sources correctly in the body of your argument rather than asserting them.
These videos were chosen from YouTube on October 3, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.