The takeaway: A good error message does three things: it says what happened in plain language, it avoids blaming the user, and it tells them what to do next. Rewrite your worst error messages with that formula, and put the message next to the thing that needs fixing.
Why error messages are worth an hour of your time
Users meet your product at its worst moments: the card that declines, the upload that fails, the field that rejects their input. Nielsen Norman Group places error recovery among the core quality components of a usable experience, and traces the principle back to Jakob Nielsen's usability heuristic "help users recognize, diagnose, and recover from errors." In their error-message guidelines, NN/g frames an error message as an interruption to the user's workflow - which means a badly written one doubles the cost of something already going wrong.
The good news for a small team: error copy is cheap to fix. You can rewrite your ten worst messages in an afternoon.
The three-part formula
NN/g's communication guidelines boil down to a repeatable structure:
- Say what happened, precisely. "An error occurred" tells the user nothing. "We could not charge your card" is specific. Avoid technical codes and jargon - NN/g notes that even the web's most common error, the 404 page, is a famous violator. Show codes only for diagnostic purposes.
- Offer constructive advice. Stating the problem is not enough; suggest a remedy. If a card fails, say what to try (another card, a different browser, contacting their bank). If an item is out of stock, say when it might return or offer a notification.
- Take a positive tone - never blame the user. NN/g advises against words like "invalid," "illegal," or "incorrect" that imply the user did something wrong. "That email address looks incomplete" beats "invalid email." Skip humor too: it can turn stale fast when someone hits the same error repeatedly.
A quick rewrite, as an exercise: "Error 403: unauthorized request" can become "You do not have access to this project. Ask the project owner to invite you, or switch to an account that has access." Same event, very different next step.
Put the message where the problem is
NN/g's visibility guidelines are about placement and timing as much as wording:
- Show the error next to its source. A message at the top of the page about a field halfway down forces the user to hunt. Highlight the field itself and put the message beside it.
- Use noticeable, redundant indicators. Bold, high-contrast, red text is conventional - but never rely on color alone, since a large share of people have some form of color-vision deficiency. Add an icon or explicit label.
- Match the design to the severity. A toast or inline note fits "good to know" situations; reserve modal dialogs for errors that genuinely block progress.
- Do not show errors prematurely. Flagging an empty field the moment someone tabs through it feels like being graded before answering. NN/g calls this a hostile pattern. Inline, real-time validation can work for error-prone inputs like passwords - but only once the user has actually tried.
Protect the user's effort
The worst error message is the one that does not exist - silence after a failed action leaves users guessing. Two further efficiency guidelines from NN/g are easy wins for a small product:
- Preserve the user's input. Let people edit what they entered instead of retyping everything. Losing a form's contents on error is one of the most punishing experiences a product can inflict.
- Reduce correction effort. If the system can guess the fix, offer it. "City and ZIP code do not match" is fine; "City and ZIP code do not match - did you mean Springfield?" is better.
Find your worst offenders
You do not need to audit every message at once. A practical sweep:
- List the errors you already log or see in support requests.
- Read each one aloud. If it would confuse a stranger, rewrite it with the three-part formula.
- If you want to watch real people hit these messages, the same testing method from our guide on how to run your first usability test works well here.
- For longer explanations, link out instead of cramming text into the message - our post on writing your startup's first help article covers that companion piece.
If your product is still finding its first users, every rough edge like this costs you the few people willing to try it. Getting your startup in front of early adopters on Maidensail is one way to keep new testers coming while you smooth things out.
The takeaway
Error messages are tiny pieces of writing with outsized impact. Say what happened, skip the blame, offer a next step, and place the message where the problem lives. Rewrite a handful today - your future support inbox will be quieter for it.
Your launch deserves users who stick around
Products that treat people well at their worst moments earn word of mouth. When you are ready for more of those users, launch your startup on Maidensail and get in front of founders and early adopters.
Source: Nielsen Norman Group - Error-Message Guidelines (Tim Neusesser and Evan Sunwall, 2023). Rewritten example above is an exercise, not a measured case study.

