Usability Findings Report and Recommendations

Description

Report each usability finding with location, user-and-task description, design cause, evidence, severity and a costed, specific recommendation, ranked so teams can act on it.

Comparative studies such as CUE-4 showed that many practitioners write findings developers cannot use. A good finding states the problem in user and task terms, not as a solution; gives its location with annotated screenshots; names the judged design cause, linked to guidelines; provides evidence of what users did and said; rates severity with reasons; and proposes a redesign, ideally bundling related problems into one fix, with cost and trade-offs. Molich and colleagues add that recommendations should be clear, specific, at the conceptual level, respectful of business and technical constraints, and solve the whole class of problem. Ranking by importance and expected effort makes managers more likely to act. Reports should be audience-tailored, jargon-free, organised by affinity for large sets, backed by short video clips and presented in person; informal numbers must not be presented as statistics. Summative reports follow the Common Industry Format.

Attributes

Loss type
Active
Stage
Evaluation
Effort
Days

Steps

  1. Identify the audience (team, stakeholders, management, clients) and adapt content, format and tone.
  2. Write each problem as user, task and effect, with location (annotated screenshot) and evidence of what users did and said.
  3. State the judged design cause with links to guidelines, and give a reasoned severity rating.
  4. Propose specific redesigns at the conceptual level, bundling related problems and noting cost, constraints and trade-offs.
  5. Rank recommendations by importance and expected effort, for example top priority, mid-level changes, small required fixes and next-version items.
  6. Organise large sets by affinity, add short self-contained video clips (with consent), and keep numbers informal and anonymous.
  7. Present in person and argue for prioritisation; use the Common Industry Format for summative tests.

Sources

  • The UX Book (Hartson & Pyla, 2019)
  • Usability Testing: A Practitioner's Guide (Hertzum, 2020)
  • Designing the User Interface (Shneiderman et al., 2018)
  • Handbook of Usability Testing (Rubin & Chisnell, 2008)

Also known as

  • Formative UX evaluation problem reporting
  • UX evaluation report
  • Formative Common Industry Format
  • Problem-cause-severity-solution record
  • Redesign proposals
  • Usability test report
  • Five-element finding description
  • Prioritised usability recommendations
  • Molich recommendation guidelines

Categories

  • User Research
  • Usability & Evaluation