Simplifying online product registration for a global electronics brand
Client project · May - October 2025 · UX focus: flow simplification, cognitive load reduction
Product registration should be one of the easiest things a customer does after buying something. You bought it. You want your warranty. You fill in a form.
But for users of one of the world's largest electronics brands, it wasn't that simple. Reddit threads were full of complaints: forms that froze mid-way, model numbers that wouldn't register, purchase dates that got rejected for no clear reason. And most frustratingly:
"Even when registration looks successful, it sometimes doesn't show up under 'My Products'. I don't know if the registration was successful or not."
People weren't avoiding registration out of laziness. They were avoiding it because the process was confusing, unreliable, and offered no clear reassurance that it had actually worked. The result was a significant gap between products sold and products successfully registered, a problem that affected users, who lost access to warranty coverage, and the business, which lost valuable customer data.
And then the client's brief arrived with an added complication: the client wanted to collect even more information from users during registration.
This is the tension that defined the entire project: the client needed more data from users, at the exact moment when users were already abandoning the process because it asked for too much.
My job was to find a way to give the client everything they wanted, without making the experience feel any heavier than it already did.
We had no room for formal usability testing. So I did what made sense, I went to Reddit.
I used the help of AI to compile user-reported complaints from relevant communities, looking for patterns in where and why people were dropping off or getting frustrated. This wasn't a perfect research method, but it gave us something more valuable than assumptions: real users describing real problems in their own words, unprompted and unfiltered.
At the same time, we sent the client a set of questions to understand their goals, key concerns, and the most important data they wanted to capture. Mapping user frustrations against client requirements side by side made the design decisions much clearer and we could see exactly where they aligned and where they conflicted.
This was a team project. A colleague handled the component library in Figma. My focus was entirely on the UX: the flow, the logic, the sequencing of information.
Which steps to prioritise. What to simplify. What to defer. And crucially, how to make sure the client still received every piece of information they needed within a structure that felt lighter and more manageable to users.
Because our communication with the client went through an intermediary, I made a point of annotating every design decision directly in Figma and building presentations to explain our reasoning clearly. When you're not always in the room when decisions are being made, your documentation has to speak for you.
Five improvements were designed and delivered:
Email capture moved to step one, with registration benefits made visible immediately. This is giving users a reason to continue before asking anything of them.
The verify later option. Detailed personal and purchase information becomes optional at registration and can be completed later through their account, removing the biggest source of cognitive overload and drop-off.
A protection plan offer is introduced clearly at the final stage, with transparent communication that it's handled by a third party so users know exactly what they're signing up for.
The rigid model number dropdown is replaced with a searchable type-ahead field. Users type their model and get suggestions, with on-screen guidance showing where to find it on their product.
Email confirmation is made reliable with a print option added, so users always have a backup record of successful registration, regardless of what happens in their account.