Form design for small teams

It comes up on almost every project, usually later than it should. Most advice about form design assumes a team that does not exist at your size. Here is the version that does not.

Consistency is the quiet half of design work: it rarely gets complimented, and its absence is noticed immediately. It is the sort of thing that looks like polish right up until it costs you an enquiry.

What to keep

Every field you remove increases completion. This is the sort of thing that compounds, quietly, in both directions. Doing this properly once is usually cheaper than doing it approximately three times.

What to drop

Process that exists to coordinate ten people is overhead when there are two of you. The reasoning matters more than the rule, because the rule has exceptions.

What good looks like

Explain why you need anything that feels personal. The cost of getting this wrong is rarely visible on the day it happens. It rarely shows up as a line item, which is exactly why it slips.

In practice

Design decisions are the ones clients feel most confident arguing about, which makes it worth separating taste from evidence early. Three things worth confirming about form design before you move on:

• Someone can say what the current setup is without going to look
• Labels above fields survive small screens better than placeholders — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Worth checking on your own setup before it becomes someone else's problem to fix.