First things first: I’m a product designer.
And yes, I’ve done over 300 user tests as a TESTEE, not an interviewer.
Why did I do this?
Simple truth: I just don’t have the budget or opportunities to run external user tests like mega companies do.
So I thought — if I can’t run that many tests, why not join them as a testee instead? That way, I could learn what other designers are doing, spot trends, and experience how different teams conduct their research.
I started this journey during COVID. Five years later, I’ve completed more than 300 user tests across four platforms. Looking back, I’ve gathered some valuable insights that I’d love to share with my fellow product/UX designers. Hope you will like it 😃
What platforms did I use?
- Usertesting.com — 172 tests
For designers/product owners:
This is probably the most well-known platform in the industry. It recently acquired UserZoom, so now it offers think-aloud tests, live interviews, and surveys (questionnaires, card sorting, etc.).
For testees:
There are plenty of tests available daily. The pay is decent — usually $10 USD per think-aloud test and $30 USD for a 30-minute live conversation. You’ll need to pass a short qualification interview to join the panel.
2. Usercrowd — 132 tests
For designers/product owners:
Known as Lyssna on the company side, this platform is perfect for limited budgets.
Here are the common test methods on this platform:
For testee:
Earnings range from $0.20–$1 per test, but each one takes significantly less time. You can withdraw once you reach $10, paid via PayPal.
3. Userlytics — 15 tests
This platform is user-friendly. I even participated in a test about redesigning Userlytics’ own website!
Compared to the other two, test invites are less frequent here. You’ll also need to pass a screener to qualify.
4. Userbrain — 6 tests
I have not done much for this platform yet. So far most of the tests were the think-aloud type. Here are some features of this platform.
As for testee, you’ll typically earn $5 per test, which is relatively low compared to other platforms.
What Did I Actually Learn from Doing 300 Tests?
- I got sneak peeks at unreleased features before they hit the market
One of the coolest parts? I got to test features from some big names — think FAANG, Canva, IKEA, etc. — before they launched.
During these tests, I wasn’t just clicking through screens. Sometimes, I got to have real chats with the designers and researchers behind the product. I got to understand the why behind their design decisions, and they got my fresh, unbiased thoughts as a user.
Even when it wasn’t a live session, I could still observe their prototypes and try to reverse-engineer their design thinking. It felt like a rare kind of design exchange — I got a glimpse into what the future might look like, and in some small way, I got to help shape it.
2. I learned so much from other designers
We usually work with PMs, devs, and maybe a copywriter or two. But testing like this meant I actually interacted with hundreds of other designers, and wow — it was eye-opening.
After a while, I could feel the difference between juniors and more seasoned designers just by how they ran a session.
A junior designer might just follow a script word-for-word. No matter what kind of user they’re talking to, the questions sound like a checklist. No follow-ups, no adapting on the fly.
But experienced designers? They treat the interview like a real convo. They’ll throw in a perfectly timed “Why do you say that?” and suddenly you’re pouring your thoughts out like you’re in therapy.
It made me reflect a lot on how I run sessions — and how I want users to feel when they’re talking to me.
To do and not to do when you are setting up a test
- Screening questions
✅ Set clear screening questions
Most tests I did had screening questions, and honestly, they’re super helpful. It’s the easiest way to make sure you’re getting the right people in. Don’t skip it.
✅ Double-check your settings
I’ve seen tests where it says “Select all that apply” but you can only choose one option. Little things like that completely throw users off — and they might quit halfway. Test your own test before launching, please.
❌ Don’t go overboard
If you’re asking more than 10 questions just to get in… good luck getting anyone through the door. Even legit testees might get screened out just because one answer doesn’t match your ideal version. Keep it simple and clear.
2. Figma prototype
✅ Password protect your prototype
If you’re using Figma for the test, put a password on it. Then change it once testing is over. I’ve seen so many prototypes still sitting in my “Recent Projects” — some even editable. 😬 Don’t risk your IP like that.
✅ Change the view to “Fit Width” before sharing
By default, Figma opens in “Actual Size,” which often makes everything look zoomed-in and messy. One tiny setting switch makes a huge difference in how smooth the test feels on the user end.
And here is how it looks like after changing to the“Fit Width” option.
✅ Help your users troubleshoot before they get stuck
Sometimes Figma won’t load on Chrome (yep, it happens). I’ve had to switch to Safari or Edge just to access a test. Most testees won’t bother. So if your link needs a backup plan, mention it upfront. Saves everyone frustration.
3. Background information
✅ You don’t always have to say what company it is upfront
A lot of people feel like they have to say “This is for XYZ company” at the beginning. But actually, keeping it vague at first can lead to way more honest feedback. If users don’t know who they’re testing for, they’re more likely to speak their mind.
True story:
Someone once asked me about AR/3D tools on mobile. I said, “I tried this kind of function in the IKEA’s furniture app… didn’t love it, to be honest.”
Turns out? They were from IKEA.
I was slightly mortified. But also kind of glad— because that was my unfiltered feedback. If I knew it was IKEA, I probably would’ve sugar-coated it. So yeah, sometimes not revealing upfront = better insights.
Disclamier:
I know a lot of screening tests are designed to filter out other designers, but I truly believe that if I’m both a designer and one of your legit target users, I can bring valuable insights from multiple perspectives.
Let me know if you found this helpful!
Is there anything else you’d like to know from my experience? Drop a comment and let me know!
I am Dana, thank you so much for reading. I will see you next time.
I Joined 300 User Tests as a Testee— Trends, Mistakes, and Insights You Can’t Google was originally published in UX Planet on Medium, where people are continuing the conversation by highlighting and responding to this story.