Having to enter the same information multiple times has usability costs

darah16204

Discussions about forcing users to enter their email address twice are primarily concerned with user experience and preventing incorrect information from being stored in the database. There are various articles on this topic , so I will not discuss the pros and cons here. Instead, I'd like to use eye tracking to support the hypothesis that asking users to enter their email address twice hurts the user experience. Many forms also suffer from this problem by not only asking for your email address, but also asking for your phone number multiple times (sometimes up to three times). Is this information really necessary? Below is a table summarizing the average length of all fixations and the average number of fixations in a user session when entering personal information. This data is not conclusive, but the general trend is that the simpler the input fields (email address confirmation + phone number), the fewer fixations it takes to complete the input, and the fewer fixations there are. The time will also be shorter. This supports the hypothesis that requiring these items to be entered is leading to friction in the user experience.

Practical advice : Don't ask users to confirm their email address or enter their phone number multiple times unless you have a good reason to do so. 5. Develop the UI to minimize the cognitive load on the user Looking at the forms asking for employment details, there was a big difference between the best Belgium Phone Number Data performing form (Halifax) and the worst performing form (Santander). Why was there such a difference? At first glance, each form looks similar. Image comment: Field to enter Halifax employment details Image comment: Field to enter Santander employment details The most obvious difference is that Santander's form asks for more information, such as the employer's address. This is additional information and requires more concentration than the short form.




However, this difference is not the whole story. There are two other factors as well. First, there is an item regarding "Job Title". At first glance, it appears to be a free text box where you can input anything you want. However, this is not the case. If a response is submitted that doesn't match the list maintained on the backend, a red asterisk will be displayed (and as mentioned above, it will be displayed when the form is submitted, rather than inline) . The problem is compounded by the lack of guidance on what is wrong. In the above example, the answer "teacher" is accepted, but it is not clear. The only way to get help is to click on the question mark, but the guidance is still vague. Looking at the eye-tracking data, we can see that fixations are clustered around this field. In other words, it can be said that effort is required to recognize it. Halifax is taking a different approach.