AI Feature UX Checklist

# AI Feature UX Checklist

Use this to audit an AI-powered product feature before it ships.

## 1. User Value

- [ ] The feature solves a specific user problem.
- [ ] AI is necessary or meaningfully improves the workflow.
- [ ] The user can understand what the feature is doing.
- [ ] The feature reduces effort without removing important user control.
- [ ] The workflow still works when AI output is imperfect.

## 2. Inputs

- [ ] Required inputs are clear.
- [ ] Optional context is easy to provide.
- [ ] The user knows what data will be used.
- [ ] Sensitive data expectations are explicit.
- [ ] Input examples are available when useful.
- [ ] Bad or incomplete input produces a helpful response.

## 3. Output Quality

- [ ] Output is structured for the next user action.
- [ ] Uncertainty is visible when confidence is limited.
- [ ] Sources or rationale are shown when decisions need trust.
- [ ] The user can edit, regenerate, accept, reject, or undo.
- [ ] The output avoids false precision.
- [ ] The product avoids presenting generated content as verified fact.

## 4. Failure States

- [ ] Slow responses have a clear loading state.
- [ ] Model errors are recoverable.
- [ ] Empty or low-quality responses explain what happened.
- [ ] Rate limits or quota issues have clear messaging.
- [ ] The user can continue manually.
- [ ] The system avoids dead ends.

## 5. Trust And Safety

- [ ] The feature states what it can and cannot do.
- [ ] Risky outputs require review before action.
- [ ] The user can inspect or correct important assumptions.
- [ ] Personal, financial, legal, or health claims are treated carefully.
- [ ] Generated recommendations are distinguishable from deterministic product logic.
- [ ] Abuse cases and prompt injection paths have been considered.

## 6. Evaluation

- [ ] The team has examples of good and bad outputs.
- [ ] The team has a review process for regressions.
- [ ] Success metrics are tied to user outcomes, not model usage alone.
- [ ] Human feedback can be collected.
- [ ] Logs capture enough context to debug safely.
- [ ] The feature can be disabled or rolled back.

## 7. Interface Polish

- [ ] Copy is direct and non-magical.
- [ ] The UI does not overpromise.
- [ ] Generated content is visually integrated with the workflow.
- [ ] Review actions are close to the generated output.
- [ ] The feature works on mobile and desktop.
- [ ] Accessibility basics are covered for streaming, updates, and status messages.