AI

Hallucinations

A practical guide to understanding why AI generates false information and what to do about it.

What AI hallucinations are, why they happen, how to spot them, and how to design AI products that account for them.

22 May 20264 min read

What it is

An AI hallucination is when a language generates information that is factually incorrect, fabricated, or entirely made up — but presents it confidently as if it were true.

Hallucinations happen because language do not retrieve facts. They generate text based on learned during training. When asked about something outside their knowledge or in an area where was limited, they fill the gap with what sounds most plausible.

This can produce convincing-sounding but completely wrong answers — including invented citations, fictitious statistics, and events that never happened.

Hallucinations are not a sign of a broken . They are a known characteristic of how these work.

The practical implication is that any AI-generated content that will be used in a real needs to be validated before it is relied on.

When to use it

Understand when hallucinations are a serious risk. They are most problematic when:

They are a lower risk when:

The AI is being used to generate factual claims, citations, or data
Outputs will be used without human review
The subject matter is specialised, niche, or recent
Users will trust AI responses without questioning them
Errors would be costly, embarrassing, or harmful
Outputs are creative, stylistic, or generative in nature
Human review is built in before outputs are used
The AI is grounded in a reliable knowledge source through RAG

Key takeaway

Assume hallucinations will happen. Design your AI features around that assumption rather than hoping they will not occur.

How it works

Understand the basic mechanism. Language generate by predicting the most likely next token given everything that came before it. They do not look up facts — they -match from training.

When a does not have reliable on a topic, it still generates a confident-sounding based on what typically surrounds similar questions. That is where hallucinations come from.

The has no internal mechanism to signal uncertainty in the way a human expert might say they do not know.

What this means for designers and product teams. Every AI that surfaces factual information to users carries hallucination risk. That risk needs to be designed around, not ignored.

Design choices that help include grounding the AI in a verified knowledge source (RAG), building in human review before outputs are used, displaying where appropriate, and making it easy for users to verify or question AI-generated content.

What to look for

Focus on:

Specificity without source — confident facts with no way to verify them
Invented references — citations, links, or statistics that do not exist
Plausibility over accuracy — answers that sound right but cannot be confirmed
Edge case inputs — topics where the model's training data is likely to be thin
User over-trust — whether users are accepting AI outputs without scrutiny

Where it goes wrong

Most issues come from: If you ship AI-generated content without a validation step, hallucinations will eventually reach your users.

Removing human review to save time or cost
Assuming a well-known model is reliable across all topics
No process for catching or correcting errors after they occur
Outputs used in high-stakes contexts without grounding or validation
Users not being informed they are reading AI-generated content

What you get from it

Understanding hallucinations gives you:

Clearer criteria for when AI outputs need human review
A stronger brief for how AI features should handle uncertainty
Better decisions about where to use AI and where not to
A more honest conversation with stakeholders about AI limitations

Key takeaway

Hallucinations are not an edge case — they are a regular occurrence. The question is not whether they will happen, but whether your design accounts for them.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is an AI hallucination?

It is when an AI generates information that is factually wrong or entirely made up, but presents it confidently as if it were accurate. The is not lying — it is -matching from its and producing what sounds most plausible, even when it does not have reliable information to draw from.

Why do AI hallucinations happen?

Because language generate text based on statistical , not verified facts. When a model encounters a topic where its is limited, it still produces a response — it just has less reliable information to base it on.

Can hallucinations be prevented?

Not entirely, but they can be significantly reduced. Grounding the in a reliable knowledge source (RAG), using well-structured , and building in human review are the most effective approaches. Hallucinations cannot be eliminated, but their impact can be managed.

How do I spot a hallucination?

Look for specific facts, statistics, or citations that cannot be verified. If an AI gives a precise number, names a specific study, or cites a source, check it. Hallucinations tend to be specific and confident — vague answers are usually less likely to be fabricated.

Should I tell users that AI can hallucinate?

Yes. Being transparent about the limitations of AI and helps users engage with outputs critically. Hiding the fact that AI can be wrong and then having it get something wrong is much more damaging than being upfront about limitations from the start.

Quick take

AI hallucinations are not glitches — they are a fundamental characteristic of how language models work, and designing around them is part of the job.

Related Services

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services. The work usually starts where things have become harder than they need to be: unclear journeys, inconsistent products, competing priorities, or teams trying to move forward without a clear direction. I help simplify the problem, shape the right next step, and turn complexity into something people can actually use.

Previous feedback

Will Parkhouse

Senior Content Designer

01/20