Use AI limitation onboarding to teach AI capabilities, limits, data scope, uncertainty, review needs, safe trial, feedback, and fallback before users rely on an AI feature; onboarding for product activation; inline message for local guidance; warning text for a risky action; confidence uncertainty display for reliability of one output; source grounding display for evidence coverage; scope clarification for an ambiguous request; and human approval gate for pausing execution.
Use AI limitation onboarding to teach AI capabilities, limits, data scope, uncertainty, review needs, safe trial, feedback, and fallback before users rely on an AI feature; onboarding for product activation; inline message for local guidance; warning text for a risky action; confidence uncertainty display for reliability of one output; source grounding display for evidence coverage; scope clarification for an ambiguous request; and human approval gate for pausing execution.
Practice the judgment: Imagine this situation: The AI is introduced as an expert teammate and users assume human-level judgment, full data access, or final authority. Write the person's goal, choose one of these patterns, and show the state that helps the person continue. Use the decision rules and source trail below to explain your choice.
Review the underlying principle →| Dimension | AI limitation onboarding | Onboarding | Inline message | Warning text | Confidence / uncertainty display | Source grounding display | Scope clarification | Human approval gate |
|---|---|---|---|---|---|---|---|---|
| UI or UX | UI + UX - First-use or new-feature onboarding that teaches AI capabilities, limits, uncertainty, user control, and recovery paths | UI + UX - First-run or new-feature orientation that leads to first value | UI + UX - Contextual in-flow feedback | UI + UX - Severe-consequence warning copy before an action | UI + UX - Calibrated reliability and uncertainty display for AI or automated predictions before user action | UI + UX - Whole-answer source coverage and grounding evidence display | UI + UX - AI clarification surface that asks for missing task boundaries before answering, planning, retrieving, or using tools | UI + UX - Runtime checkpoint that pauses AI or automation until an eligible human authorizes the next step |
| UI guidance | Use concrete examples, safe trial actions, capability cards, limitation chips, fallback buttons, feedback links, and review gates rather than long legal disclaimers or human-like claims. | Render onboarding as a short purposeful path with a visible benefit, current step, skip or later path when safe, persistent resume point, and the next product action users can take immediately after finishing. | Render the message inside the same row, card, panel, form section, or task region that it describes, with a clear tone, concise title, body text, and at most one local action or detail disclosure. | Render warning text as a short high-emphasis statement with a warning icon, visible or hidden warning label, and explicit consequence copy placed before the relevant action, declaration, or instruction. | Render confidence and uncertainty as labelled reliability information with confidence band, reason, input scope, calibration status, review threshold, freshness, and the next safe action. | Render source grounding as an answer-wide evidence panel that separates source scope, searched sources, retrieved sources, used sources, supported claims, partially supported claims, unsupported claims, and unresolved source states. | Render scope clarification as a focused question tied to the user's request, with the missing boundary named in plain language: object set, timeframe, audience, source set, authority, output depth, risk limit, or action target. | Render a human approval gate as a paused automation checkpoint with the proposed action, tool or workflow step, triggering rule, risk level, payload snapshot, requester or agent, approver eligibility, timeout, and explicit approve, reject, edit, cancel, or bypass controls. |
| UX guidance | Use AI limitation onboarding when users are first encountering an AI feature, a changed AI capability, or an agent with enough autonomy that users may over-trust, under-trust, anthropomorphize, or misuse it. | Use onboarding only when users need orientation, minimal setup, personalization, or instruction before the normal interface can deliver value, and remove steps that merely market features or repeat what the UI already explains. | Use inline messages when users need contextual feedback while continuing nearby work, such as a row-level warning, section-level success, local policy note, or task-specific next step. | Use warning text when users must understand a serious consequence before acting or failing to act, such as a fine, loss of access, permanent deletion, eligibility impact, or legal responsibility. | Use confidence / uncertainty display when users need to decide whether an AI prediction, classification, recommendation, extraction, risk assessment, or generated answer is reliable enough to apply. | Let users inspect coverage gaps, source scope, retrieval status, and unsupported claims before they copy, publish, apply, or rely on the answer. | Use scope clarification when an AI request is too broad, underspecified, conflicting, high-impact, or likely to produce the wrong answer unless the user narrows the task first. | Use human approval gate when automation is ready to act but policy, risk, confidence, cost, access, publication, deployment, customer impact, or legal consequence requires a human decision before execution continues. |
| Good UI | A contract assistant opens with I can summarize clauses and flag missing dates, but I may miss legal nuance; review source text before sending, then offers a sample contract to try safely. | A project-management app asks for role and team size, creates a sample board, highlights the first Add task action, and lets users skip the tour while keeping a setup checklist available. | An invoice row shows Missing billing contact directly beneath the affected customer with Add contact as the only action. | Before Submit declaration, a warning with an exclamation icon says the user may be fined if they provide false information. | A claim classifier says Medium confidence, 71 to 78 percent calibrated range, review threshold 80 percent, conflicting account-age signal, and routes the case to manual review. | A policy answer includes a Grounding panel showing 4 sources searched, 3 retrieved, 2 used, 5 supported claims, 1 partially supported claim, and 1 unsupported claim with a Review action. | An assistant receives Summarize the issues and asks Which issue set should I summarize? with Current sprint, All open issues, and Selected label choices before generating. | An AI support agent pauses before issuing a refund, shows the proposed amount, customer, policy match, confidence, source grounding, approver role, timeout, Approve refund, Edit amount, Reject, and Stop run controls. |
| Bad UI | The product explains uncertainty only after the user has already acted on a wrong answer. | A first launch shows six promotional slides about every feature, requires Next on each slide, and lands on an empty dashboard. | A section message contains a full support workflow, several links, and unrelated settings controls. | A red sentence says Important below the submit button after the user has already acted. | Users over-trust an AI answer because a confidence badge looks authoritative. | The answer shows a green Grounded badge even though only one citation supports one paragraph. | The assistant responds with ten open-ended questions even though one scope choice would let the task proceed. | A reviewer can approve an automation run after the action already executed, making the gate only decorative audit text. |
| Good UX | The person reaches the intended result with clear feedback. | A new admin selects Invite teammates as their goal, imports two sample users, sees progress saved, skips notification setup, and arrives on the team page with the invite action focused. | A successful send message remains beside the invoice long enough to copy the generated reference. | Users see the fine or eligibility consequence before checking the declaration and can pause to verify their answer. | A reviewer sees low confidence and out-of-distribution input, opens the reason panel, collects the missing invoice, and avoids auto-denying the claim. | The person reaches the intended result with clear feedback. | A user asks for a customer email draft; the assistant asks whether the audience is trial users, enterprise admins, or all affected accounts before drafting. | A billing lead opens the paused refund gate, sees that the amount is under policy but source grounding is partial, edits the refund to the verified amount, approves, and the agent resumes only that step. |
| Bad UX | A user assumes the assistant has read all company documents because onboarding says Ask me anything, then acts on an answer missing restricted policy files. | A user is forced to configure integrations, notifications, billing, and profile details before they know whether the product solves their task. | The message disappears like a toast even though users still need the invoice reference. | Users incur a penalty because the warning looked like ordinary hint text. | A model update invalidates old confidence scores but the UI keeps showing them as current. | Grounded status is shown before retrieval finishes. | A user answers a clarification question, but the assistant forgets the answer on the next step and asks again. | A human approves a stale agent action from email and the agent applies it to a different customer state. |
| Best fit | An existing AI feature changes enough that users need to recalibrate expectations before relying on it again. | New users need orientation, setup, personalization, or instruction before the regular interface can deliver value. | A visible object or section has local status, warning, success, or next-step information. | A user must understand a serious consequence before taking or skipping an action. | Users must judge whether an AI prediction, classification, recommendation, extraction, risk score, or generated answer is reliable enough to use. | Users need answer-wide evidence coverage before trusting generated content. | A user's AI request has missing object, audience, timeframe, source, workspace, permission, output-depth, or action-target boundaries. | An AI agent, workflow, deployment, or automation is ready to perform a high-impact step and must pause for human authorization. |
| Avoid when | The product only needs standard setup, account orientation, or a first-value path unrelated to AI capability limits. | The product is already understandable through the normal interface. | The message is a one-field validation correction. | The message is a dynamic task status that must be announced when it appears. | Users only need source coverage or claim evidence, which belongs to source grounding display or citation display. | The only task is opening one claim's source preview, which belongs to citation display. | The request is clear enough to answer safely and clarification would only slow the user down. | The action has already happened and users only need an audit log. |
| Required state | First-run welcome state with user benefit, AI role, and plain-language capability boundary. | First-run welcome state with benefit-focused copy and one clear next action. | Informational inline message attached to the relevant object or section. | Before-action warning state placed immediately before the related control or declaration. | High confidence state with calibration scope, reason, and whether direct apply is allowed. | Default grounded state with source scope, searched sources, retrieved sources, used sources, and supported-claim count. | Ambiguous request state with original prompt preserved and missing scope named. | Paused gate state with proposed action, payload snapshot, reason for gate, and run context. |
| Accessibility burden | Keep onboarding short and skippable where safe, with headings that let screen-reader users jump between Benefit, Limits, Data, Review, and Try sections. | Keep onboarding screens in normal heading order with clear titles and step labels. | Keep the message in the reading order near the context it describes. | Keep the warning in reading order before the control, declaration, or instruction it qualifies. | Expose confidence label, uncertainty reason, threshold, freshness, and gated action as text rather than relying on color, position, or animation alone. | Expose grounding summary, source scope, status counts, unsupported claims, and source groups as text. | Expose original request, missing boundary, choices, selected scope, default, blocked state, and resume status as text. | Expose gate status, proposed action, target, payload summary, risk, approver rule, timeout, and current run state as text. |
| Common misuse | Using charming human-like copy that implies broad expertise while hiding actual AI limits. | Forcing all users through a feature tour before they can do useful work. | Using an inline message for a single field error that should be connected to that input. | Using warning text for routine hints, explanations, or mild reminders. | Showing a fake percent or exact decimal for an uncalibrated model score. | Showing a global Grounded badge when only some claims have evidence. | Asking a long questionnaire when one boundary would let the task proceed. | Using a post-action audit record as if it were a pre-action human gate. |