Run a UX audit
A heuristic UX review with severity-ranked issues and redesign recommendations.
This is a practical, copy-paste process for users struggle, or conversion is weak.. Use it when you want a clear structure, then add your own details and the linked evidence.
Published by Deepstory Research. Reviewed Sep 2026.
How to use this method
- 1. Copy or downloadCopy the prompt below, or download the method file and attach it to your chat.
- 2. Paste into any AIChatGPT, Claude, Gemini or Copilot. Replace each [PLACEHOLDER] with your details, or let the AI ask you.
- 3. Add evidenceAttach the evidence files listed on this page so the AI works from sourced numbers, not guesses.
The prompt
Paste it as-is. The AI will ask for anything still in [BRACKETS].
# Run a UX audit Method by Deepstory Research: deepstoryresearch.com/method/ux-audit You are a UX lead using Nielsen’s heuristics. Follow the method below step by step. Goal: A heuristic UX review with severity-ranked issues and redesign recommendations. ## My inputs - Product and flow: [PRODUCT_AND_FLOW] (example: screenshots or URL descriptions) - User goal: [USER_GOAL] (example: book a test drive) - Known complaints: [KNOWN_COMPLAINTS] (example: support tickets) Before you start: if any input above is still in [BRACKETS] or missing, ask me for it in one short numbered list and wait. Do not guess. If I attached files (data, briefs, Deepstory evidence files), treat them as the primary source. ## Steps to follow 1. Walk the flow step by step. 2. Evaluate against heuristics and accessibility. 3. Rate severity. 4. Recommend fixes with examples. ## Deliver the output in this structure - Flow walkthrough - Issue table - Recommendations - Quick wins ## Quality rules - Issues tied to specific screens/elements. - Label every number as FACT (with source and date), ESTIMATE (show the calculation) or ASSUMPTION. - If a Deepstory evidence file is attached, use its figures as the reference values and cite its source references; tag claims that are not from it as [UNVERIFIED]. - End with: the 3 assumptions that matter most, what would change the answer, and the single best next step.
What you need to give the AI
| Input | Placeholder | Example |
|---|---|---|
| Product and flow | [PRODUCT_AND_FLOW] | screenshots or URL descriptions |
| User goal | [USER_GOAL] | book a test drive |
| Known complaints | [KNOWN_COMPLAINTS] | support tickets |
Use it when
- Users struggle, or conversion is weak.
What you get
- Flow walkthrough
- Issue table
- Recommendations
- Quick wins
The procedure, step by step
Read this before you run it, so you can check the AI actually followed the method.
Walk the flow step by step.
Evaluate against heuristics and accessibility.
Rate severity.
Recommend fixes with examples.
Quality checks built into the prompt
- • Issues tied to specific screens/elements.
- • Every number labelled FACT, ESTIMATE or ASSUMPTION; claims outside attached evidence tagged [UNVERIFIED].
Evidence for this method
This method runs on your own material: your files, brief or code. If your task needs market or economic numbers, attach a sourced context file from the evidence library alongside the prompt.
Browse evidenceRun next
Methods that chain well after this one.
Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment decisions need a qualified professional.