It’s easy to design for the perfect path. You know, the happy path—when users do exactly what we expect, click where they should, and everything just works.
But real users aren’t perfect. They forget passwords. They mistype. They have poor signal. They get confused. And the products that really shine are the ones that support users when things go sideways.
Enter the UX of error states.
An error isn’t just a red message. It’s a moment of vulnerability—a fork in the road where you either lose trust or deepen it. A great error message:
-
Explains what went wrong in clear, human language
-
Offers a path to fix it—or avoids the error altogether
-
Preserves the user’s progress and data
-
Acknowledges your fault, not just theirs
-
Uses design (color, layout, icons) to reduce stress, not amplify it
Think about the difference between:
“Error: 422 – Unprocessable Entity”
vs.
“Hmm, looks like something went wrong on our end. Your info is still safe. Try again in a few seconds or [contact support].”
One triggers frustration. The other builds trust.
At UXpect, we believe designing for failure is just as important as designing for success. Because if you handle the hard moments well, users will remember you for all the right reasons.