Lessons and outlineLesson 5 of 10

AI Product ManagerLesson 5

18 min read

Designing AI Experiences

Set expectations, show your work, handle doubt, ease correction and design the handoff.

In plain English

Good design builds the right amount of trust. Set honest expectations, show sources and steps, and make doubt visible in plain words with a next step. Make correction easy with edit, undo and confirm. Collect feedback in the flow and design the handoff to a person.

Handoff
Passing the user to a person, with the context.
Streaming
Showing the answer as it is written.
Over-trust
Relying on the AI more than its quality deserves.
Picture it
Building the right trust
1
Set expectations
Purpose and limits
2
Show sources and steps
So users can check
3
Show doubt in plain words
With a next step
4
Make correction easy
Edit, undo, confirm, hand off

The best model can still make a bad product if the experience is poor. People need to know what the AI is doing, when to trust it, how to fix it and how to reach a person. This lesson covers design patterns for AI features that build trust and make mistakes easy to recover from.

Set expectations

  • Say what the feature is for and what it is not for.
  • Tell people it is AI, in simple words, where it matters.
  • Show an example of a good request, which teaches users how to ask.
  • Do not overpromise. Words such as always accurate or fully automatic break trust when the first error appears.

Show your work

  • Show sources for answers drawn from documents, with links that open the right part.
  • Show what the AI did: steps taken, tools used, data read.
  • Show what it changed, and let users compare before and after.
  • Use plain labels such as drafted by AI, so users know to check.

Handle doubt honestly

Good products make doubt visible. When the AI is unsure, it says so, and offers a next step: ask a clarifying question, show likely options, or hand over to a person. Avoid fake precision, such as 87 percent sure, when the number is not reliable. Plain words work better: I'm not sure about this, please check.

Make correction easy

  • Let users edit AI output directly.
  • Offer undo for every action the AI takes.
  • Let users regenerate, refine with a short instruction or choose from options.
  • For actions with consequences, show a preview and ask to confirm.

Collect feedback in the flow

  • A simple thumbs up or down, with an optional reason.
  • Learn from edits: what did the user change?
  • Let users report a problem in one click.
  • Thank them, and tell them when you fix things.

Design for waiting

Models take time. Streaming text as it arrives makes waiting feel shorter. For long tasks, show progress and what is happening. Let users do something else and notify them when it is ready. Never leave a blank screen.

Design the handoff to people

Some cases need a human. Make the path clear and quick. Pass the whole context to the person, so the user does not repeat themselves. Tell the user what to expect, such as a reply within an hour.

ai-ux-checklist.md
[ ] Purpose and limits are clear in the first view
[ ] The user knows it is AI where it matters
[ ] Sources and steps are visible
[ ] Doubt is shown in plain words with a next step
[ ] Edit, undo, regenerate and confirm are available
[ ] Feedback takes one click
[ ] Waiting has streaming or progress
[ ] Errors explain what happened and how to recover
[ ] Handoff to a person is easy and carries context
[ ] Works with a keyboard and a screen reader; text is readable
[ ] Works in the languages and on the devices your users use

Avoid common mistakes

  • Hiding that content is AI-made.
  • A chat box for everything, when a button or a form would be clearer.
  • No way to fix mistakes.
  • Too many options, or too few clues about what to ask.
  • Blaming the user for a bad answer.
⚠Over-trust is as risky as distrust. If the interface looks too certain, people stop checking. Calibrate the design so that care matches the risk.
Key takeaways
  • ✓Set honest expectations: purpose, limits, an example request and no overpromising.
  • ✓Show sources, steps and changes. Make doubt visible in plain words, with a next step.
  • ✓Make correction easy with edit, undo, regenerate and confirm, and collect feedback in the flow.
  • ✓Design for waiting and for handoff to a person with full context, and avoid hiding AI or blaming users.
Hands-on exercise

Design the states of one feature

  1. Take an AI feature that drafts replies to customer emails.
  2. Sketch or describe five states: first use, loading, a good answer, an unsure answer and an error.
  3. For each state, write the exact words the user sees and the next action offered.
  4. Run the checklist and mark any line that you missed.
Check yourself
Q1Why prefer plain words to a confidence number?show answer

A number looks precise but may not be reliable. Plain words such as I'm not sure, please check are clearer and lead to a next step.

Q2Why show sources?show answer

They let users check answers and build trust, and they make errors easier to find.

Q3Why make handoff to a person carry context?show answer

The user does not have to repeat themselves, which saves time and avoids frustration.

0 / 10 0%