Usability Testing Template (free)

Structure your usability test observations and session notes into prioritised findings so your team knows exactly what to fix and why.

Template components

Task Scenario & Participant Info
Record the task the participant was asked to complete, their role or segment, and any relevant background context before the session begins.
Example: Participant: Maya, 34, mid-market SaaS product manager. Task: "Without any help, find and export last month's usage report as a CSV." Prior tool experience: moderate. Session length: 45 min.
Session Observations & Direct Quotes
Log timestamped behavioural observations and verbatim quotes as the participant moves through the task, noting hesitations, errors, and workarounds.
Example: 02:14 — Clicked "Analytics" first, then backtracked. Said: "I assumed exports would be under Analytics, not Settings." 05:40 — Hovered over three icons without clicking. "I have no idea what these do." 09:22 — Successfully found export but missed CSV option, defaulted to PDF.
Issue Log with Severity Rating
List every distinct usability issue observed, assign a severity level (Critical / High / Medium / Low), and note how many participants encountered it.
Example: Issue: Export function buried in Settings, not Analytics. Severity: Critical. Frequency: 4/5 participants. Issue: Icon tooltips absent on dashboard toolbar. Severity: High. Frequency: 3/5 participants. Issue: CSV not the default export format. Severity: Medium. Frequency: 2/5 participants.
Prioritised Findings & Recommended Actions
Summarise the top insights from across all sessions, ranked by impact, and pair each with a concrete design or product recommendation for your team to act on.
Example: Finding 1 (Critical): Navigation mental model mismatch — users expect export to live in Analytics. Recommendation: Move export entry point to Analytics or add a cross-link. Finding 2 (High): Unlabelled icons cause task abandonment. Recommendation: Add persistent tooltip labels to all toolbar icons.

Full Copyable Template

How to use it

  1. Set up your task scenarios before each session
    Fill in Section 1 for every participant so you have consistent context that makes cross-session comparison reliable.
  2. Capture observations and quotes in real time
    Use Section 2 during the session itself — timestamp every notable behaviour and write quotes verbatim so you don't lose nuance when reviewing later.
  3. Log and rate every issue immediately after each session
    Complete Section 3 while the session is fresh, assigning severity and tracking how often each issue appears across participants.
  4. Synthesise findings across all sessions into Section 4
    Once all sessions are done, group recurring issues by theme, rank them by severity and frequency, and write one clear action per finding for your product team.

What it looks like filled in

Navigation Mental Model Mismatch
"I kept looking in Analytics — it never occurred to me that exporting would be a Settings thing."
→ Relocate the export function to the Analytics section or add a persistent shortcut link from Analytics to Settings exports.
Unlabelled UI Controls Cause Abandonment
"I didn't want to click something I didn't understand — I was worried I'd break something or lose my data."
→ Add visible text labels or always-on tooltips to all toolbar icons to eliminate ambiguity and reduce task hesitation.
Default Export Format Doesn't Match User Expectation
"I wanted CSV straight away — I use it in Excel. The PDF default just added an extra step I wasn't expecting."
→ Set CSV as the default export format and surface format options more prominently before the user initiates the download.

Why teams skip the template

  • Manually reviewing hours of session notes is exhausting and slow
    Combing through timestamped observations across five or more sessions to spot patterns takes hours of focused work that's easy to rush or cut short under deadline pressure.
  • Severity ratings are subjective and inconsistent across researchers
    When different team members rate the same issue differently, your prioritisation becomes unreliable and stakeholder conversations stall over conflicting interpretations.
  • Synthesis is where nuance gets lost
    Compressing rich qualitative observations into a findings summary by hand means subtle but important signals — especially low-frequency but high-severity issues — often get dropped entirely.

Analyze your usability test observations and session notes automatically — no template needed

👉 TRY IT NOW FREE