A form is a negotiation. Every field is you asking for something before you've given anything, and every one of them loses you people who would otherwise have said yes.
Rules that hold up
- Ask for what you'll act on this week. If nobody will read the answer, delete the field.
- One question per screen beats a wall of inputs on mobile — where most of your responses come from.
- Never ask for something you can look up. You don't need their company name if you have their work email.
- Say what happens next. 'We reply within a day' converts better than a bare Submit.
The one exception
Long forms are fine when the person has already decided — a job application, an onboarding questionnaire, a booking they're keen on. Length hurts at the top of the funnel, not the bottom.
Order the Questions to Build Momentum
Which fields you ask matters less than the order you ask them in. Open with something easy and self-evidently relevant — the thing the person came to give you — and leave the sensitive or effortful questions for the end. Once someone has typed their name and answered one simple question, they've quietly committed, and they'll finish fields they'd have abandoned had you led with them.
This is why asking for a phone number or a budget in the first slot kills forms. Put it last, after the person is already invested, and phrase it as optional if it truly is. A booking form that opens with 'what are you looking for?' and closes with 'best number to reach you' will outperform the same fields in reverse every time.
The same logic covers the 'how did you hear about us' curiosity questions. They're for you, not the buyer, so they go at the bottom where a half-committed person will still humour them — never at the top, where they read as a toll booth.
Make Optional Truly Optional — and Only Ask When It's Relevant
A required asterisk on a field the person can't easily answer is a wall, and they hit it at full speed. Before you mark anything required, ask whether a missing answer would actually stop you acting. If you'd proceed without it, it isn't required — it's a nice-to-have wearing a blocker's clothes.
Better still, don't show fields that don't apply yet. Conditional logic — reveal the 'which product?' dropdown only after someone picks 'I want to buy', show the address field only for physical orders — keeps the form looking short for everyone while still capturing the detail you need from the people it applies to. The person filling it in sees three questions, not the eleven that exist.
When you do gate a field behind 'required', say why in a word. 'Email (so we can send your receipt)' meets far less resistance than a bare mandatory box, because now the ask has a reason attached to it.
The Failures You Won't See on Your Own Laptop
Most form drop-off happens in places the maker never encounters, because you test on a big screen with fast fingers and your own details already autofilled. The person on a three-year-old phone on a train meets a different form: a dropdown with fifty options, a date picker that fights the thumb, a validation error that wipes everything they'd typed.
Fix the mobile reality and you recover responses you didn't know you were losing. Load your own form on a phone, on mobile data rather than wi-fi, and fill it in as a stranger would — no autofill, no patience. The friction you feel is the friction that's costing you finishes.
- Never blank the form on a validation error — highlight the one bad field and keep everything else they typed.
- Use the right keyboard: an email field should bring up the @ keyboard, a phone field the number pad.
- Replace a fifty-option dropdown with a type-to-search field or a shorter set of choices.
- Let the browser autofill name, email and address — don't split fields in ways that break it.