On a healthcare intake form we redesigned, the original version asked for 28 fields on a single scrolling page before a user could even reach the appointment calendar. Completion rate was under 50%. We split it into a five-step flow, grouped by logical chunks (contact info, insurance, medical history, preferences, confirmation), and completion climbed to over 80% without removing a single required field — the perceived effort dropped even though the actual effort didn't change much.
Inline validation timing mattered more than we expected. Validating a field the instant a user starts typing feels punishing — an email field showing 'invalid' after the first two characters trains people to distrust the validation entirely. We moved validation to fire on blur, after the user finishes a field, and added a debounce so fast typers don't see flicker. That single timing change cut form-related support complaints noticeably on a client's signup flow.
We also stopped asking for information we didn't immediately need. A shipping form used to ask for a phone number up front 'in case we need it later' — we moved that field to only appear if the user selected a delivery method that actually required contact (same-day courier), and made it optional everywhere else. Removing unjustified fields consistently outperforms any amount of clever field styling.
Error states needed to point at the fix, not just the problem. 'Invalid phone number' tells a user something is wrong without telling them what to change; 'Phone number needs 10 digits, including area code' does. We rewrote error copy across every client form to include the expected format, and it reduced repeat submission errors on the same field, based on funnel analytics from two separate client projects.
Multi-step forms need visible progress, but the wrong kind of progress indicator backfires. A percentage-based bar that jumps unevenly between steps (20% to 80% because one step has more fields) reads as broken. We switched to step counts — 'Step 2 of 5' — which sets an honest expectation regardless of how much content sits inside each step.
