Technical writer and UX writer
⚠️
PROBLEM
Error messages in a new mobile application at Ephesoft did not follow a consistent or user-friendly format. Some messages were repeated across multiple conditions, leaving users confused as to how to resolve them.
💡
SOLUTION
I proposed to write new microcopy for error messages that would provide clear solutions and a seamless user experience.
💬
PROCESS
I requested a list from our Engineering team of all error messages implemented in the mobile application, and their associated triggers.
After reviewing the original messages, I drafted revised content for problematic messages in Google Docs. This was based on the following:
-
Best practices for registration and login
-
OWASP guidelines for authentication
-
Competitve research
With the new messaging, users easily understood what issue they were experiencing, and were provided the solution.
I reviewed this messaging with our Product and Engineering teams, and made minor changes based on preference and functional limitations.
Here are some examples of before and afters:
BEFORE
Username is invalid
Username is invalid
Invalid verification code
AFTER
Enter your email address in the format: name@example.com
If that email address is in our database, we will send you an email to reset your password.
The temporary password you entered does not match the code we sent, or it has expired. To request a new temporary password, contact support@email.com.
✔️
IMPLEMENTATION
The new error messages were launched.