Heuristics H9 4 min read

Errors are inevitable. Confusion is not

09 Heuristic 9 Help Users Recognize, Diagnose, and Recover from Errors

Error messages should be expressed in plain language, precisely indicate the problem, and constructively suggest a solution.

Every user will hit an error eventually. What separates a trustworthy product from a frustrating one isn't whether errors happen — it's what the product says when they do. Clarity and kindness in error messages is a design decision.

01 — Real-world story

My mom's salt test is the best error message I know

Personal story — the kitchen, every time

Taste early. Correct while you still can

When my mom cooks curry for rice, there's one step she never skips — tasting the salt before the final stage. We all know how important salt is to a dish: too much or too little and the whole thing is off. And let me be honest — every time I cook, my mom ends up taking over the salt department entirely. It's an art.

Here's the connection to UX: when she tastes the curry mid-cook, she's running a check. If the salt is right — success, continue. If it's off — error detected, correct immediately. The dish still turns out great.

But imagine if you could only taste the curry after it's fully cooked, plated, and served. If the salt was wrong, you'd have to redo the entire dish. Frustrating, wasteful, and entirely avoidable.

The same error. One caught early with a simple correction. One caught at the end requiring full recovery. Timing is everything — in cooking and in UX.

"Catch errors early, correct them immediately, and make recovery feel effortless. That's the salt test — applied to every digital product."

— The lesson from mom's kitchen

02 — The three-part job

Recognize. Diagnose. Recover

A good error message doesn't just announce that something went wrong. It does three things — each one building on the last — to get the user back on track as quickly and confidently as possible.

Recognize

Make it unmistakably clear that something went wrong. The user should never have to guess whether an error occurred — the product should tell them directly and visibly.

Diagnose

Tell the user what went wrong and why — in plain, human language. Not "Error 403." Not "Something went wrong." Say what actually happened so they can understand it.

Recover

Offer a clear next step. Try again, choose an alternative, contact support — give the user a path forward. Don't leave them staring at an error with nowhere to go.

03 — Digital example

The difference one good error message makes

Failed payments are one of the most anxiety-inducing moments in any digital product. The user doesn't know what happened, whether their money was charged, or what to do next. This is exactly where the three-part framework earns its keep.

Bad error message

"Something went wrong. Try again later."

No recognition of what specifically failed. No diagnosis — the user has no idea if their card was charged. No recovery path — "try again later" gives them nothing to act on. The user is left anxious and stranded.

Good error message

"Payment failed due to a network issue. Your card was not charged."

Recognizes the failure clearly. Diagnoses the cause (network issue) and removes the biggest anxiety (card not charged). Offers two recovery paths.

Try Again Choose Another Method

Same failed payment. Left: the user has no idea what happened or what to do. Right: they know what went wrong, know their card is safe, and have two clear paths forward.

04 — Types of errors

Slips and mistakes need different responses

Not all errors are the same — and how a product responds should reflect the nature of the error. A slip and a mistake require different kinds of guidance to recover from.

Slip — right intention, wrong action

The action went wrong

Real-world

You reach for toothpaste on autopilot — but someone moved the shaving cream there. Your intention was right. The context changed.

In UX

Clicking "Reply All" instead of "Reply" because both buttons sit right next to each other. The recovery message should be immediate and offer a simple undo.

Mistake — wrong intention from the start

The understanding was wrong

Real-world

You have body pain and assume it's from the gym — but it's actually a fever. Your mental model was incorrect from the start.

In UX

A user thinks "Archive" means "Delete permanently" and archives an important file. The recovery message should explain what actually happened and offer a clear path to reverse it.

Slips need quick, frictionless recovery. Mistakes need clear explanation. In both cases, the product's job is to respond with clarity and kindness — not to lecture, not to blame, just to help.

05 — What to design for

A product that guides through errors builds trust

Show clear, human-readable error messages

Avoid technical jargon. Error codes and system language mean nothing to most users. Write as if you're talking to a person, not logging to a server.

Highlight exactly what went wrong and where

Don't make users hunt for the problem. Point to the field, the step, or the action that failed — clearly and specifically.

Offer guidance and recovery options

Every error message should end with a path forward. Try again, contact support, choose an alternative — give users something to do with the information.

Don't punish users for honest mistakes

Errors are human. The product's tone should be calm and helpful — never condescending, never alarming. Make fixing the error feel easy, not shameful.

06 — Closing thought

Don't let an error be the end of the journey

Errors are inevitable. Every user will encounter them at some point. What separates a trustworthy product from a frustrating one isn't the absence of errors — it's how the product responds when they happen.

A product that gently guides users out of mistakes — with clarity and kindness — builds trust and keeps users coming back. Make the error a quick detour, not a dead end.

The lesson from H9

Errors are inevitable. Confusion is not. When something breaks, your product's voice matters most — make it clear, human, and helpful.

Apply this to your next design

Find the three most common errors in your product. For each one, ask: does the message tell the user what happened, why it happened, and what to do next? If any of the three are missing, you've found your fix.

Up next

H10: The Best Manual Is No Manual. The final heuristic — help and documentation. Even when a product is designed well, sometimes users need support. How you provide it says as much about your product as the design itself.