Prompts for UX Audits

8 ready-to-use ChatGPT prompts for UX audits. Fill in the bracketed fields, paste into ChatGPT, and go.

Product & UX · 8 prompts

01

Audit an Onboarding Flow for Friction

Review an onboarding flow for friction, confusion, and missed activation opportunities.

You’ll needflow descriptiontarget usersactivation goaldrop-off pointsconstraints
Prompt
You are a UX auditor focused on onboarding and activation.

Audit the onboarding flow below.

Context:
- Flow description: [flow]
- Target users: [users]
- Activation goal: [goal]
- Known drop-off points: [dropoffs]
- Constraints: [constraints]

Instructions:
1. Review the flow for clarity, momentum, trust, and unnecessary friction.
2. Identify the highest-impact points where users may hesitate, abandon, or misunderstand.
3. Explain why each issue likely affects activation.
4. Recommend fixes in priority order.
5. Separate quick wins from structural redesign opportunities.

Output format:
- Audit summary
- Top friction points
- Findings table: issue, why it matters, recommended fix
- Quick wins
- Deeper redesign ideas

Missing information policy:
Ask up to 2 concise questions only if the flow or activation goal is unclear. Otherwise proceed with assumptions.

Quality bar:
- Tie every point to user behavior.
- Prioritize impact.
- Avoid generic audit commentary.
02

Audit a Mobile Experience for Usability

Review a mobile experience for usability, hierarchy, and task-completion issues.

You’ll needmobile flowtarget usersgoaldevice contextknown issues
Prompt
You are a mobile UX reviewer.

Audit the mobile experience described below.

Context:
- Mobile flow or screens: [flow]
- Target users: [users]
- Primary goal: [goal]
- Device or context notes: [device context]
- Known issues: [issues]

Instructions:
1. Review the experience for clarity, hierarchy, tap targets, cognitive load, and continuity across screens.
2. Identify usability issues that are especially costly on mobile.
3. Explain why each issue matters to completion or confidence.
4. Recommend fixes with attention to implementation realism.
5. Prioritize the issues by likely user impact.

Output format:
- Audit summary
- Top issues
- Findings table
- Quick wins
- Strategic improvements

Missing information policy:
Proceed with assumptions unless the flow or primary goal is unclear.

Quality bar:
- Mobile-specific thinking.
- Concrete rationale.
- No generic design filler.
03

Audit a Product Page for Trust and Clarity

Review a product page for trust, message clarity, and decision friction.

You’ll needpage descriptiontarget audienceconversion goalknown objectionstraffic source
Prompt
You are a UX and conversion reviewer.

Audit the product page below for trust and clarity.

Context:
- Page description: [page]
- Target audience: [audience]
- Conversion goal: [goal]
- Known objections: [objections]
- Traffic source or acquisition context: [traffic]

Instructions:
1. Review message clarity, trust signals, hierarchy, proof, and CTA friction.
2. Identify what may be making users hesitate or defer a decision.
3. Explain which problems are likely to matter most.
4. Recommend specific fixes in priority order.
5. Distinguish copy problems from structural UX problems.

Output format:
- Trust and clarity assessment
- Main friction points
- Recommended fixes
- Quick wins

Missing information policy:
Proceed with assumptions unless the page or conversion goal is unclear.

Quality bar:
- Focus on why users hesitate.
- Separate UX from copy.
- Prioritize changes by likely lift.
04

Run a Product Design Critique That Produces Better Decisions

Create a critique structure that keeps product and design reviews focused on goals, evidence, and decision quality.

You’ll needdesign work under reviewproduct goaluser contextcurrent critique problemsparticipants
Prompt
You are a product design critique facilitator.

Design a better critique structure for the situation below.

Context:
- Design work under review: [design work]
- Product goal or user outcome: [goal]
- User context: [user context]
- Current critique problems: [problems]
- Participants or roles involved: [participants]

Instructions:
1. Define how the critique should frame the problem, user goal, and constraints before opinions begin.
2. Create a structure for separating observed issues, hypotheses, tradeoffs, and decisions.
3. Suggest prompts that improve the quality of feedback from PMs, designers, and engineers.
4. Explain how to prevent the session from collapsing into subjective preference fights.
5. Include outputs the team should leave with after the critique.

Output format:
- Critique structure
- Facilitation prompts
- Rules for high-quality feedback
- Decision outputs
- Anti-patterns to avoid

Missing information policy:
Proceed with assumptions unless the design work or goal is too vague to anchor the critique.

Quality bar:
- Tie discussion to the user and product goal.
- Improve decision quality, not just feedback volume.
- Avoid taste-based drift.
05

Audit an Internal Tool Workflow for Friction and Trust Problems

Audit an internal tool workflow for friction, trust breakdowns, confusing states, and adoption barriers.

You’ll needworkflow descriptiontarget userskey tasksadoption issuestrust concernsconstraints
Prompt
You are auditing an internal tool workflow for friction and trust problems.

Use the context below.

Context:
- Workflow description: [workflow]
- Target users: [users]
- Key tasks in the workflow: [tasks]
- Adoption issues or workarounds: [adoption issues]
- Trust concerns or output doubts: [trust concerns]
- Constraints: [constraints]

Instructions:
1. Identify where the workflow creates friction, uncertainty, or unnecessary manual work.
2. Diagnose why users may not trust the tool, output, or system state.
3. Separate clarity issues from deeper product or operational design problems.
4. Recommend the highest-leverage improvements first.
5. Keep the audit tied to real user behavior rather than generic UX theory.

Output format:
- Audit summary
- Main friction points
- Trust breakdowns
- Highest-leverage improvements
- Risks if unchanged

Missing information policy:
Proceed with assumptions unless the workflow or trust concerns are unclear.

Quality bar:
- Real user-behavior focus.
- Trust-specific diagnosis.
- Prioritized fixes.
06

Audit an AI Workflow for Trust Erosion in the Output Layer

Audit an AI workflow for trust erosion in the output layer, including clarity gaps, overclaiming, and review friction.

You’ll needAI workflowuser-facing outputsuser reactionsknown trust issuesrisk areasproduct context
Prompt
You are auditing an AI workflow for trust erosion in the output layer.

Use the context below.

Context:
- AI workflow or feature: [workflow]
- User-facing outputs: [outputs]
- User reactions or observed behavior: [reactions]
- Known trust issues: [trust issues]
- Risk areas: [risks]
- Product context: [context]

Instructions:
1. Identify where the output layer creates overtrust, undertrust, or confusion.
2. Clarify how copy, presentation, and workflow state may be contributing to trust erosion.
3. Distinguish product-quality problems from communication and framing problems.
4. Recommend the highest-leverage fixes first.
5. Keep the audit grounded in real user behavior.

Output format:
- Trust audit summary
- Main trust erosion points
- Why users may distrust or overtrust the output
- Recommended fixes
- Risks if unchanged

Missing information policy:
Proceed with assumptions unless the workflow or user-facing outputs are unclear.

Quality bar:
- Trust-specific diagnosis.
- User-behavior grounding.
- Prioritized recommendations.
07

Review Why Users May Resist an AI Workflow Assistant

Review why users may resist an AI workflow assistant, including trust, workflow fit, and perceived value issues.

You’ll needassistant concepttarget userscurrent workflowadoption concernstrust issuesstakes of failure
Prompt
You are reviewing why users may resist an AI workflow assistant.

Use the context below.

Context:
- Assistant concept or current feature: [concept]
- Target users: [users]
- Current workflow or existing habits: [workflow]
- Adoption concerns or objections: [concerns]
- Trust issues or known skepticism: [trust issues]
- Stakes of assistant failure: [stakes]

Instructions:
1. Diagnose the strongest reasons users may resist adoption.
2. Distinguish lack of trust from lack of usefulness or poor workflow fit.
3. Identify where current habits or incentives work against adoption.
4. Recommend what would most improve credibility and fit.
5. Keep the review grounded in user behavior, not generic AI fear.

Output format:
- Adoption-risk summary
- Main sources of resistance
- Trust and workflow-fit issues
- Highest-leverage improvements
- Risks if adoption stays weak

Missing information policy:
Proceed with assumptions unless the assistant concept or target users are unclear.

Quality bar:
- Behavior-grounded diagnosis.
- Trust and usefulness both addressed.
- Actionable adoption insights.
08

Audit Whether a Workflow Is Fragmented Across Too Many Tools

Audit whether a workflow is fragmented across too many tools and identify the biggest coordination and trust costs.

You’ll needworkflow descriptiontools involvedhandoffsfriction symptomsuser groupsbusiness stakes
Prompt
You are auditing whether a workflow is fragmented across too many tools.

Use the context below.

Context:
- Workflow description: [workflow]
- Tools, systems, or surfaces involved: [tools]
- Handoffs or transition points: [handoffs]
- Friction symptoms or error patterns: [symptoms]
- User groups involved: [users]
- Business stakes: [stakes]

Instructions:
1. Identify where fragmentation is creating unnecessary cognitive load or execution risk.
2. Distinguish necessary complexity from avoidable tool sprawl.
3. Surface the worst handoff or context-switching points.
4. Recommend where consolidation, tighter integration, or workflow redesign would help most.
5. Keep the audit grounded in actual usage patterns.

Output format:
- Fragmentation audit summary
- Main tool or handoff problems
- Workflow costs created by fragmentation
- Highest-leverage simplifications
- Risks if unchanged

Missing information policy:
Proceed with assumptions unless the workflow or tools involved are unclear.

Quality bar:
- Usage-pattern grounding.
- Clear fragmentation costs.
- Practical simplification guidance.