The Form
A structured request for information, where every field asked costs someone finishing.
The problem it solves
A product needs data it cannot infer. The person filling the form wants to be finished. Every question added serves the business and taxes the user, and the exchange rate is worse than teams assume.
Form length against completion, in the abstract
Start by cutting. For each field, ask who reads it and what decision changes because of the answer. Fields that exist because a department might want the data later are the ones that lose you completions. The shortest form that supports the next step is the correct form.
Layout rules that survive testing
- One column. Multi-column forms break the vertical scan and cause skipped fields.
- Labels above inputs, always visible. Placeholder-as-label disappears the moment someone types, which strands them mid-form.
- Group related fields under a heading, and keep each group to a handful of items.
- Size the input to the expected answer. A postcode field the width of a street address invites the wrong content.
- Mark optional fields rather than required ones, once the form is short enough that optional is the minority.
- Set the right input type and autocomplete attribute, so mobile keyboards and password managers do their job.
Write labels as the question a person would ask, not as the database column. And put help text where the confusion happens, under the field, rather than in a tooltip that requires a hover a touchscreen cannot produce.
Field copy that stalls people
- Name
- Address Line 2
- DOB
- Phone (optional) - we may contact you
- Company size
Field copy that gets answered
- Full name, as it appears on your card
- Apartment, suite, or floor (optional)
- Date of birth. We ask because the licence requires you to be over 18
- Mobile number (optional). Only used for delivery updates, never marketing
- How many people work at your company? Pick the nearest range
For long forms, split by topic rather than by count, show a step indicator with real step names, and save progress between steps. A person who abandons at step three of five should find step three waiting when they come back, not an empty step one.
Worked example
A hypothetical field cull
A signup form asks for company name, role, team size, and how the person heard about the product. None of the four gates account creation. Moving all four into the product, asked once the person has a reason to answer, shortens signup to email and password. The data does not disappear; it arrives later from people who are already invested, which usually makes it more honest as well.
When it fits
- The information genuinely cannot be inferred, defaulted, or asked for later.
- Each field has a named consumer who will act on the answer.
- The form can be completed in one sitting on the device people will actually use.
- Progress can be saved if the form runs longer than a couple of screens.
When it backfires
- Fields are collected speculatively, which trades completion rate for data nobody queries.
- Everything is asked up front when half of it could be asked after the person is committed.
- Labels use internal vocabulary, so people guess and guess wrong.
- The form resets on validation failure, which is the single fastest way to lose someone who was nearly done.
Products using it
Stripe Checkout
Asks for the minimum payment fields, detects card type from the number, and derives the address format from the country.
GOV.UK
Uses one question per page for complex services, with labels written as plain questions and help text under the field.
Typeform
Presents one question at a time with saved progress, trading page density for a lower sense of length.
The psychology under it
The takeaway
Delete fields before you style them, and ask for the rest once the person has a reason to answer.
Finished the teardown? Bank it and the day counts toward your run.