DEV Community

Cover image for UX Writing Challenge: Day 12
Johnny Santamaria
Johnny Santamaria

Posted on

UX Writing Challenge: Day 12

From:
DailyUXWriting

80% done with the challenge!!

Scenario: A user is creating an account. When they come to the step where they are asked to enter their name, they get an error message. A fraud detection software thinks their name is fake—but it’s wrong 5% of the time.

Challenge: Write an error message that prompts them to fix the error without shaming them for having a fake-sounding name.

Message: 45 characters max

--

Message: Please double-check your username

Why I chose this:

  1. Neutral tone: The message avoids making assumptions or accusations about the user's name, ensuring a respectful interaction.

  2. Actionable: It clearly prompts the user to take a specific action—checking their input—without introducing confusion.

  3. Concise: At 45 characters, it remains within the limit while effectively conveying the necessary information.

  4. Universal: The term “double-check” is understood across various demographics and doesn't alienate users with complex terminology.

  5. Polite and empathetic: The phrase acknowledges the user’s agency and avoids implying any fault or judgment about their name.

Conclusion

This error message balances clarity, politeness, and efficiency. It ensures users feel respected while addressing the issue, maintaining a positive user experience.

cover image credit

Sentry blog image

Identify what makes your TTFB high so you can fix it

In the past few years in the web dev world, we’ve seen a significant push towards rendering our websites on the server. Doing so is better for SEO and performs better on low-powered devices, but one thing we had to sacrifice is TTFB.

Read more

Top comments (0)

Cloudinary image

Video API: manage, encode, and optimize for any device, channel or network condition. Deliver branded video experiences in minutes and get deep engagement insights.

Learn more

👋 Kindness is contagious

Immerse yourself in a wealth of knowledge with this piece, supported by the inclusive DEV Community—every developer, no matter where they are in their journey, is invited to contribute to our collective wisdom.

A simple “thank you” goes a long way—express your gratitude below in the comments!

Gathering insights enriches our journey on DEV and fortifies our community ties. Did you find this article valuable? Taking a moment to thank the author can have a significant impact.

Okay