layman/terms
When things break

Error message

air · er mess · ij

In shortA message an app shows when something goes wrong, ideally saying what happened and what to do next.

A warning light on your dashboard doesn't fix anything. But it tells you something needs attention. It even hints at what.

A light comes on in your car: a little oil can, or an engine shape. It doesn’t fix the problem. It tells you something needs attention. It even hints at where to look.

An error message is that warning light. It’s what an app shows when something has gone wrong. A good one says what happened and what you can do about it.

Good and bad errors

Reading one

Even a confusing message often has a useful clue: a short code, a file name or one plain word like “permission” or “not found”. Searching the exact words online often finds others who had the same problem.

What it isn’t

It isn’t always your fault. Many errors come from the app or the website, not from anything you did.

Where the comparison breaks down

A dashboard has a handful of agreed symbols. Software can show endless different messages, written by different people, with no standard at all.

How the words fit together

A bug often triggers an error message. Websites use status codes like 404. Developers look in the log for the full story.

Pro tip

When you ask for help, copy the exact wording of the error or take a screenshot. “It says there's an error” is much harder to help with.

When you'll hear it

“What does the error say?” Tell me the exact words of the message, so I can work out what went wrong.

“It just shows a generic error.” The message doesn't say anything useful, like “Something went wrong”.

“Check the error code.” Look for the short number or label in the message, which points to the cause.

Say it in a meeting

“Do our error messages tell customers what to do next, or just that something failed?”