← Back to deliverables selector

Findings Matrix

evaluationmediumIntermediate

TL;DR

Organizes all findings by severity, frequency, and impact to prioritize actions.

What is it

The Findings Matrix is a prioritization tool that organizes all problems identified in research into a tabular structure with severity classification, occurrence frequency, and solution effort. It enables the team to make informed decisions about what to fix first.

What it is for

  • ✓Prioritize problems objectively based on data
  • ✓Facilitate decision-making on what to fix first
  • ✓Create a research-based improvement backlog
  • ✓Communicate to the development team the priority order

Research methods that feed it

Usability testsHeuristic evaluationAnalytics analysisSatisfaction surveys

When to use it

  • ✓When you have multiple findings and need to prioritize
  • ✓When delivering UX audit results
  • ✓To create a research-based improvement roadmap
  • ✓When the development team needs a prioritized backlog

When NOT to use it

  • ✗If you have fewer than 5 findings (no need for a formal matrix)
  • ✗When all findings are at the same severity level
  • ✗If the team prefers a narrative format

How to create it step by step

  1. 1List all findings: Gather all problems identified in research with their evidence.
  2. 2Define classification criteria: Severity (1-4), Frequency (how many users affected), Business impact (high/medium/low).
  3. 3Score each finding: Assign values in each criterion based on research data.
  4. 4Calculate priority: Multiply severity × frequency to get a priority score.
  5. 5Add estimated effort: Work with development to estimate solution effort for each item.
  6. 6Order and present: Sort the matrix by descending priority. Quick wins (high priority, low effort) go first.

Tips for small teams

  • Use a simple spreadsheet — no complex tools needed
  • Involve development when estimating effort for realistic estimates
  • Visually highlight 'quick wins' to facilitate decisions
  • Update the matrix after each round of tests

Common mistakes

  • ✗Classifying everything as 'critical' (if everything is urgent, nothing is)
  • ✗Not including evidence supporting the classification
  • ✗Ignoring implementation effort when prioritizing
  • ✗Not updating the matrix when problems are resolved

Contextualized example

Context: Banking app with 15 findings from a UX audit.

Quick win #1: Transfer button poorly visible (Severity: 3, Frequency: 7/8, Effort: Low) → Change button color and position.

Major improvement: Confusing onboarding flow (Severity: 4, Frequency: 5/8, Effort: High) → Redesign the complete flow with progressive validation.

Phase

evaluation

Audience

product-teamdevelopment

Complexity

medium

Experience level

Intermediate

Related deliverables

Usability Report

Related methodologies

Usability Testing

Free tool by UXR — UX Research Consulting in Chile