← Back to deliverables selector

Usability Report

evaluationcommunicationmediumIntermediate

TL;DR

Documents problems, severity, and recommendations after usability testing.

What is it

The Usability Report is the document that synthesizes findings from usability tests, heuristic evaluations, or UX audits. It presents the problems found, their severity, evidence (video clips, quotes, metrics), and prioritized improvement recommendations.

What it is for

  • ✓Document usability problems with concrete evidence
  • ✓Prioritize improvements by severity and user impact
  • ✓Communicate technical findings to non-technical stakeholders
  • ✓Create a historical record of problems and solutions

Research methods that feed it

Moderated usability testsUnmoderated usability testsHeuristic evaluationUX auditAnalytics analysis (error rates, abandonment)

When to use it

  • ✓After each round of usability testing
  • ✓Upon completing a heuristic evaluation or audit
  • ✓When you need to justify design changes to stakeholders
  • ✓To document UX state before a redesign

When NOT to use it

  • ✗If you only need to share quick findings internally (use an executive summary)
  • ✗When you don't have enough data to support recommendations
  • ✗If the team already saw sessions and agreed on changes (a formal report may be redundant)

How to create it step by step

  1. 1Organize findings: Group problems by category (navigation, content, forms, etc.) or by flow.
  2. 2Classify severity: Use a 1-4 scale (cosmetic, minor, major, critical) based on frequency × impact.
  3. 3Add evidence: For each finding, include: problem description, user quote or video clip, screen where it occurs, number of affected participants.
  4. 4Write recommendations: For each problem, provide an actionable and specific recommendation (not generic).
  5. 5Prioritize actions: Order recommendations by impact × implementation effort.
  6. 6Include executive summary: On the first page, summarize the 3-5 most critical findings for stakeholders who won't read the full report.

Tips for small teams

  • Use a report template you can reuse across projects
  • Include short video clips — they're more persuasive than text
  • The 1-page executive summary is the most important part
  • Classify everything with severity so the team can prioritize without your help

Common mistakes

  • ✗Reporting problems without concrete evidence
  • ✗Not including actionable recommendations (only listing problems)
  • ✗Making reports so long that nobody reads them
  • ✗Not prioritizing by severity (everything seems equally important)
  • ✗Mixing personal opinions with data-based findings

Contextualized example

Context: Supermarket e-commerce — usability test of checkout with 8 participants.

Critical finding (4/4): 6 of 8 users couldn't find the discount code field, located below the purchase summary. Quote: 'I looked everywhere, I thought they didn't have online discounts'. Recommendation: Move the discount field above the purchase summary with an expandable link 'I have a discount code'.

Minor finding (2/4): 3 users were unsure about the meaning of 'Standard shipping'. Recommendation: Add estimated days next to each shipping option.

Phase

evaluationcommunication

Audience

product-teamstakeholdersdevelopment

Complexity

medium

Experience level

Intermediate

Related deliverables

Findings MatrixInsights Presentation

Related methodologies

Usability Testing

Free tool by UXR — UX Research Consulting in Chile