Error Design: Turning Frustrating Moments into Helpful Experiences

Error Design: The UX Discipline Everyone Ignores

Most design effort goes into happy path experiences — successful logins, completed forms, loaded content. But errors happen constantly, and how a product handles them determines user trust and satisfaction as much as the successful path. Design Agency Group designs error states and edge cases as first-class design concerns.

Types of Error States

Form validation errors: The most common. Two approaches:

• Inline validation (real-time as user types) — catches errors early but can feel intrusive
• Submit-time validation — less friction during input, but forces re-work after submission

Best practice: real-time validation for format errors (email format, password requirements) and submit-time for data errors (email already exists).

System errors (500): The server failed. Users need to know: it's not their fault, and what they should do (try again, contact support, come back later).

Not found errors (404): Page doesn't exist. Don't just show a code. Acknowledge it, apologise, and provide useful links to get users back on track.

Empty states: When a section has no content (empty inbox, empty search results, new user with no data). Design these as opportunities — what should the user do to fill this space? A helpful CTA beats a sad empty container.

Permission errors: User doesn't have access. Distinguish between "not logged in" and "logged in but not authorised". Don't show a cryptic code — explain what they need and how to get it.

Error Message Writing

Good error messages are:

• Specific — "Email address is already in use" not "Invalid input"
• Actionable — Tell users what to do ("Try signing in or resetting your password")
• Human — Avoid technical jargon
• Appropriately toned — Serious for data loss risks, lighter for minor hiccups
• Not the user's fault (when it isn't) — "We couldn't connect to our servers" not "You're offline"

Optumio monitors website errors and uptime — ensuring error states are caught and resolved quickly, rather than becoming permanent user experiences.