Tell people what’s wrong before they hit Submit
Check tricky form fields as people finish them, not after they submit, and don’t nag them mid-keystroke.
Nothing says “we don’t want your money” like a form that waits until you hit Submit, reloads, and only then reveals that your username is taken.
Luke Wroblewski tested this with usability firm Etre: 22 people, six versions of a registration form. Compared with checking everything on submit, the best inline version had a 22% higher success rate, 22% fewer errors, 31% higher satisfaction and 42% faster completion times. The details mattered. Validating a field after people finished it worked better than validating while they typed, which made some of them type one character, wait for the message, and repeat. Green checkmarks on easy fields like name confused people: correct according to whom? Inline feedback paid off most on hard fields, like choosing a username or a password with strict rules.
It was a small lab study from 2009, so treat it as a strong hint, not a law. Still, the playbook is simple: validate the hard fields when people leave them, skip the cheerleading on obvious ones, and never make anyone hunt for what went wrong.
The example
- Instead of
- “Click “Create account” → page reloads → “There were errors in your submission.””
- Try
- “Leave the username field → instantly: “maker_jo is taken. Try maker_jo_dev?””
Before you flush
Fill out your own signup form with a taken username and a weak password. Count how many steps it takes to learn what went wrong.