HCI 670 internal presentation benchmark: a planning guide
The audience is executive leadership, which changes everything — the deck has to justify the work rather than describe it, and the human factors slide is the one that separates informatics from IT.
Editorial process
Last reviewed · August 10, 2026
What does an executive audience change about this deck?
The audience specification is the assignment's most important line and the one that decides whether the deck works. This is designed for executive leadership, which means the people watching did not build the form, do not remember the gap analysis, and will not read the notes. They need to know what problem existed, what was done, whether it worked, and how you will know. Everything else is supporting detail. A deck built as a chronological account of your coursework — here is what I did in topic 2, then topic 3 — describes the process to an audience that only wants the argument. Assume every slide will be read in about fifteen seconds and that any question will be about cost, risk or evidence.
Structure the ten to fifteen slides against the six required elements rather than against the timeline. The gap or need is the opening and it should be quantified from the case study wherever the case supplies numbers, because an executive audience reads a stated problem as a claim on resources. The electronic form and the future state workflow are the intervention, and the useful framing is what changed rather than what was built: the navigator previously did X in Y steps across two systems, and now does it in one place at the point of care. Screenshots or a workflow diagram carry that far better than prose. A before-and-after pair of workflow diagrams on adjacent slides is the single most effective thing you can put in this deck, because it makes the change visible without anyone reading a word.
The human factors and user interface slide is the one that distinguishes an informatics presentation from an IT status update, and it is where most decks go thin. Human factors engineering is a discipline with specific principles you can name and apply: designing to the task and its interruptions rather than to the data model, minimising memory load, making errors visible and recoverable, keeping the number of steps and screens down, and using consistency so the interface is predictable. Say which principle drove which design decision. "We made it user-friendly" is not an application of anything, whereas "required fields were reduced from eleven to four because the remaining seven were unavailable at the moment of entry" demonstrates the discipline the course is teaching. Implementation belongs on that slide too, since the brief says design and implementation: training, phasing, and what you did to reduce the burden on people whose workflow changed.
The last two elements are separate and are commonly merged. The evaluation measures are what you will count — completion time, error rate, referrals appearing in the receiving queue, user satisfaction, abandonment. The process for evaluating success is how and when you will count it: baseline before go-live, measurement points afterwards, who collects the data, what threshold counts as success, and what happens if the measure moves the wrong way. An executive audience is used to that distinction, and a deck that gives measures without a process invites the obvious question of who is actually going to check. Include at least one measure that could show the solution failing; a set of metrics that can only improve is not an evaluation.
Slide craft matters here more than in a written assignment, because the notes are explicitly required and that tells you what belongs where. Claims and evidence go on the slide, kept to what can be read at a glance; the reasoning, the caveats and the citations go in the presenter's notes. Three to five credible sources are required and they should be attached to the design and evaluation decisions rather than assembled on the reference slide alone. Usability validation methods for health records and implementation reviews are the natural sources — cite them where you justify a choice, and the deck stops being an assertion about your own work. Keep the reference slide to the same three to five sources rather than padding it, since the cap is part of the specification.
One judgement call worth making deliberately: what to do about limitations. Presenting a completed solution to leadership without any risks or open questions reads as sales rather than analysis, and this is a benchmark being marked by someone who knows the case study. Name what you could not test, what the evaluation will not show, and what would have to be true for the solution to hold at scale. One honest slide near the end will do more for the assessment than another slide of features. It is also what executives are trained to look for, so the deck reads as more credible rather than less.
Likely learning objectives
Inferred from the brief — check these against your own rubric.
- 01Adapt a technical account for an audience that did not do the work.
- 02Justify design decisions by naming the human factors principle behind each.
- 03Distinguish an evaluation measure from an evaluation process.
- 04Use presenter's notes as the place where reasoning and citation live.
Read the full question
Review every instruction before using the planning guidance that follows.
The six required elements and the slide rules
- 01A 10–15 slide PowerPoint presentation for executive leadership.
- 02A description of the gap or need identified.
- 03A description of the electronic form created to assist the oncology RN navigator.
- 04A description of the future state workflow created to meet the needs of the EHR.
- 05An explanation of how human factor engineering and user interface principles were integrated into the design and implementation.
- 06The evaluation measures for the informatics solution.
- 07The process for evaluating the success of the solution.
- 08Cover slide, reference slide and presenter's notes, with three to five credible resources.
Gap, solution, design rationale, evaluation
The gap and why it mattered
State the identified need with a figure from the case study and the consequence of leaving it unaddressed.
The form and the future state workflow
Show what the navigator does now versus what they did before, using a diagram rather than prose.
Human factors and interface design
Name the principles applied and the specific design decision each one produced.
Evaluation measures and process
List what will be counted, then set out when, by whom, against what threshold, and what happens on failure.
Where the human factors evidence sits
Recommended databases
- The Integrated Case Study resource
- NIST publications on EHR usability
- PubMed Central and JMIR Human Factors
- ONC HealthIT.gov
Search sequence
- 1.Pull every number the case study gives about the gap before designing a slide; an executive deck without a figure on the problem slide is arguing from assertion.
- 2.Search human factors engineering in health IT for named principles, then match each to a decision you actually made.
- 3.Search EHR implementation evaluation for the measures other organisations used, which is faster than inventing your own and easier to defend.
- 4.Keep three to five sources and no more; the brief caps them, and a deck with a dozen citations is not an executive presentation.
Sources for usability and implementation claims
These are authoritative starting points, not a ready-made bibliography. A qualified reviewer must confirm that each source fits the assignment and supports the claim beside which it is cited.
Nothing here is cleared for citation until you have read it.
- 01
Technical Evaluation, Testing, and Validation of the Usability of Electronic Health Records: Empirically Based Use Cases for Validating Safety-Enhanced Usability and Guidelines for Standardization
National Institute of Standards and Technology · 2012
The standard method for validating EHR usability with safety in view. Cite it on the human factors slide, where it converts a design claim into an application of an established protocol.
- 02
Human factors in healthcare IT: Management considerations and trends
Journal of Hospital Management and Health Policy · 2023
Frames usability and human factors as management concerns rather than technical ones, which is exactly the register an executive audience needs. Useful for the slide that explains why design decisions belong on a leadership agenda.
- 03
Mind the Gap: A systematic review to identify usability and safety challenges and practices during electronic health record implementation
Applied Clinical Informatics · 2016
Six recurring implementation gaps including workflow analysis, customisation and training. Good support for the evaluation process slide and for the limitations you acknowledge near the end.
- 04
SAFER Guides
Office of the National Coordinator for Health Information Technology · 2025
Self-assessment guides for safe health IT use. A source for at least one safety-oriented evaluation measure, which most decks omit and which an executive audience will expect to see.
Before you submit the deck
Common mistakes
- Presenting the coursework chronologically rather than presenting the argument.
- Stating the gap without any figure from the case study to size it.
- Describing what was built rather than what changed for the navigator.
- Claiming the design is user-friendly instead of naming the human factors principle applied.
- Merging evaluation measures with the evaluation process, so nobody is accountable for measuring.
- Putting the full argument on the slides and leaving the presenter's notes empty.
- Attaching the three to five sources only to the reference slide rather than to the decisions they support.
- Presenting a solution with no limitations, which reads as sales rather than analysis.
Submission checklist
- Slide count is 10–15 excluding cover and reference slides.
- The gap is quantified from the case study.
- The form and the workflow are described in terms of what changed.
- At least three human factors or interface principles are named and tied to specific decisions.
- Evaluation measures are listed as countable quantities.
- The evaluation process names timing, owner and success threshold.
- Every slide has presenter's notes carrying the reasoning and citations.
- Three to five credible sources are cited at the decisions they support.
- At least one limitation or open risk is acknowledged.
Use this guide to plan and review your own work. Follow your institution's rules and read our academic-integrity policy.

Written by
Aaron Bishop
MA, Education
assignment interpretation and research-methods coaching across disciplines
Aaron leads the EssayCrackers editorial desk. He works on how assignment briefs are read — what a rubric is actually asking for, and where students most often answer a different question than the one set.

Reviewed by
Dr. Nathan Cole
PhD, Rhetoric & Composition
Argumentation and thesis development
Nathan teaches first-year composition and directs a university writing center. He reviews EssayCrackers guides for argumentative soundness and citation accuracy.