Use this workflow to analyse a marketing page or funnel step for UX friction that may prevent visitors from converting.

### Required Input
- Page or Funnel Step: [Describe the exact experience to analyse. Example: lead magnet signup page, demo request form, checkout page]
- User Goal: [State what the visitor is trying to accomplish. Example: understand pricing, request a demo, download a guide]
- Business Conversion Goal: [State the desired action. Example: completed form submission, trial signup, purchase]
- Target Audience: [Describe visitor type. Example: small business owners comparing accounting software]
- Page Copy or Experience Description: [Paste copy or describe key sections, fields, navigation, CTA, and layout. Example: hero, benefits, 7-field form, testimonials, FAQ]
- Known Behaviour Data: [Share available observations. Example: high mobile bounce, low form completion, drop-off at payment step]
- Device or Context Priority: [State whether desktop, mobile, or both matter most. Example: mobile traffic is 72%]
- Constraints: [List limits. Example: cannot remove required compliance checkbox, design changes must be light]

### Input Validation
Review all required inputs before analysing friction. If the experience description is incomplete, the goal is unclear, or behaviour data is missing, ask specific clarification questions and pause. Do not produce the analysis until the inputs are clear enough.

### Instructions
Analyse friction from the visitor's perspective. Focus on moments where the experience causes confusion, hesitation, unnecessary effort, mistrust, distraction, or decision fatigue.

Evaluate:
- Clarity of the next step
- Cognitive load and reading effort
- Form length, field labels, and perceived commitment
- CTA placement and wording
- Information hierarchy
- Trust signals and reassurance
- Navigation distractions
- Mobile usability risks
- Error prevention and recovery
- Alignment between visitor goal and page flow

Avoid vague design opinions. Every issue must explain how it affects conversion behaviour.

### Output
Return the analysis in this structure:
1. UX Friction Summary
- State the main friction pattern and likely conversion impact

2. Friction Inventory
Create a table with these columns:
- Friction Point
- User Impact
- Likely Cause
- Severity: High, Medium, or Low
- Evidence or Assumption

3. High-Priority Fixes
Create a table with:
- Fix
- Exact Change
- Why It Helps
- Effort: Low, Medium, or High
- Priority Rank

4. Form or CTA Improvements
Provide revised field, CTA, or microcopy recommendations where relevant.

5. Mobile-Specific Watchouts
List likely mobile risks and practical checks.

6. Measurement Plan
Recommend metrics or observations to track after changes.

7. Implementation Order
List the first 5 fixes to make.