A common experience refinement problem
Your error states are dead ends
The short answer: make every error an exit ramp. Here is how to recognise this problem in your funnel, why it happens, and how the best consumer apps design it away.
How to recognise it
- Sessions ending on error screens
- “Something went wrong” as the entire error vocabulary
- No retry, alternative or next step offered at failures
Why do error states lose users?
An error screen is the product at its worst moment, which is exactly when design effort matters most and is spent least.
“Something went wrong” answers none of the user's three questions: what happened, is my stuff okay, and what do I do now? A dead end with a sad icon is a dressed-up shrug.
Users do not remember products by their average screen. They remember the day it broke and what it did about it. Every unhandled failure spends trust that took months to earn.
How do you design useful errors? Explain, protect, offer the next move
Write every error to answer the three questions, in order. What happened, in plain words. What survived: “your draft is safe” is the sentence that matters most. What to do now: retry, an alternative path, or an honest “we're on it, check back in an hour”.
Design the common failures individually: offline, timeout, not found, payment declined each deserve their own useful screen, because each has a different useful answer.
Recover automatically where you can: retry silently once before announcing anything; queue the action for when connection returns; never make the user redo what the system can redo itself.
And keep tone proportional: calm and competent, never cute, at moments involving money or lost work. A pun on a failed payment reads as mockery.
The building blocks that solve it
- JTBD Copywriting: The three answers, in the user's language.
- Loading Feedback: Honesty about system state, before and during the failure.
Who does this well
Google Docs: The error state says the only thing that matters, your work is saved, and the anxiety never arrives.
Monzo: Failures name what happened and whether money moved: precision is the comfort.
Questions founders ask
Should error messages be funny?
Almost never at the moment of failure, and never near money or lost work.
Humour reads as the product not taking your problem seriously. Save the personality for the 404 page; give the payment error to your calmest writer.
What's the most important line in an error message?
The one that says what survived: your draft is safe, your money didn't move, nothing was deleted.
Users can absorb almost any failure once they know their things are intact. That sentence should come first, not last.