How one form field was blocking a small brand’s online sales
A checkout redesign for a handmade hat brand: the biggest blocker removed, required fields cut from 11 to 8, and every test participant able to complete their purchase.

4/4 test participants blocked before the redesign
11 → 8 required fields, about 18 seconds less to fill in (-28%)
4/4 completed the redesigned checkout
About LazyHat
LazyHat is a small business selling handmade hats. At the time of the project, most sales came through Instagram, with the online store as a secondary channel. The founder wanted the store to work harder: customers who reached checkout should be able to complete their purchase without friction.
Problem: people were interested, but didn’t buy on the website
In Baymard Institute’s research, 17% of shoppers have abandoned a checkout because it was too long or complicated. LazyHat’s story fits that pattern: interest in the hats was strong, but few customers completed a purchase on the website. The founder knew she was losing sales online, she just didn’t know where or why.
Challenge: fix it without analytics or direct site access
LazyHat had no analytics tools installed, so there was no historical data on where or why customers dropped off. As a team of two designers, with no direct access to the site and a three-week window, we relied on a stakeholder interview, a user survey and moderated usability testing to identify the problems directly. Every change also had to go through the founder.
The evidence had to come from users, not dashboards.
Research: the survey told us where to look, the sessions showed us what was happening
We started with a stakeholder interview and a competitive analysis, then surveyed 22 online shoppers about why they abandon a purchase:
59% would abandon if the process felt too long or complicated
54% named unclear instructions or labels as a top frustration
45% pointed to too many fields
In 4 moderated sessions on LazyHat’s live checkout, participants confirmed these issues and ran into others specific to this checkout:
4/4 participants were blocked by the mandatory tax code field
3/4 questioned why some required fields were needed
2/4 struggled to see or read key elements
The tax code field, placed right before payment, was the biggest blocker. Some required fields also felt unnecessary, and key elements were hard to read: a WCAG check confirmed the main button failed contrast requirements.

Solution: a shorter, clearer form that asks only for what the order needs
We focused on the data entry step, where friction was most concentrated. We moved from mid-fi wireframes to a hi-fi prototype, which the founder then implemented on the live site.
Removing the blocker
The tax code field wasn’t arbitrary: the founder’s accountant had advised including it for invoicing. In practice, it’s only needed when a customer asks for an invoice, yet the form required it from everyone. We removed it from checkout. Customers who need an invoice can contact the founder directly.
Asking for less
Every required field was reviewed against one question: does fulfilling a hat order actually depend on this? Email stayed required, since the order is confirmed there. The phone number became optional, and fields that weren’t needed were removed. Required fields went from 11 to 8.

Making the main action visible to everyone
With at least 2.2 billion people living with a vision impairment (WHO), the button that completes the purchase has to be readable by everyone. Ours fell short of the WCAG AA standard, so we delivered an accessibility report recommending a compliant colour.

Impact: every participant completed the new checkout
In the final usability test, all 4 participants completed the redesigned checkout. No one was blocked at the point that had stopped every participant before.
Without analytics, post-launch results couldn’t be measured. The next step would be tracking checkout completion rate, drop-off by step and time to complete.
