Reporting
How to Write Better UX Findings
A good finding connects an observable interface problem to a user consequence and a realistic recommendation.
Use a consistent structure
- Where: identify the screen, section, or step
- Issue: describe the observable problem
- Impact: explain the likely user consequence
- Recommendation: provide a specific improvement
- Priority: indicate urgency using a consistent scale
Describe the problem, not your preference
Avoid presenting personal taste as evidence. Instead of saying a design feels dated, explain how weak hierarchy, unclear labels, or insufficient feedback makes a task harder.
Make recommendations implementable
Recommendations should be precise enough to act on while leaving room for design exploration. Name the element, desired change, and intended outcome.
Weak: “Make onboarding clearer.” Better: “Replace the empty dashboard with a three-step setup checklist that starts with creating the first project.”
Keep one main issue per finding
Combining several unrelated problems makes prioritization and implementation difficult. Split findings when they have different causes, impacts, or owners.
Put the process into practice.
AuditFlow keeps evidence, findings, recommendations, priorities, and reports connected in one workspace.
Start free