Occam's Razor

Among competing hypotheses that predict equally well, the one with the fewest assumptions should be selected.

The scenario: registering for a free product webinar. Applied to UX, the razor means: analyze each element and remove as many as possible without compromising the function of the whole. Both forms below accomplish the same job — reserving a seat. One demands twelve answers first; the other demands three.

What's wrong here? Marketing wanted lead data, sales wanted firmographics, legal wanted checkboxes — and the attendee just wanted a seat. Twelve-plus fields (including a fax number) for a free webinar. Every field is a small toll booth, and most visitors turn around before the end of the road.
gridframe.io/webinar/scaling-dashboards

Reserve your seat

Live webinar · “Scaling Dashboards Without Scaling Headcount” · Sep 24, 16:00 EEST

14 fields to complete

🔍 What changed

  • 14 inputs → 3. Each removed field failed the razor's test: the form works equally well without it.
  • Salutation, middle name, fax, and address served no one — deleted outright.
  • Firmographics (company, size, industry) are enriched automatically from the email domain instead of being asked.
  • Sales questions moved to a post-registration follow-up, when the attendee is already committed.
  • Two opt-in checkboxes and a consent box collapsed into one plain-language sentence with a terms link.

💼 Explaining it to stakeholders

“Every field we ask before the ‘Register’ click taxes the exact people we ran this webinar to attract — industry studies consistently show that cutting registration forms from 10+ fields to 3–4 lifts conversion by 25% or more. We're not giving up the lead data: we get company details automatically from the email domain and ask the rest after registration, when people are invested. Shorter form, same intelligence, meaningfully more attendees.”