UX Research Reporting Checklist

Use this checklist when documenting and reporting on your UX research so that:

  • observations, findings, recommendations and significance are clearly communicated
  • recommendations are evidence-based, robust, influential and defensible
  • internal staff and vendors understand what they need to do, and when
  • if someone needed to repeat the research, that there is enough information for them to do that
  • you've done everything you need to do to get your research signed off.

Step / Complete
  1. Your report has an executive summary at the beginning. In fewer than two pages your executive summary outlines what the testing was, what the overall performance measures were and whether this is good or bad, and the extent that the research answers key research questions or if there are more steps needed

  1. Your findings are summarised and each finding is prioritised, so that it’s clear at a glance which findings you are recommending are critical and which are minor

  1. Your main introduction describes why the research was needed, what the expected benefits were, what the method used was, if there were factors that could have impacted the findings including the extent that research participants’ represented the key user groups (e.g. age, gender, industry, education, experience, language and cultural background)

  1. List your findings and include for each finding:
  2. What you observed or what happened, what participants did or said (finding)
  3. How it happened, or a supporting quote (evidence)
  4. Why you think it is important and what you think the potential impact might be (insight)
  5. What action is likely to address the finding (recommendation)
  6. Extent that the recommendation is likely to address the finding (impact)

  1. For task-focussed processes summarise overall and individual task completion:
  2. What each task was and what participants needed to do
  3. How well participants completed tasks and their success and failure rates

  1. For usability testing calculate the System Usability Scale (SUS) score:
  2. What the overall SUS score was (unacceptable/marginal/acceptable)
  3. What the implication of the SUS score is

  1. Include references to support materials, and relevant conventions and standards if used

Acronyms and terms / Description
UX / User Experience
WoVG / Whole of Victorian Government
DPC / Department of Premier and Cabinet
DJR / Department of Justice & Regulation
SUS / System Usability Scale
SES / Single Ease Score

TRIM ID: CD/16/413375| Enterprise Digital, Integration and Application Services

Page 1 | February 2017 | WoVG Digital Standards Framework