The day we tested Gluuer with our moms
You can run all the QA in the world and still miss the question that matters most: does a normal person understand what you built?

There's a risky point in every software project where everything starts making perfect sense to the people building it. Of course that icon means upload, and naturally everybody knows what a "gated URL" is.
After clicking through the same flow four hundred times, your brain becomes almost useless at judging whether anything is actually obvious. You stop seeing the screen the way a newcomer does, and you start filling in gaps without noticing.
So we ran a very sophisticated usability study. We gave Gluuer to our moms.
There was no onboarding presentation and no strategy deck. Nobody who had spent months working on the product hovered nearby explaining things. We handed over a laptop, said "here, try this," and then did our best to keep quiet.
The first lesson showed up almost immediately
People outside the software world don't care about your terminology, and they care even less about how the product was built. Nobody is impressed that your backend is tidy or that a particular feature took three days of work. They look at the screen and ask one question: "What do I do?"
That's a brilliant question, because it's essentially the entire job of interface design. Every label, button and empty state exists to answer it. If a person has to ask it out loud, the screen hasn't done its job yet.
It also reminded us how much jargon creeps into a product without anyone deciding to put it there. Words like "gate" and "asset" feel natural after months of internal meetings, yet to everyone else they sound like a foreign language.
Files made sense quickly
The file flow clicked fast, largely because the mental model already exists. Everyone has attached a file to an email or uploaded photos somewhere. You pick the file and give it a name, and a link appears. That feels familiar even to someone who has never heard the phrase "lead magnet."
The real moment of understanding came a little later, when it sank in that the new link asks for an email before handing the file over. One of our testers looked at the preview, pointed at the email field and said, "So people put their email here, and then they get this?"
Exactly. That sentence is basically Gluuer in a nutshell.
Then came the questions we'd stopped asking ourselves
Once the basic idea landed, a new round of questions followed, and they were good ones. The first was about where the emails end up. They go into your contacts, which you can check from the dashboard whenever you like. Then someone wanted to know whether the person receives the file immediately. They do, as soon as they've confirmed their email address.
That led to the best question of the afternoon: "Why do they have to confirm it?" We explained that without it, people type fake addresses just to grab the download. There was a short pause, and then: "Oh. That makes sense."
That reaction is one of my favorite forms of product validation. Nobody said "wow," and nobody called it disruptive. A person with no stake in the product simply understood why something worked the way it did, and agreed with the reasoning.
Simple products are complicated to build
Here's something that sounds backward but holds true. Simple products often need far more explanation while you're building them than they do once they're finished.
We spent a ridiculous amount of time on questions most users should never have to consider. What happens to a public link when a file gets replaced? How should a Magnet behave if the account behind it changes plans? And what's the right way to handle the same email address arriving twice, or one person requesting several resources from the same creator?
Users shouldn't carry any of that around in their heads. Their thinking should stay close to "I have this useful thing and I want people to get it." Everything else is our problem to solve quietly in the background.
Our moms found problems too
This wasn't a magical session where everyone understood every pixel and we all went home patting ourselves on the back. There were pauses. Some labels that seemed perfectly clear to us sounded odd to someone else, and at one point somebody tapped an element we never expected anyone to touch.
That was the valuable part. Every time someone hesitated, we asked why, and the aim was never to defend the interface. We wanted to understand what caused the hesitation, because a hesitation is data. It's a very different mindset from demoing a product, where the instinct is to jump in and rescue the user before they get stuck.
A few small wording changes came straight out of those sessions. We also moved one step so that it shows up at the moment people actually need it, rather than a screen earlier.
The moment it worked
After a while, nobody needed help anymore. Our testers were uploading a file and sharing the link without glancing over at us for reassurance.
Someone who works nowhere near marketing or tech had created something that could collect a verified contact, entirely on their own. That was when we looked at each other and thought, okay, this might actually work.
Gluuer was never meant to be another tool for people who enjoy configuring tools. Its entire purpose is to remove configuration, so watching someone succeed without instructions told us more than any internal review could.
If you're building something, try it
You don't need a research budget to run this kind of test. Find someone who has never seen your product and has no reason to be polite about it, then give them one realistic goal. Resist the urge to explain anything. Write down every pause, and ask about it afterward rather than in the moment.
You'll probably learn more in twenty minutes than in a week of internal debate about button labels.
The mom test is staying
We'll keep doing the serious work, of course. Automated testing and security checks are part of how we build, and they aren't going anywhere.
The mom test is staying too, though. Software can pass every technical check you throw at it and still fail a very human one: can a normal person use this without feeling silly? That's the standard we want to hold ourselves to.
And if your mom can create a lead magnet in about ten seconds, you're probably onto something.
Posted by Holly Rogan on 15 September 2026
Already have the resource?
+ Create a magnet linkHost the file or gate the link and start collecting emails. Free to start.


