Why your field count and your default values decide more about revenue than any redesign ever will.
The short version: The form is the checkout counter. You've hidden it behind a door that sticks. One redundant field cost Expedia twelve million dollars a year. One changed default can double a decision rate — with zero media spend. Since June 2025 it's also a compliance question in Germany. The whole thing costs three to four weeks of design work, not a quarter. Anyone saying "no capacity right now" is really saying "we'd rather keep paying."
There's a line in almost every project plan that reads: build the form. One ticket. Maybe two person-days. Usually at the end of the sprint, usually assigned to whoever is cheapest, usually never tested.
And there's a place in almost every product where interest turns into money. The signup. The application. The checkout. The account opening.
Same place.
I've been doing this for over ten years — enterprise work, startups, internal tools, onboardings — and I've never seen a project where the form got as much attention as the homepage. Seven people will spend three weeks arguing about the hero section. Nobody argues about the field where half the users drop out.
Yet the homepage decides whether someone likes you. The form decides whether someone pays you.
This is written for the people who approve budgets. It has numbers, court rulings and sources. And one claim: form work isn't a design question, it's a revenue question. Push it to the end of the sprint and you're not moving a task, you're moving income.
1. Every Field Is a Question You Ask a Stranger
Picture someone walking into your shop. You want to sell. And before selling, you ask: first name, last name, salutation, company, second address line, phone number, fax number.
Fax. Still. I see it every year.
Nobody would do this in a shop. Almost everyone does it in a form — because a form doesn't look like a conversation, it looks like a database table. And database tables come from wherever internal wishes get collected: sales wants the phone number, marketing wants the industry, legal wants the checkbox, CRM wants it mandatory. What you end up with is a form that reflects the needs of eight departments and not a single customer.
That's expensive. Measurably.
Expedia. The most-cited example: the booking form had a "Company" field. Plenty of customers typed in the name of their bank — and then, on the line below, the bank's address instead of their own. Credit card address verification failed, the booking collapsed. Expedia deleted the field. The result, according to their then-VP of Analytics: roughly $12 million in additional annual profit. One field.
The $300 million button. Jared Spool describes a major retailer whose checkout opened with a wall: log in or register. New customers wanted to buy, not get married. The team replaced "Register" with "Continue" plus a note that no account was needed — everyone calls that guest checkout now, back then it was an affront to the CRM department. Purchases rose 45 percent, the first month brought in an extra $15 million, the first year $300 million. The same analysis found 45 percent of customers had registered multiple times, and that the system was fielding around 160,000 password requests a day. The original 2009 piece is still online.
The average. The Baymard Institute has been measuring checkouts for over a decade. Their benchmark: an average checkout presents around 23.5 form elements, of which roughly 15 are actual input fields — about eight would do. Baymard considers a 20 to 60 percent reduction achievable for most shops. Average cart abandonment has hovered around 70 percent for years, and a large share of that is fixable: Baymard puts the conversion upside from checkout usability alone at over 35 percent.
The public sector can do this too, by the way. The UK's Government Digital Service didn't digitise the Carer's Allowance claim — they took it apart. Result: 170 questions removed, nearly half the form. Completion rates afterwards ran above 80 percent, above 90 for returning users.
The point isn't that fewer fields look tidier. The point is that every field has its own drop-off. You've been paying for it for years — you just can't see it, because it doesn't sit in any cost centre. No controller notices money that never arrived.
2. Defaults: The Strongest Lever Nobody Budgets For
If cutting fields is the obvious optimisation, defaults are the invisible one.
A default is the answer your form gives when the user does nothing. And most users do nothing. That's not laziness, it's economics: someone filling in a form wants it over with. Whatever is already there gets read as "probably correct" and as "probably recommended."
The study behind this is a classic by now. Eric Johnson and Daniel Goldstein published work in Science in 2003 asking why organ donation consent rates across European countries differ by almost an order of magnitude — with similar cultures, similar infrastructure, similar religion. The difference wasn't conviction. The difference was the checkbox. In opt-out countries consent sits near 100 percent; in opt-in countries it lands in the low double digits. In their own online experiment, consent was around 82 percent under opt-out and around 42 percent under opt-in — identical question, identical people, different default. "Do Defaults Save Lives?", Science 302, 1338–1339.
Note the magnitude: one checkbox roughly doubled the decision. No copy test, no redesign, no campaign budget gets near that. Behavioural economists call it choice architecture. You call it "that's just how the developer set it."
Why it works is well understood:
- Effort. Every change costs a click and a decision. Both are more expensive than they look.
- Recommendation. People read a preset value as advice from the provider. "They probably know what's normal."
- Status quo. Taking something away feels worse than never having had it. That applies to a checkbox too.
So if your product has a default, you are making a decision on behalf of a substantial share of your users. The only question is whether you're doing it deliberately or whether it came with your framework.
Which is the sentence I say most often to project leads: You don't get to choose whether you set defaults. You only get to choose whether you design them.
3. Smart Defaults: The Hypothesis About Your Users
The term of art is smart defaults — preset values derived from data, context and device rather than from someone's gut. The emphasis is on smart. A default nobody derived isn't a smart default, it's a value from the documentation of a framework that has never met your customers.
Because a default is always a claim: this is what our typical user looks like. Fail to test the claim and you don't save work — you just move it. From your team to your customer.
A few examples from practice, all real, all seen more than once:
The country field. Alphabetically sorted, Afghanistan on top. If the vast majority of your customers are in one country — and in most projects I see, they are — then that majority scrolls past eighty countries on every order. Check your own numbers before you file this under trivia.
The salutation. In Germany this stopped being a matter of taste and became a legal one. The Frankfurt Higher Regional Court ruled in 2022 that a booking form forcing a choice between "Mr" and "Ms" discriminates against non-binary people (case 9 U 92/20); the Federal Court of Justice dismissed Deutsche Bahn's appeal in 2024. Summary at beck-aktuell. But the more honest question is whether you need the salutation at all. If it exists purely so a mail merge can write "Dear Mr", you've built a mandatory field with litigation risk in order to save yourself one line of template text.
The amount. For savings plans, donations and subscriptions, the preset amount is the single most consequential number on the page. Too low and you leave volume on the table. Too high and you lose the people who don't dare to correct it. That number should be derived from your existing data, not from a product manager's instinct.
The payment method. Usually preselected as the one with the lowest fees for you. Rarely measured for what it costs you in abandonment.
The newsletter checkbox. More on that shortly.
The second address line. Needed by one percent of your users. In the way of a hundred percent. Belongs behind a link — that's progressive disclosure, and it costs you precisely nothing.
And the field you think is a preset. Placeholders aren't defaults, but they get treated as such — and far too often they replace the label. The Nielsen Norman Group said this plainly back in 2014: placeholders in form fields do more harm than good. The moment someone types, the hint is gone. Anyone scrolling back to check their answers sees values without labels. For people with visual or attention impairments it's simply a barrier.
Designing for your audience means answering one concrete question: who is the majority, and what is right for the majority? Not: what's convenient for us. And definitely not: what was preselected when we bought the template.
That question is answerable. Existing data, five to eight user tests, a look at the support call log. No fundamental research, no study, no institute. One week of work. You spent longer than that discussing a logo last year.
4. Where the Default Ends and the Dark Pattern Begins
Short section, but a necessary one, or I'll be misread.
Defaults are powerful. Which is exactly why they're regulated.
In 2019 the Court of Justice of the European Union ruled in the Planet49 case that a pre-ticked box is not valid consent (C-673/17); the German Federal Court of Justice confirmed this for Germany in 2020 (I ZR 7/16). Summary at vzbv. Anyone still working with pre-ticked consent isn't optimising, they're collecting legal exposure.
The test I use is simple:
Who benefits from this default if the user doesn't notice it?
If the user benefits, it's good design. If only you benefit, it's a dark pattern — a design that works only as long as nobody is paying attention. The difference between "standard shipping preselected" and "travel insurance preselected" isn't a nuance. One is service, the other is fraud in corporate colours.
And the side effect your finance people will love: deceptive defaults produce cancellations, complaints and support calls. They pull revenue forward and push cost backward. That's not a business model, that's a bow wave with a quarter's delay.
5. Since June 2025 This Isn't a Nice-to-Have Anymore
If the revenue arguments don't land, there's now also a law.
Germany's Accessibility Strengthening Act (Barrierefreiheitsstärkungsgesetz, BFSG) came into force on 28 June 2025, implementing the European Accessibility Act. It covers, among other things, e-commerce services aimed at consumers: online shops, booking flows, contact forms, payment processes, apps. The benchmark is EN 301 549, which in turn points to WCAG 2.1 AA. Fines up to €100,000, plus competition-law warnings. Micro-enterprises are exempt for services.
And what's typically inaccessible about a form? Exactly the things this article is about: missing labels or labels disguised as placeholders, error messages with no connection to the field, required fields marked by colour alone, time limits, blocked autofill, focus orders that jump around.
Put differently: the form overhaul you should be doing for conversion reasons has, for a year now, also been the compliance task you have to do anyway. Two arguments, one budget line. That's rare. I wouldn't overthink it.
And no, a bought-in accessibility overlay is not a solution. It's an invoice with a calming function.
6. What I Actually Do in These Projects
So this doesn't read as principle-mongering, here's the process I run in form projects. It's unspectacular, and that's the point.
1. Field audit. Every field on the table, and one question per field: who needs this, what for, and what happens if it's missing? In my experience a third drops out immediately and another third moves behind a link or into a later step. The hard part isn't the analysis. It's the conversation with the department that ordered the field.
2. Data need versus data cost. Every piece of information you request has a price in abandonment and a second one in data protection obligations. A field that's just "nice for the CRM" is never free.
3. Derive smart defaults, don't guess them. Look at the distribution in your existing data. What do 80 percent choose? That becomes the preset — as long as it doesn't harm the user. Where the distribution is flat, there is no default, there's a deliberate choice. "Let's just take the first one" isn't derivation, that's rolling dice in a nicer typeface.
4. Errors as a design task. Messages at the field, in plain language, with a fix. Validate on leaving the field, not while typing. And never delete input. A form that punishes you doesn't get filled in twice.
5. Test with five people from the actual audience. Not colleagues. Colleagues know the vocabulary. That's precisely the problem.
6. Measure. Per-field drop-off, error frequency per field, time in field. Forms are one of the few design artefacts whose impact can be quantified cleanly. That's your best shot at defending design work internally.
Concretely, this came up for me in the VisualVest account opening, the digital investment offering in the Union Investment orbit. Opening an investment account is the hard case: regulatory weight, lots of mandatory information, identity verification, risk profiling — and still a flow at the end of which someone either invests money or doesn't. Every preset becomes a question of trust there, because a preset amount or a preselected risk profile isn't neutral, it reads as advice. If you set a default in that context, you'd better be able to justify it.
A second project — a digital future planner, so far unpublished — came down to the same question from the other direction: how much can a product decide on the user's behalf before help turns into paternalism?
The rest runs as detail work through nearly every project I do: signups, onboardings, applications, contact flows. Not spectacular. But it's where products are won or lost.
7. The Business Case That Gets This Approved
The most common response to good form work is: "we don't have capacity for that right now." So here's the calculation to put in front of your decision-makers.
Say 50,000 people start your form each year and 60 percent complete it. That's 30,000 completions. You improve completion by five percentage points to 65 — conservative, measured against the numbers above. That's 2,500 additional completions. At €80 contribution margin: €200,000.
On the other side: field audit, redesign, two rounds of testing, implementation support. Realistically three to four weeks of design work.
What you actually need to approve, if you want the line item spelled out:
- one to two days for the field audit, including the conversations with sales, legal and CRM
- access to your existing data — without it, defaults stay opinion
- two rounds of testing with five people each from the real audience, not colleagues
- implementation support, so the decisions don't evaporate into tickets
- one person with the authority to decide which field gets cut
That last point matters most. Form projects almost never fail on design. They fail because nobody is authorised to take a field away from a department.
And one cost block that gets forgotten: every abandonment that lands in your service centre costs a phone call. Every unclear error message produces tickets. Every duplicate account pollutes your CRM and gets expensively cleaned up in a migration project later. Bad forms aren't only a revenue problem. They're an operating cost problem with a long half-life.
Why You Can Take My Word for It
I'm Tobias Adam, a freelance UX designer in Hamburg, more than ten years in digital product development.
I learned the craft agency-side, including at Jung von Matt and deepblue networks — the place where ambition, enterprise reality and deadline all land on the table at once. I've worked for BMW, Audi, FIFA, Union Investment, Vodafone, OBI and Deutsche Messe, among others. Over 20 awards, including Webby, ADC and Cannes.
What interests me about forms is exactly what makes them useless for awards: they're the most honest part of a product. A homepage can claim you're user-centred. A form shows whether it's true.
Today I work freelance and together with HC Merkle as intro.team — two freelancers for the phase where an idea becomes a testable product: concept, UX, UI, prototype, user testing. Short cycles, senior staffing, no agency apparatus. And yes, it's about forms more often than average.
The Short Version for Your Next Sprint
- Count your fields. Cut every one nobody can name a purpose for. Today, not "in the next release."
- Don't ask for anything you can derive. City from postcode, card type from the number, salutation mostly not at all.
- Set defaults deliberately. They're the answer for the majority of your users, whether you like it or not.
- Make them smart defaults. Derived from data, not from meetings.
- Test every preset with the benefit question. Who does it help when nobody's looking?
- No placeholders instead of labels. Ever. Not even when the mockup looks tidier.
- Errors at the field, in plain language, with a way out. And never delete input.
- Allow autofill and use correct input types. An afternoon's work, immediately noticeable on mobile.
- Test with five real users before you ship. Five. Not fifty, not zero.
- Measure per field. Without numbers, every form discussion is a taste discussion — and those are won by whoever has the bigger title.
Forms aren't a detail. They're the checkout counter. And yours sticks.
Sources and Further Reading
- Johnson & Goldstein: Do Defaults Save Lives?, Science 302 (2003) – science.org
- Jared Spool: The $300 Million Button (2009) – articles.centercentre.com
- Baymard Institute: Checkout Optimization – Minimize Form Fields – baymard.com
- Baymard Institute: Cart Abandonment Rate Statistics – baymard.com
- Nielsen Norman Group: Placeholders in Form Fields Are Harmful – nngroup.com
- Government Digital Service: Simpler Carer's Allowance digital service now live – gds.blog.gov.uk
- GOV.UK Design System: form and question patterns – design-system.service.gov.uk
- CJEU C-673/17 "Planet49" and BGH I ZR 7/16 – vzbv.de
- OLG Frankfurt 9 U 92/20, BGH X ZR 71/22 on gender-neutral salutation – beck-aktuell.de
- Barrierefreiheitsstärkungsgesetz (BFSG), in force since 28 June 2025 – bfsg-gesetz.de
- Luke Wroblewski: Web Form Design – Filling in the Blanks (Rosenfeld Media)