The best error message is the one that never shows up
How to write a great error message
Thomas Fuchs
2.2K25

YAS. A clear illustration of an instance where a good content decision is a good design decision. Leaving a content person out of the early/middle stages of development opens the door to awful error messages (and worse).

Too often the conversation starts with “give us content for this error message,” instead of “here’s a problem we anticipate, how can content help?”