Augment

Designing for AI Mistakes: Errors, Hallucinations, and Uncertainty

Every AI feature will be wrong sometimes. The product's job is to make mistakes visible, small, and fixable.

A dark analytics dashboard showing retention and usage charts
Photo by Luke Chesser on Unsplash, with an Augment halftone treatment
Executive Summary

Key Takeaways

  • Plan for wrong answers as a normal state, not an edge case.
  • Use plain language to signal uncertainty. Raw confidence scores confuse more than they help.
  • Give users a one-step way to report, correct, or retry a bad result.
  • Match the guardrails to the stakes: the higher the cost of a mistake, the more review it needs.

Wrong is a normal state

Language models can produce fluent text that is simply incorrect. Designers cannot remove that risk. They can decide how the product behaves when it happens.

Nielsen's classic heuristics still apply. Help users recognize, diagnose, and recover from errors. Keep them informed about system status. Give them control and freedom to back out. AI does not retire these rules. It makes them more important.

Match guardrails to the stakes

StakesExampleDesign response
LowA suggested email subjectShow it, let the user edit, no extra friction
MediumA summary of a customer callLink to the source, flag unverified claims
HighA change to billing or permissionsPreview the effect, require approval, log it
CriticalMedical, legal, or financial adviceKeep a human expert in the loop, restrict scope

Say "I am not sure" like a person would

A percentage like 72% means little to most people. A sentence like "I could not find this in your documents, so this is a guess" tells them exactly what to do. Use plain flags where uncertainty changes the next step, and stay quiet where it does not.

Make correction one click

  • Put a visible way to correct or flag an output next to it, not in a menu.
  • Offer reasons as quick choices: wrong fact, wrong tone, not relevant.
  • Let users retry with the correction applied, and confirm it worked.
  • Feed corrections back to your team so recurring failures get fixed in the product.

Empty and failure states matter too

When the model cannot answer, do not show a generic error. Explain what happened, what the user can try, and offer a non-AI path to finish the task. A dead end is the worst failure mode for a feature meant to save time.

Frequently Asked Questions

Link claims to sources where possible, flag unverified content, make correction easy, and add review steps when the stakes are high.

Sources and further reading

  1. 10 Usability Heuristics for User Interface DesignNielsen Norman Group · Published · Updated · Accessed
  2. People + AI GuidebookGoogle PAIR · Published · Updated · Accessed
  3. Designing AI Products and Features: Study GuideNielsen Norman Group · Published · Accessed

Credits

  • Written by Augment Editorial Team, Product design and engineering, Augment Lab.
  • Cover photo Photo by Luke Chesser on Unsplash, with an Augment halftone treatment, used under the Unsplash License.
  • Research Statistics and standards are cited from the sources above. Always check the original page for the latest version.

Augment Product Design

Ready to make your product clearer?

From first concept to go-live, we turn complex product ideas into clear, useful experiences.

Designing for AI Mistakes: Errors, Hallucinations, and Uncertainty | Augment. Lab