Imagine a user landing on your company’s website. They browse the offer, learn about its benefits, look at your work, and start considering getting in touch. They’re interested. You don’t need to convince them from scratch anymore, because they’ve already taken several steps toward making a decision.
Finally, they click the “Request a quote” button.
And that’s when the problem begins...
The form asks for their first name, last name, phone number, email address, company name, job title, industry, number of employees, and several additional details. Some fields have no explanation, others are mandatory, and the user doesn’t know why the company needs all this information. After a moment’s hesitation, they close the page.
The company may conclude that the user wasn’t interested enough. But perhaps they were ready to get in touch, and the effort required to take that final step simply proved too great.
This is one of the less dramatic, yet significant, challenges in designing digital experiences. A form can look attractive and work perfectly from a technical standpoint, yet still make it harder to achieve a business goal.
A form isn’t just a set of fields. It’s a decision the user has to make
From a designer’s perspective, a form is an interface element. From a user’s perspective, it’s a specific task that requires time, attention, and sharing personal information.
Each additional field means another decision. Do I have to fill this in? Do I know what kind of answer is expected? Why does the company want to know this? What will happen to my data? Will someone call me right after I submit the form? Am I committing to a purchase?
Users don’t always consciously analyze these questions. Often, they simply feel that something is too complicated, unclear, or disproportionate to the benefit they’ll receive.
In cognitive psychology, an important concept is cognitive load: the effort required to process information and complete a task. An interface that demands too many decisions at once can make it harder to act, especially when the user is on a phone, in a hurry, or unsure whether they’re ready to get in touch.
This doesn’t mean every long form is bad. A loan application, product configurator, or medical form may require a lot of information. The problem arises when the number of fields, how they’re presented, and the effort required don’t match the user’s goal or their stage in the decision-making process.
1. Too many questions too early
One common mistake is trying to collect all the information during the very first interaction.
The company wants to build a complete profile of a potential customer right away. The sales team needs data to qualify the lead, marketing wants to segment audiences, and the CRM system needs a complete record. From a business perspective, these needs may be justified. But that doesn’t mean users should bear the full cost of meeting them right at the start.
Someone who only wants to ask about an approximate price may not be ready to provide a dozen detailed answers. Someone just considering working with you may not know their budget or timeline yet. Asking for answers the user doesn’t have or isn’t ready to provide puts them in an uncomfortable position.
A better solution is to identify what information is genuinely needed to take the first step. If an email address and a brief description of the user’s needs are enough, there’s no point in requiring a detailed company profile at this stage.
The remaining information can be collected later, when the user is more motivated to continue the process.
In some cases, a multi-step form can also work well. Instead of displaying a dozen fields at once, the system guides the user through a series of steps. However, this isn’t automatically a better solution. If the steps feel artificial and the user has to keep clicking “Next,” the experience can become even more frustrating.
First, simplify the process itself; only then decide how to divide it visually.
2. Every field should have a purpose
“Phone number.” “Company name.” “Job title.” “Number of employees.”
These are useful details for a company. For users, they may be yet more obstacles, especially when they don’t understand why the information is needed.
It’s worth remembering that sharing contact details isn’t a neutral act for everyone. Users may worry about unwanted calls, aggressive sales tactics, their information being shared with other organizations, or a flood of marketing messages later on.
In this situation, the field itself isn’t the only problem. The context in which the information is requested also matters.
If a phone number is needed so a consultant can call back and discuss the details of an inquiry, it’s worth explaining that briefly. If the company needs a business name to prepare an offer for the right customer segment, that can be communicated clearly too.
This isn’t about adding lengthy explanations to every field. It’s about removing uncertainty where it could prevent the user from taking action.
At the same time, don’t pretend that information is essential if it really isn’t. Designing a good experience isn’t about getting people to share information more effectively; it’s about creating a process that is justified and transparent.
3. The user doesn’t know what happens after they submit the form
The “Submit” button is technically unambiguous. Psychologically, that may not be enough.
What exactly does submitting the form mean? Will the inquiry reach the right department? Will someone respond within a day, a week, or perhaps not at all? Is the user starting a sales process or simply asking for information?
If the answers aren’t clear, users have to estimate the consequences themselves. For some, that uncertainty will be enough reason to put off the decision.
That’s why an effective form should clearly explain what happens next. This could be information about the approximate response time, how the company will get in touch, or what the next step will be. Of course, only if the company can actually deliver on that promise.
The wording on the button also matters. “Submit” describes a technical action. “Request a quote” or “Book a consultation” better describes the outcome, if that’s what the form is intended to achieve.
The message shouldn’t promise something the user won’t receive. Good microcopy reduces uncertainty instead of creating false expectations.
4. A form can punish users for making a simple mistake
The user fills in several fields, clicks the button, and gets a message: “An error occurred. Check the form.”
But which field is incorrect? What needs to be fixed? Have all the entered details been saved?
At a moment like this, a simple process turns into a puzzle. Users have to figure out the cause of the problem themselves and sometimes re-enter information they have already provided.
A good interface should help users fix errors, rather than merely inform them that errors exist.
In practice, this means, among other things:
-
identifying the specific field where the problem occurred;
-
explaining how to correct an invalid value;
-
preserving the other data after an unsuccessful submission attempt;
-
using clear messages instead of technical error codes;
-
validating data at the right time, without unnecessarily interrupting the user’s work.
Accessibility also matters. An error message should not be conveyed through color alone, as some people may not notice it. It should also be presented as clear text and support assistive technologies appropriately.
The goal is not to ensure that a form never accepts invalid data. The goal is to make sure an error does not leave users guessing about what to do next.
5. Required fields and consents must not be a puzzle
Asterisks next to fields, checkboxes, marketing consents, and personal data clauses all serve a purpose. Problems arise when users do not understand what they mean or cannot tell required information from optional information.
It is worth clearly marking required and optional fields. You should also distinguish between matters that serve different purposes: providing information about data processing, obtaining consent where required, and voluntarily signing up for marketing communications.
Consents should not be preselected in a way that makes it difficult to choose freely and knowingly. Nor should fulfilling a request be conditional on marketing consent when there is no appropriate basis for doing so.
In this area, UX design must work hand in hand with legal requirements. A simple interface must not mean concealing important information or taking control away from users.
Transparency can help build trust, but it does not replace a proper legal analysis of a specific process.
6. A form that works on a computer is not necessarily a good form on a phone
A form that looks short on a large screen may require a lot of scrolling on a smartphone, along with returning to previous fields and precisely tapping small elements.
This is compounded by issues with the onscreen keyboard, unsuitable field types, difficult date selection, or error messages that disappear.
Mobile design should not simply mean reducing the form’s width. You need to consider how users actually enter information.
It is worth using the appropriate keyboard type for email addresses and phone numbers, clear labels, sufficiently large interactive elements, and visible error messages. Autofill can make entering data easier if implemented correctly.
You should also avoid situations where opening the keyboard obscures the field currently being edited or the button to continue.
Ultimately, what matters is not whether the form fits on a phone screen, but whether users can fill it in comfortably and without mistakes.
7. Fewer fields do not always mean better results
Reducing the number of fields can be a good approach, but it should not be treated as a universal solution.
A contact form on a simple service website serves a different purpose than a financing application, technical configurator, or service request. In some processes, additional information is necessary to prepare a reliable response or avoid errors later on.
That is why it is worth distinguishing between three situations.
First: the data is essential to complete the action. It should be collected, but in a clear and convenient way.
Second: the data is useful but not necessary at the outset. You can consider collecting it at a later stage.
Third: the data is collected out of habit, without a clear purpose. In that case, you should question whether it belongs there.
It is also worth remembering that a multi-step form is not necessarily better than a single-step one, and a shorter process is not always clearer. The design should be based on users’ needs and the nature of the task, not on a trend toward a particular solution.
8. How can you tell whether a form is really losing you customers?
The biggest mistake would be to evaluate a form solely based on how it looks or on the opinions of the team that designed it.
If a form is meant to support sales, it is worth measuring how well it performs.
Form start and completion rates. These show what proportion of users begin the process and how many complete it. The figures alone do not explain why users abandon the form, but they can indicate the scale of the problem.
Drop-offs at each stage. In a multi-step form, you can check which step most often marks the end of user activity. If the problem occurs at a question about budget or phone number, it is worth reviewing why those fields are needed and the context in which they appear.
Validation errors. Frequent errors in a particular field may indicate an unclear label, a non-intuitive data format, or an inappropriate validation method.
Lead quality. More form submissions do not necessarily mean better business results. If simplifying the process increases the number of inquiries but significantly reduces their quality, you need to assess the change’s impact on the entire sales process.
Usability tests. Observing a few people completing a real task can reveal problems that are not apparent from statistics alone. It is worth checking whether users understand the questions, know which fields are required, and can anticipate what will happen when they submit the form.
A/B tests. If the traffic and experimental conditions allow, you can compare two versions of a form. It is best to change specific elements so you can interpret the results. An increase in conversions alone does not prove why one version worked better.
Measurements should take users’ privacy into account. Do not collect the contents entered in fields, personal data, or sensitive information in analytics tools unless it is necessary.
9. Practical pre-launch checklist
Before a form is launched or redesigned, it is worth asking a few specific questions:
-
Does every field have a clear purpose?
-
Do we really need all this information at this stage of the process?
-
Does the user understand why we are asking for specific information?
-
Is it clear which fields are required and which are optional?
-
Does the button text clearly state the result of the action?
-
Does the user know what will happen after submitting the form?
-
Do error messages identify the problem and explain how to resolve it?
-
Is the form easy to use on a phone?
-
Are information about personal data and consents presented transparently?
-
Are we measuring completions, drop-offs, errors, and the quality of the inquiries we receive?
-
Have we tested the form with real users?
Not every problem requires rebuilding the entire website. Sometimes all it takes is removing an unnecessary field, changing an unclear message, or explaining why a phone number is needed. In other cases, the source of the problem may be the entire customer service process, not the interface itself.
That’s why diagnosis should come before designing changes.
A form is part of the sales process, not just a technical add-on
Companies often invest in advertising, SEO, attractive photos, and detailed descriptions of their offerings to attract potential customers. Meanwhile, the final step, where users are asked to take a specific action, is sometimes treated as secondary.
This is a risky approach. A website can successfully attract attention while making it difficult to contact the company. Users won’t always report a problem. Most often, they’ll simply give up and look for an easier option.
A good form doesn’t have to be flashy. It should be clear, predictable, accessible, and proportionate to the purpose it serves. It should respect the user’s time, avoid asking for data without justification, and help them complete the process without unnecessary obstacles.
At Web24, we approach UX/UI design not only in terms of how an interface looks, but also in terms of the tasks users want to complete and the goals a company wants to achieve. Because sometimes improving the customer experience doesn’t start with a new homepage. It starts with a single form that finally stops getting in the way of making a decision.
So the most important question isn’t: how many fields should a form have? It’s: what needs to happen for users to take the next step without unnecessary worry or effort?
