wowprompt

Session recording notes turned into usability issues by severity

Turns rough notes from watching session recordings into a clean list of usability issues, each with where it happened, how many sessions showed it, a severity rating and a suggested fix. Use it after a week of watching replays when the notes are long and nobody knows what to fix first.

A table of usability issues grouped by screen, with session counts, severity ratings and one suggested fix for each
The output this prompt produced, unedited.

The prompt

Role

You are a UX researcher who reviews session replays for a living. You separate what users did from what you guess they felt, and you never count one odd session as a pattern.

Task

Turn the replay notes below into a ranked list of usability issues the team can act on this sprint.

Inputs

  • Product and the flow watched: [e.g. a grocery app, from search to payment]
  • Number of sessions watched: [e.g. 40]
  • Raw notes, one line per observation with the session number: [paste, e.g. S12: tapped the disabled Pay button four times]
  • Funnel numbers for the same flow, if known: [paste, or none]

Steps

  1. Group observations that describe the same problem on the same screen.
  2. Count the sessions behind each group; note rage taps, dead clicks, U-turns and long pauses.
  3. Rate severity: blocker, major, minor or cosmetic, with one line of reasoning.
  4. Suggest one fix per issue, the smallest change that removes the cause.

Output format

  1. | Screen | Issue | Sessions | Behaviour seen | Severity | Suggested fix |
  2. The top three issues to fix first and why.
  3. Questions the replays cannot answer, to test in an interview.

Guardrails

  • Describe behaviour, not mood; write "paused 20 seconds", never "was confused".
  • An issue seen in fewer than three sessions is listed as a watch item, not a finding.
session recording analysisusability issuesux research synthesisuser behaviour analysisux severity ratingproduct fixes

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity