Look closely at the AI products people actually enjoy using and you start to see the same few ideas again and again. They are not the same features. They are the same AI UX patterns: small, repeatable answers to the moments where AI products usually go wrong.
In my earlier posts I defined what AI-native design really means and showed how the autonomy dial decides how much an AI should do on its own. This post is about the AI UX patterns that make those decisions work on screen. I group them into three families: wayfinders, governors and trust builders.
Why AI UX patterns matter
Traditional interfaces fail in predictable ways: a broken link, an unclear label, a form that rejects a valid date. AI interfaces fail in new ones. People do not know what to ask. The system does something nobody approved. The answer sounds right and is not. Each of these moments needs its own design answer, and once you name them you can reuse them across a whole product.
AI UX patterns also make design reviews faster. Instead of debating every AI screen from scratch, the team can ask three questions: how does the user start, how does the AI act, and how does the user check the result?
Figure 1 · Three families of AI UX patterns across one journey
01 Start
Wayfinders
Suggestion chips, examples, prompt helpers. Replace the blank box.
02 Act
Governors
Plan previews, approvals, stop and undo. Pause before the irreversible.
03 Verify
Trust builders
Citations, visible reasoning, confidence cues. Make it easy to check.
Wayfinders: AI UX patterns that replace the blank prompt
An empty text box with a blinking cursor is the most common AI interface, and one of the hardest to use. It assumes people know what the system can do and how to ask for it. Most people do not, so they type something vague, get something vague back, and decide the product is not for them.
Wayfinders are the AI UX patterns that give people a place to start. The most familiar form is suggestion chips: short, tappable prompts that show what the system is good at. Spotify’s AI Playlist is a good example, offering ready-made prompt ideas so a listener can try it without inventing a request from nothing. Other common wayfinders include:
- Example galleries that show finished results and the request that produced them.
- Prompt helpers, such as an “improve my prompt” button that turns a rough request into a detailed one the user can still edit.
- Context starters that begin from what the user already has open: “Summarise this document” next to the document, not in a separate chat window.
- Follow-up suggestions after an answer, so the second step is as easy as the first.
When to use them: on first use, on any open-ended input, and whenever analytics show short, vague first prompts followed by drop-off. A good wayfinder teaches the system’s capabilities while the person is already using it, which is why these AI UX patterns also belong in AI product onboarding.
Watch out for: generic chips that could appear in any product. “Write a poem” teaches nothing in a project management tool. The best suggestions are specific to the user’s data and goal.
Governors: AI UX patterns that show the plan before acting
As AI moves from answering to acting, the risk moves too. A wrong answer wastes a minute. A wrong action can send an email, change a codebase or move money. Governors are the AI UX patterns that keep people in control at the moments that matter.
The clearest governor is the plan preview. Before doing multi-step work, the AI shows what it intends to do and waits. Coding agents have made this mainstream: tools such as Cursor and Replit offer planning modes where the agent proposes the steps and files it will change, and the developer approves, edits or rejects the plan before any code is written. The same pattern works for any agent: a travel booking, a data clean-up, a batch of emails.
Other governors include:
- Approval checkpoints placed only before steps that are hard to undo, not before every step.
- Scope controls that limit what the AI can touch, such as one folder, one project or a spending limit.
- A visible stop button while the AI is working, and a clear record of what it did before it stopped.
- Undo for every action the AI takes on its own.
Where to put the pause: use the autonomy dial. Low-risk, easy-to-undo actions should flow without interruption. Approvals belong just before the irreversible step, where a person can still change the outcome. Too many approvals train people to click yes without reading, which is worse than none.
Figure 2 · A governor in practice: the plan preview
Plan: tidy the Q4 client folder
1. Rename 42 files to the client naming format
2. Move 12 duplicates to Archive
3. Share the folder with 3 client contacts (needs your approval)
Approve planEdit steps
Trust builders: AI UX patterns that make the AI easy to verify
AI can be wrong while sounding completely sure. Telling people to “always double-check” does not help unless the product makes checking easy. Trust builders are the AI UX patterns that turn verification from a chore into a glance.
The best-known example is the inline citation. Answer engines such as Perplexity place small numbered source markers next to each claim, so a reader can open the exact source behind a sentence instead of searching for it. Other trust builders include:
- Visible reasoning, often a collapsible panel that shows the steps the AI took. Closed by default, available when someone wants to check.
- Confidence cues that mark uncertain parts of an answer, or say plainly when the system does not know.
- Diff views that show exactly what the AI changed in a document or codebase, line by line.
- Editable outputs, so correcting the AI takes one click rather than a new prompt.
- Feedback controls that let people flag a wrong answer and see that it made a difference.
These AI UX patterns are well supported by research. Microsoft’s Guidelines for Human-AI Interaction include making clear why the system did what it did and supporting efficient correction. Google’s People + AI Guidebook covers explainability and trust in similar terms.
Watch out for: fake transparency. A long reasoning panel nobody reads, or citations that do not actually support the claim next to them, damage trust faster than having none.
How the three AI UX patterns work together
The real value appears when the three families of AI UX patterns cover a whole journey. Take a finance team using an AI assistant to prepare a monthly report.
- Start (wayfinder): the assistant opens with “Draft October’s variance report from the ledger”, based on what the team did last month, instead of a blank box.
- Act (governor): it shows a plan, which data it will pull, which charts it will build, and who it will send the draft to, and asks for approval only before sharing.
- Verify (trust builder): every number in the draft links to the ledger rows behind it, and anything the AI estimated is clearly marked.
Remove any one of the three and the experience weakens. Without the wayfinder people never start. Without the governor they do not dare to let it act. Without the trust builder they redo the work by hand, and the AI saves nothing.
An AI UX patterns checklist for design reviews
Use these questions on any AI feature before it ships:
- Does a first-time user see at least one specific, useful way to start?
- Are suggestions based on the user’s own context, not generic examples?
- Before any action that is hard to undo, does the user see the plan and approve it?
- Can the user stop the AI while it works, and undo what it did?
- Can every factual claim be traced to a source in one click?
- Does the product say clearly when the AI is unsure or does not know?
- Can the user correct an output directly, without starting again?
If you are reviewing an existing product, these AI UX patterns also make a useful extra section in a wider UX audit.
What comes next
Wayfinders, governors and trust builders cover how people start, act and verify. The next shift goes further: interfaces that assemble themselves around each answer. In the next post in this series I look at generative UI and what it means for design systems and for the job of the designer.
Which of these AI UX patterns is weakest in the AI product you use most? I am discussing them one by one in my AI-Native, Explained series on LinkedIn, and I would like to hear your examples.
Frequently asked questions
What are AI UX patterns?
AI UX patterns are reusable design solutions for the moments where AI products usually fail: knowing how to start, letting the AI act safely, and checking whether its output is right.
What is a wayfinder in AI UX?
A wayfinder helps people start using an AI feature without facing a blank prompt. Examples include suggestion chips, example galleries, prompt helpers and follow-up suggestions.
What is a governor in AI UX?
A governor keeps people in control when AI takes actions. Examples include plan previews, approval checkpoints before irreversible steps, scope limits, a stop button and undo.
How do you build trust in AI interfaces?
Make the AI easy to verify: inline citations, visible reasoning, clear signals of uncertainty, diff views of changes and outputs people can edit directly.
