How Much Friction Is Too Much in a Form?

The Question

A form can appear simple when someone designs it and feel completely different when someone has to fill it out.

From the business side, every question may have a reason. A sales team wants a phone number. Operations needs a ZIP code. Someone wants a budget range. Someone else wants the type of service, preferred date, project details, company size, or how the customer heard about the business.

Individually, none of those requests looks unreasonable.

Together, they become a task.

That is why counting fields is an incomplete way to evaluate form friction. Two forms with the same number of questions can demand very different amounts of attention, interpretation, typing, correction, and disclosure.

The research gives us a better framework for looking at that work.

What the Research Examined

Seckler and colleagues conducted a controlled eye-tracking experiment with 65 participants to evaluate the combined effect of 20 usability guidelines on interactive web forms. The researchers applied those guidelines to forms taken from real company websites and compared the improved versions with the originals. [1]

The improved forms were completed faster, required fewer submission attempts, generated fewer eye movements, and received higher satisfaction ratings. [1]

That is an important result, but it does not tell us that one particular guideline caused the improvement or that the redesigned forms generated more sales leads. The researchers tested the guidelines as a combined treatment and measured form usability, not downstream business conversion. [1]

That distinction makes the study more useful, not less. It tells us that the experience of completing the form can be improved even when the basic task still exists.

What the Research Found

Friction Is More Than Form Length

Length does matter in some contexts.

Galesic and Bosnjak experimentally varied the stated length of a web questionnaire—10, 20, or 30 minutes—and found that the longer expected duration reduced the number of people who started and completed it. They also found changes in response behavior as questions appeared later in the questionnaire: later answers were completed faster, open-ended responses became shorter, and responses became more uniform. [2]

That study involved web surveys, not sales-lead forms, so it should not be turned into a rule such as “a lead form must take less than ten minutes.” The contexts and motivations are different. [2]

What it does demonstrate is more general: the amount of work people expect and the amount of work already completed can influence whether and how they continue.

For a business form, that gives us a reason to question information requests that exist because they are convenient for the company rather than necessary for the customer to take the next step.

The Same Question Can Require Different Amounts of Work

Form friction also comes from the way a question is implemented.

Bargas-Avila and colleagues studied how web forms communicate formatting requirements. In an online experiment with 166 participants, giving users the formatting requirements in advance produced significantly fewer errors and fewer attempts than providing no visible guidance. [3]

A related study with 172 participants compared six ways of collecting dates. Different controls produced different tradeoffs: dropdown menus were better at avoiding format errors, while a single text field with the expected format shown alongside it or as disappearing guidance inside it produced faster completion and higher satisfaction. [4]

The underlying information being requested had not changed.

The interaction had.

That is an important distinction for conversion work because removing a field is only one way to reduce effort. Sometimes the better solution is to make the field easier to understand and complete.

Small Interface Decisions Can Create Avoidable Errors

Required fields provide another example.

Pauwels and colleagues experimentally compared two ways of indicating required fields in an online form. In their study of 24 participants, the alternative required-field treatment produced fewer errors, faster completion, and greater user satisfaction than the asterisk treatment they compared it with. [5]

The specific visual treatment in a 2009 experiment should not automatically become a modern design prescription. Interfaces, conventions, accessibility requirements, and user expectations evolve.

The durable lesson is narrower: even small signals around a form field can change how easily users complete the task.

That should make us cautious about looking at a form, counting eight fields, and concluding that the number eight is the problem.

What You Ask Matters Too

Not every field carries the same psychological cost.

Someone entering a first name is doing something different from someone disclosing household income, medical information, a project budget, or another piece of information they consider sensitive.

Joinson and colleagues studied self-disclosure in web-based forms and found that responses to sensitive questions changed when privacy concerns were made more salient. Their experiments used behavioral measures such as choosing “I prefer not to say” rather than relying only on participants saying whether they felt concerned about privacy. [6]

Again, this was research on web-based surveys rather than commercial lead forms. [6]

But it helps explain why treating every field as an identical unit of friction is misleading. Asking for one more piece of sensitive information may create more hesitation than asking for several low-effort details.

The customer is not counting boxes. They are evaluating what each box is asking them to do.

What This Does—and Doesn’t—Tell Us

The research supports the broader idea that unnecessary effort can make forms harder to complete. Better-designed forms can reduce completion time, errors, submission attempts, and visual effort, while longer expected tasks can reduce participation in web-survey settings. The implementation of individual fields can also materially affect how easily people complete them. [1] [2] [3] [4] [5] [6]

What the evidence does not give us is a universal conversion formula.

It does not establish that four fields always outperform eight. It does not prove that removing a phone number increases qualified leads. It does not tell us that every optional field should disappear or that asking more questions is inherently bad.

And it does not show that the form with the highest submission rate necessarily produces the best business outcome.

A longer form could reduce total submissions while helping a business collect information necessary to qualify, route, price, schedule, or serve an inquiry. Whether that tradeoff is worthwhile is a business question the usability studies do not answer.

The useful principle is more precise:

Every piece of effort you require should earn its place.

What This Means for Your Website

Start by separating information the customer needs to provide now from information the business would simply like to have now.

Those are not always the same thing.

If someone only needs to give a name, contact method, service type, and short description to begin a conversation, asking for ten additional details because they eventually help the sales process may be shifting internal work onto the customer too early.

That does not mean those questions should never be asked. It may mean they belong later.

That can help when the fields are unnecessary, but deletion should not be the only tool.

Look for questions that require interpretation. Look for unfamiliar terminology, unclear formatting requirements, dropdowns with difficult choices, required fields that do not appear required, instructions shown only after an error, and questions that make someone wonder why the business needs the information.

Research on format guidance and input controls shows that the same requested information can become easier or harder depending on how the interaction is designed. [3] [4]

Sometimes the field is not the friction.

The way the field works is.

The same can be true for household information, detailed property information, dates of birth, financial information, or anything else that requires a visitor to disclose more than basic contact information.

The relevant question is not simply whether the business can use the data.

It is whether the customer understands why providing it is appropriate at that point in the relationship.

Research on online self-disclosure gives us reason to expect privacy concerns and question sensitivity to affect response behavior. [6]

If a question is necessary, explain it when explanation would reduce uncertainty. If it is not necessary yet, consider moving it later.

Reducing friction until almost anyone can submit may increase raw form volume while creating more unqualified inquiries, additional follow-up work, worse routing, or scheduling problems. Adding questions indiscriminately can create the opposite problem: a form that serves the company's internal process but discourages people before a conversation ever begins.

That is why form optimization should connect user effort with lead quality and downstream outcomes.

A useful test is not merely:

Did more people submit?

It is:

Did the right people find it easier to complete the next step, and did the resulting inquiries become more useful to the business?

That is a conversion question rather than simply a form-design question.

Format restrictions should be understandable before submission where appropriate, error messages should identify what needs attention, and the customer should not have to reconstruct the entire form because one answer was invalid.

The research on form formatting is especially useful here. When formatting expectations were communicated in advance, participants made fewer errors and required fewer attempts. [3]

Error prevention is not merely polish.

Every avoidable correction adds another opportunity for the customer to decide the task is no longer worth finishing.

The Practical Takeaway

Do not begin a form review by asking how many fields it has.

Begin by asking what work each field requires.

Is the information actually necessary at this stage? Does the customer understand what is being requested? Is the input easy to provide on the device they are using? Are the formatting requirements clear? Does the question ask for information someone may hesitate to disclose? If they make a mistake, can they recover without fighting the interface?

Then connect those answers to the business outcome. Look at completion, abandonment, errors, lead quality, routing, bookings, sales, and the operational value of the information being collected.

A field should not stay simply because someone inside the business likes having the data.

And it should not disappear simply because a generic best-practice article says shorter forms convert better.

Keep the information that earns its place. Remove or redesign the friction that does not.

Where This Applies at CTG

Calls, Forms & Booking

We look at the full path from intent to contact: what information is requested, when it is requested, how easily someone can provide it, what happens when something goes wrong, and whether the completed inquiry gives the business what it actually needs.

Landing Pages

A high-intent landing page can lose momentum at the exact point where the visitor is ready to act. We evaluate whether the form matches the promise and context that brought someone to the page rather than treating the form as a separate component.

Conversion Optimization

Form changes create testable hypotheses. Depending on the business, the meaningful outcome may include submission rate, qualified-lead rate, booked appointments, sales progression, or a combination rather than raw form completions alone.

Website Redesigns

Redesigning the surrounding page without examining the lead-capture experience can leave one of the most consequential interactions untouched. Forms, booking flows, validation, mobile input behavior, and post-submission expectations should be treated as part of the experience.