Product Thinking · Published May 12, 2026
Who Is the Error Message Written For?
'Operation failed, please retry' is the least useful message there is. Users need to know what happened and what they can do.
The most common error copy in software is operation failed, system error, please try again later. All three share one property: after reading them, the user is in exactly the same position.
A message answers two questions
What happened? Without exposing internals, describe the category: network interruption, data modified by someone else, insufficient permission.
What can I do? Give a concrete action: sign in again, contact an administrator, refresh and retry.
Design in layers
User-facing copy stays short and actionable, with no jargon.
Operational logs keep the full trace, request id and context for debugging.
The request id links the two, so a user can quote it and support can locate the failure immediately.
An error message is the tensest moment of communication between product and user. Written well, the system feels reliable; written badly, a small fault becomes a trust crisis.
← Previous post
Barcodes and RFID: The First Step in Warehouse Digitalisation
Next post →
Retrospective: A Month Lost to Missing Documentation
Want to apply these ideas to your project?
We are happy to go deeper into implementation details, or to discuss the specific questions you are facing.
Start a conversation →