This modal appears early in the workflow, so clarity matters. The original wording felt heavy and uninviting, which made a simple task feel harder than it should be.
Before: modal with wordy instructions and an error that left users guessing.
After: modal with cleaner guidance and an error message that actually helps.
The instructions asked for too much attention, and the error message stopped users without showing them how to move forward.
Shorter text, clearer intent, and guidance that supports choosing a valid name.
AdminHQ is our internal tool for configuration and platform management. It had a “Need help?” link, but stakeholders worried it sounded like someone was standing by to chat. I explored clearer naming options that actually matched what users would find inside: documentation and product guides.
AdminHQ UI with the original “Need help?” link that stakeholders found misleading.
Image showing three rejected naming options: “Help center,” “Support articles,” and “Developer docs,” with notes explaining why each wasn’t a fit.
Final AdminHQ interface with new “Resource library” icon and tooltip replacing the original “Need help?” link.
The “Need help?” link in AdminHQ suggested live support, which didn’t match the documentation it led to. Stakeholders were concerned it set the wrong expectation and distracted from core workflow tasks.
Give users a gentler, more accurate way to access documentation. A small icon with a neutral “Resource library” tooltip kept things helpful without sounding like live support was on standby.
This empty state kicks off the entire AutoPay experience, so it needs to make sense at a glance. I tightened the language, aligned the message with the action, and gave users a clearer idea of what they can expect.
Before: Empty state with unclear wording and inconsistent instructions.
After: Revised empty state with clearer guidance and consistent language.
The original message sent mixed signals. It told users to “turn on” AutoPay while the CTA asked them to “set up” AutoPay. It also used vague phrasing like “this feature,” leaving users unsure about what AutoPay would actually show once it was configured.
Create a message that confidently tells users where they are and where they’re going. I aligned the language with the CTA and gave users a simple explanation of what they’ll see after setup. The result is clearer and easier to act on.