Why Users Abandon Forms Halfway (and How to Stop It)
Form abandonment has less to do with 'impatient users' than with how many fields you ask for, the order of your questions, and where you show errors.
When a form gets 100 visits and 23 responses, the problem usually isn't "impatient users." There are three specific things you can measure and fix.
1. Every extra field has a cost, but not the same cost
Adding fields lowers your completion rate, but the drop isn't uniform. A field the user can answer from memory (name, mobile number) is almost free. A field they have to go and look up (national ID number, bank account number, employee ID) is several times more expensive, because the user has to leave the form.
A practical rule: any field that forces the user to leave the page should either be removed or moved to the end of the form. Someone who has already filled in nine fields is far more likely to come back for the tenth than to start over from scratch.
Optional fields cost something too
A common misconception: "We'll make it optional so nobody is bothered." But the user doesn't know a field is optional until they read it, and reading takes time. If you don't actually use a piece of data, delete the field; don't make it optional.
2. Question order affects completion
Easy, low-stakes questions first; sensitive questions last. Someone who has already typed their name and department has now "invested" and is more likely to answer the salary question or offer a critical opinion too. The reverse is a disaster: if the first question on the form is "What is your monthly salary?", a large share of people close the tab right there.
3. Where you show errors
The worst case: the user fills in the whole form, clicks "Submit," and the page comes back with five red errors. Wherever possible, errors should appear the moment the user leaves the field, not at submission.
The second important point: an error message should say what is correct, not just that something is wrong. "Invalid national ID" is of little help; "The national ID must be 10 digits" gets the user to the answer.
The numbers to watch
In Porsino's reports, two numbers are meaningful side by side:
| Number | What it tells you |
|---|---|
| Completion rate | What percentage of the people who started made it to the end |
| Average completion time | If it's much higher than your estimate, something in the form is causing friction |
If the completion rate is below 50% and completion time is also high, the problem is the length of the form. If the rate is low but the time is short, users are probably giving up on the very first page, which means the problem is in the opening questions or in not explaining "what this form is for."
The one change that usually has the biggest effect
Split the form into multiple pages and add a progress bar. The same 12 questions feel far less daunting as three pages of four, and more importantly, if someone abandons on page three, you still have their answers from the first two pages.