In the previous article, we shared cognitive psychology and user behavior in real-time verification, so how to deal with it if it fails or the other way around? In this article, let’s take a look at the author’s summary.
1. It is too early to prompt
Have you ever encountered this kind of “dissuade” form experience? The page has just loaded, and before you can type half a word, a string of red error prompts pops up like a siren: This field is required! , please enter valid content! , format error!
This design allows users to receive error prompts before they even start operating, which is prone to psychological illusions and feelings of being questioned, which in turn attributes the problem to unreasonable system design, resulting in frustration, anxiety, and even resistance. For example, a bank account opening form displays a red error message for all required fields as soon as the page loads, resulting in a 38% above-the-fold exit rate and an average dwell time of less than 7 seconds.
The correct approach is that the initial state does not show any errors, only when the user clicks on the field or starts typing, triggers feedback based on the cadence of the action, and uses gently guided prompt copy.
2. Prompt delay lag
If the system does not cancel the error prompt in time after the user corrects the error according to the prompt, it will cause anxiety and confusion to the user, making the user wonder if they have misunderstood the rules or missed other issues. For example, in the registration process of an app, the red prompt does not disappear after the user modifies the email format, causing the user to repeatedly modify it, and the operation time is far higher than average.
At this time, the user’s inner drama is like this: “Didn’t I just change it according to what you said? Why is it wrong? What’s wrong with that? You have something to say!” “Did I understand it wrong?” Then I will delete it and lose again? “Or did I miss other rules?” ”
The system doesn’t say anything, but the question marks in the user’s mind are one after another. This is typical –Lag feedbackIssue.
How can product managers do a good job in B-end digitalization?
All walks of life have taken advantage of the ride-hail of digital transformation and achieved the rapid development of the industry. Since B-end products are products that provide services for enterprises, how should enterprises ride the digital ride?
View details >
You can imagine a scene where you finish writing a question on an exam and look at the teacher with anticipation, but the teacher frowns and stands next to you in silence for a long time. You ask her, “Did I write it right?” The teacher didn’t answer, just continued to frown. You instantly panic in your heart and begin to doubt life. If the system does not give clear feedback to the user, the user will fall into a similar “feedback vacuum zone” –It’s not that I don’t know how to do it, but I don’t know if it’s done rightThe anxiety at this time is more uncomfortable than making a mistake. And, it’s not a technical issue, it isTrust issues + psychological burden: If you don’t give confirmation, they don’t dare to continue; If you don’t clear the red cue, they think they have failed.
For example, in the registration process of an app, if the user enters an email address, if the format is wrong, it will prompt “incorrect email format”; Users add “@” and domain names according to the rules, which are obviously correct, but the red prompt is still unmoving. What’s even more strange is that the user repeatedly confirmed that there was no problem, so he had to tentatively click the “Submit” button – at this time the system suddenly let go: “Registration successful!” The user’s heart at that moment was like this: “Huh? I submitted it earlier…… I was just anxious for half a day? ”
Our background data also reflects anomalies: many users repeatedly modify the email field 2-3 times, and the operation time is far above average, indicating that they are not filling out the form, but guessing the riddle!
What is the good practice?
It’s very simple, to put it bluntly, three words:Say it in time!
- As soon as the user corrects the content, the error prompt is immediately canceled and a confirmation or reassuring reminder is given, such as: “✓ Correct email format”.
- If the background needs to verify (such as checking for plagiarism), you should also add the loading status to tell the user that it is checking…”.
- Don’t let the red letters continue to be scary after the change, and don’t let users think that “the system is dead” or “I was still wrong”.
3. The icon is too warning: red exclamation marks are proliferating
Some designers are really true in the matter of “paying attention to user feedback”It’s too hard——I am afraid that users will not see the prompt, and as a result, every small question must be matched with oneRed exclamation mark, and then bold, enlarge, add flashing, and with vibration animation…… Good guy, it was as if it was about to start the alarm, and the next second it felt like the page would sound the siren. As for it?
Not every little problem is worthy of being expressed in “horror language”. If all the prompts look the same: all big red letters, all exclamation mark warnings, and all animation special effects, the user’s brain will be fastEnter a state of prompt fatigue。 They think, “Are you reminding me, or do you think I’m going to blow up the form?” ”。 At this time, the user will start insteadIgnore these tips, because they have learned: “The page always scares me anyway, and that’s what is really wrong.” ”
Real problems VS small reminders, treat them differently
This is actuallyInformation hierarchy designquestion. The feedback system is like a signal light:Red light, yellow light, green light, must perform their duties, don’t let the intersection turn on all the red lights, no one dares to go. You have to ask yourself: what exactly is this tip?
Critical error(For example, the mobile phone number is in the wrong format, the password is too simple, and the ID card is invalid)
- Use red tips + clear descriptions of errors
- The user must be prevented from proceeding
Light reminder(For example, it is recommended to use Chinese and English for nicknames, the image size is slightly exceeded, and the upload progress is slow)
- Light hints, gray text, and icons can be used to assist
- It doesn’t have to be blocked, just a suggestion or warning
Successful confirmation(e.g. “Username available”, “Correct format”)
- Please use green text and tick icon to encourage users to continue
Just like the navigation voice can’t always shout in your ear “pay attention ahead, slow down, there is a car on the right”, say it when you should say it, and if you say too much, you will directly turn off the mute.
4. Submission is not allowed: “trapping the user” design
The last common form validation “pit” is called “Mandatory no-submission” mechanism。 That is, once the system finds that a field is not filled in correctly, it immediately turns the “Submit” button into a gray area, directlyflameout, no points, no movement, the whole page seems to be frozen. And the worst part – you don’t know what’s wrong! There are no prompts, no guidance, no annotations, just a grayed out button is placed there, as if silently telling you: “You are not worthy of continuing to operate.” ”
A well-known ticket purchase platform once had a serious verification experience overturned. Users fill in their ID card number, as long as one number is missing, the system willNot giving the next step a chance at all– The “Next” button turns gray directly. The problem is, on the pageThere are no error prompts, and there is no highlighting error field, so the user can only be confused in place.
As a result, many people began to guess:
- “Is the ID card format wrong?”
- “Did I lose too fast?”
- “Is there another bug on this website?”
After two minutes of struggle, no helpful guidance, and no click to submit, the user’s final choice is usually:Close the page and abandon the purchase.This combination of “gray out button + silent page” directly “trapped” the user in the verification logic, and the result is –The abandonment rate soared, user feedback is so bad.
Everyone has itThe desire for control and expectation of feedbackHow to change. If you don’t say anything and just close the road, I can only suspect that I have entered a dead end. At this time, the system does not feel like “help me avoid mistakes”, but says, “You are not qualified to pass my test.” In other words,It is a sense of humiliation, not a sense of guidance。
Ideally, the correct approach is to allow submissions with a pop-up for a second confirmation, or highlight specific error fields with a concise and clear prompt, or display the error profile directly above the button area to let users know what the problem is and how to fix it.
