A short form is not automatically better, and a long form is not automatically better qualified. The useful question is what each answer allows the business to do. If nobody uses a field after submission, the visitor may be paying an effort cost for no practical benefit.
Review the form with the person responsible for receiving and responding to enquiries. Their workflow should influence the design.
Separate contact details from qualification
Contact information enables a response. Qualification information helps determine whether and how the business can help. Keep those purposes distinct. A name and email address may be enough to begin a conversation, while a service-area question may be essential for a business that cannot deliver everywhere.
Avoid collecting sensitive information through a general enquiry form. If a later stage genuinely requires it, establish an appropriate process and explain why it is needed.
Ask whether the answer changes a decision
For each field, complete this sentence: “We ask this because the answer changes…” Useful endings include the team that receives the enquiry, whether the location is supported or what preparation is needed for the first conversation.
Less useful endings include “we might want it someday” or “the old form had it.” Move those fields to a later stage or remove them. Data collection should have a clear purpose, not grow through habit.
Make difficult answers easier
Not every buyer knows the right service name or project budget. Provide understandable choices and a way to indicate uncertainty when appropriate. A person who needs guidance should not have to invent expertise to contact the company.
Use examples for open-ended questions. “What are you trying to improve?” followed by a short, neutral example can be more useful than an empty “Message” box. Do not make the example so specific that it steers every enquiry toward the same answer.
Design labels and errors as part of the conversation
W3C's form guidance explains the role of labels associated with their controls. Placeholder text alone can disappear once typing starts and leave the person unsure what a field means. Keep required and optional status clear.
When an error occurs, identify the affected field and how to fix it. Preserve information already entered. On a phone, check that the keyboard does not hide the next action and that the correct input type is used where supported.
Evaluate the business outcome
If a form becomes shorter, watch both submission volume and the quality of resulting conversations. If an extra question is added, check whether it improves routing enough to justify the additional effort. A higher completion rate is useful only in the context of the business goal.
Keep a field inventory with the owner, purpose and next action for each answer. Review it when the service or sales process changes. The best form is not the one with the fewest boxes; it is the one that creates a clear, appropriate next step with no unnecessary work.
EBJ FIELD NOTES / FORM FRICTION
| 01 Essential | 02 Useful later | 03 Unnecessary |
For every field, identify the decision its answer supports—or remove it from the first step.
Put it to work
For every field, identify the decision its answer supports—or remove it from the first step.
Explore EBJ’s funnel and conversion services, or tell us what your business is trying to improve.