90s kids didn’t have error messages.

When a game cartridge didn’t work, there was no troubleshooting guide, no loading spinner, and no helpful system notification.

There was just a ritual:

Take it out. Blow into it. Put it back. Try again.

Somehow, we knew exactly what to do.

That simple childhood experience reveals an important UX principle: error recovery.

Good UX doesn’t pretend things won’t fail. It prepares users for failure and gives them a clear path forward.

When something goes wrong, users should be able to understand:

• What happened?
• What can I do next?
• Can I try again?
• Will I lose my progress?

The difference can be as simple as replacing:

“Something went wrong.”

with:

“We couldn’t upload your file.”[Try again]Your previous changes are saved.

The goal isn’t simply to explain the error.

The goal is to help the user recover.

So the next time you review an error state, ask yourself:

If my interface stopped working right now, would the user know what to do?

If the answer is no, your error state needs work.

Maybe 90s kids didn’t know the term error recovery.

They just knew:

“Try again.”

And honestly, that might be a UX lesson worth keeping.

UX Crumbs: Learn UX through small, practical steps that help you build real design skills, one crumb at a time.

Ux Crumbs Beta Version is live : https://get.uxcrumbs.app/