Form Design
Form design structures questions, controls, guidance, and actions so people can provide information accurately and efficiently.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/form-design/
01What it means
Form design is the practice of turning an information or transaction requirement into a coherent sequence of labeled controls, groups, instructions, and submission actions. It covers the form's overall structure and interaction, while form validation specifically checks and helps correct entered values.[1][2]
02Why it matters
Forms often sit at the point where user intent becomes product data or a consequential transaction. Clear structure reduces interpretation effort, input errors, abandonment, and inaccessible workarounds while improving the quality of collected data.
03When to use it
Use a form when a product must collect, edit, or confirm structured information. Remove questions the product does not need, prefill known data carefully, and prefer direct actions or progressive disclosure when a form would impose unnecessary work.
04How it works
- Define the user outcome and justify every piece of information requested.
- Order questions according to the user's mental model and group related controls with clear headings.
- Choose controls that match the answer shape, expected number of options, and input context.
- Provide persistent labels, concise guidance, sensible defaults, and clear required or optional status.
- Design submission, validation, recovery, review, and confirmation as one continuous flow.
- Test completion with representative users, devices, keyboards, and assistive technologies.
05A practical example
An insurance team replaces a single dense claim form with short sections ordered around the incident, evidence, and contact details. It removes questions already known from the account and lets users save progress, reducing incomplete claims without weakening required checks.
06Where it breaks
A well-designed form cannot make an unnecessary request valuable or repair unclear policy. Long or sensitive forms still create trust and completion risks, and splitting a form into steps can hide scope or increase navigation effort.
Common mistakes
- Collecting information because it might be useful rather than because it serves a defined need.
- Organizing fields around a database schema instead of the user's task and vocabulary.
- Using placeholder text as the only label or instruction.
- Treating validation and confirmation as implementation details added after the form is designed.