How to do user testing at this stage is about one question: do people actually want this?
Not ‘can they use it’ – that comes later. This is demand validation. You’re testing the idea, the concept, the value proposition – before you spend engineering time building it.
This guide covers how to run user testing for demand and concept validation: how to frame what you’re testing, who to test with, what questions reveal genuine interest vs. polite agreement, and how to read the signals correctly.
| Not sure which guide you need? This article is about pre-build demand testing – figuring out whether people actually want what you’re planning to build, before you invest in building it. If your product already exists and you want to evaluate whether people can use it – finding friction, measuring task completion, identifying where they get stuck – that’s a different type of testing. See our guide to how to test user experience. |
TL;DR
- Don’t just “test.” Have a goal so you aren’t just watching strangers click on things.
- Five users are often enough to spot most issues. After that, you start seeing the same problems repeat.
- Keep your hands off. The moment you step in, the test stops being real.
How to Do User Testing: The Process
The user testing process involves 5 dedicated phases:
- Phase 1: The Strategy
- Phase 2: The Participants
- Phase 3: The Script & Scenarios
- Phase 4: Facilitation & Moderation
- Phase 5: Synthesis & Action
Phase 1: The Strategy
Before you ask people to try your app, slow down and make a plan. Jumping into a test without a clear goal just creates noise. You end up collecting random feedback that does not help you move forward.
Setting Objectives: What are you Actually Hunting for?
You aren’t just testing the site. You are looking for friction. Are you trying to see if people can actually find the checkout button?
Start with the “Big Why.” Identify the three most important actions a user takes.
Identifying Top Tasks (The 80/20 of user behavior)
Most users only use 20% of your features 80% of the time. Don’t waste time testing the terms and conditions page. Test the login flow, the search bar and the primary call-to-action. These are the lifeblood of your product.
The Methods: Moderated, Remote or Guerrilla?
In 2026, you have options.
- Moderated: You sit there (virtually or in person) and watch. Best for complex stuff.
- Remote/Unmoderated: They do it at home while wearing pajamas. This is great for getting honest, “real-world” results.
- Guerrilla: You take your laptop to a coffee shop and bribe a stranger with a latte to try your app. It’s fast, cheap and surprisingly effective.
Phase 2: The Participants
If you test your app with your mom, she will tell you it’s “wonderful, dear.” This is useless. You need people who will tell you your baby is ugly professionally, of course.
Recruitment: Finding Your “Real” Users
We know that the right feedback from the wrong person is still wrong feedback. If you are building a tool for brain surgeons, don’t test it with a middle-schooler unless that kid is a prodigy (actually, even that isnt 100% the slamdunk you think it is).
The “Magic 5” Rule (and when to break it)
The legendary Jakob Nielsen discovered that you only need 5 users to uncover about 85% of your usability issues. Why? Because after the fifth person, you start seeing the same mistakes over and over. Unless you have a massive budget and a lot of free time, stop at five.
The Screener Trap: How to Spot Professional Liars
There are people out there who make a living doing user tests. They are professional testers. They will lie and say they own a private jet just to qualify for your $50 study.
- The Trap: Ask a dummy question. Do you use the software ‘XylophoneConnect’ for your daily accounting? (XylophoneConnect doesn’t exist). If they say yes, show them the door.
B2B vs. B2C Testing: The Hidden Nuances
Testing a game for kids? You need high energy and short sessions. Testing a tax software for accountants? You need a quiet room and a high tolerance for talk about spreadsheets.
Phase 3: Synthesis & Action
The UX Debt Framework: Selling the Fix to the CEO
Fixing a problem after release can cost 100 times more than fixing it during the design phase. When you talk to your CEO, don’t talk about user delight. Talk about how fixing this button will save $50,000 in support calls next month. That is a language they speak fluently.
The “Cheating” Way: How Articos Automates Your Suffering
If you just read the last five phases and thought, “I have to find five strangers, write a script, watch hours of video and then fight my boss? I have a life,” then welcome to the future. Traditional user testing is like hand-washing your laundry in a river, it works but your back is going to hurt. Articos is the industrial-strength washing machine.
Instead of waiting weeks to find a “real human” who isn’t a professional liar, Articos uses AI-powered personas to simulate your audience. You give it your landing page or your brief and within 30 minutes, it runs the tests for you. It’s like having a team of 500 robot users who never get tired, never lie on screeners and don’t require you to buy them coffee.
Why Articos is the “Easy Button” for Beginners:
- Instant Gratification: Turn a six-week research cycle into a 30-minute coffee break.
- Zero Recruitment Drama: No more hunting for “brain surgeons who like gardening.” Articos already has the AI personas ready to go.
- No “Think Aloud” Awkwardness: The AI tells you exactly why a design fails without you having to sit in a dark room observing a stranger’s sighs.
Conclusion: This is How to Do User Testing Right
User testing isn’t about proving you’re right; it’s about finding out where you’re wrong before your customers do. 88% of users will never come back to your site after a single bad experience.
We believe that great design is just a series of guesses until a user touches it. So, go find five people, buy them some coffee and watch them break your product. It’s the most painful, expensive and rewarding thing you’ll ever do.
Testing an idea before you build? Articos lets you run concept validation with synthetic users in under 30 minutes – no prototype needed.
FAQs on How to Do User Testing
Five is the sweet spot. It helps you find about 85% of your biggest usability problems without wasting your entire budget on redundant feedback.
Don’t ask questions; give tasks. Instead of “Do you like the search bar?” say “Find a pair of blue socks for under $10.”
Not quite. User testing checks if people actually want the product (market fit), while usability testing checks if they can actually use it (functionality).
User testing is the “Big Picture” (Do they need this?), while usability testing is the “Nitty Gritty” (Can they click the button?).
