Usability Testing on Zero Budget

The good news: you don’t need a lab, a research team or a recruiting agency to learn what’s broken. A handful of people, a prototype and an hour of your time will reveal most of the biggest problems. Usability expert Jakob Nielsen famously argued that testing with just five users uncovers the majority of usability issues, and that small, repeated rounds beat one big expensive study.

Here’s how to run useful usability tests with no budget and no dedicated researchers.

Step 1: Plan a small, focused test

A good test starts with one question, not "let’s see what people think."

• Pick one goal. "Can new users add their first item to a collection without help?" is testable. "Is the app good?" is not.
• Write three to five tasks. Realistic scenarios, not instructions. Say "You just found an old card in a drawer. Find out what it’s worth," not "Tap the scan button."
• Decide what success looks like. Task completed or not, time taken, where people hesitated, what they said.
• Choose what to test. A clickable Figma prototype works perfectly. So does the live product, a competitor’s app or even paper sketches at the very early stage.
• Write a short script. Intro, warm-up questions, tasks, wrap-up questions. It keeps every session consistent, so results are comparable.
• Keep each session to 30 to 45 minutes. Longer than that and both you and the participant start to drift.

Step 2: Find participants without paying an agency

You need people who roughly match your users, not a perfect sample. Five per round is plenty.

• Existing users. If the product is live, ask through an in-app message, email or support chat. People who care about a product are often happy to help improve it.
• Communities. Subreddits, Telegram and Discord groups, Facebook groups, local forums around your topic. A collectors’ community for a card app, a running club for a fitness app.
• Your network, carefully. Friends of friends who fit the profile are fine. Your design colleagues are not: they think like designers, not like users.
• Social media. A short post: "Looking for 5 people who use banking apps for a 30-minute call. Coffee voucher as a thank-you."
• Guerrilla testing. Go where your users are, like a café or coworking space, and ask for five minutes in exchange for a coffee.

A small thank-you goes a long way: a gift card, a free month of the product or simply sharing what you learned. And always ask for consent before recording, and explain how the recording will be used.

Step 3: Run the session like a pro

Moderating is a skill, but a few rules get you most of the way there.

• Put people at ease. Start with: "We’re testing the design, not you. You can’t do anything wrong." Nervous participants give polite, useless answers.
• Ask them to think out loud. "Please say what you’re looking at and what you expect to happen." This is where the real insights live.
• Stay quiet. The hardest part. When someone struggles, don’t help, don’t explain, don’t hint. Count to ten in your head. The struggle is the data.
• Answer questions with questions. "What do you think this button does?" instead of telling them.
• Watch, don’t just listen. People often say a task was easy right after struggling with it for a minute. Trust behavior over opinions.
• Ask follow-ups at the end. "What was the most confusing part?" "What did you expect to find here?"

Remote sessions work just as well. A video call with screen sharing, the prototype link and permission to record is all you need. Bonus: participants test from their own phones and homes, which is closer to real life than any lab.

If you can, have a second person take notes so you can focus fully on moderating.

Step 4: Turn observations into fixes

Five sessions produce a pile of notes. The value is in what you do next.

1. Collect everything in one place. Write each observation on a separate sticky note on a digital board: one problem, one note, with who and where.
2. Group similar problems. Clusters appear quickly: "couldn’t find history," "didn’t understand the price," "missed the save button."
3. Count and rate. How many of the five people hit each problem? How badly did it block them? A problem that stopped three people beats a cosmetic issue that annoyed one.
4. Prioritize. Fix what’s frequent and severe first. Note the rest for later.
5. Share it simply. A one-page summary with the top problems, a short video clip of each and a proposed fix. A ten-second clip of a real user struggling convinces stakeholders faster than any slide.
6. Test again. After fixing, run another small round. That’s the real secret of zero-budget research: small, frequent tests beat one big study you can never afford.

Free and cheap tools that do the job

• Prototype: Figma, shared as a clickable link that works on a phone.
• Calls and recording: Zoom, Google Meet or any video tool that records screen and voice.
• Notes and synthesis: FigJam or Miro boards for sticky-note analysis.
• Unmoderated tests: platforms like Maze offer free or entry plans for simple prototype tests, with usage limits.
• AI helpers: transcription and AI assistants can summarize recordings and draft themes. Always check them against the actual footage.

Mistakes to avoid

• Asking "Do you like it?" Opinions about looks tell you little. Watch whether people can complete tasks.
• Leading questions. "This is easy to find, right?" gets you a yes, not the truth.
• Testing with designers. They spot design issues, not user issues.
• Helping too soon. The moment you explain, you lose the most valuable data.
• Testing too late. Testing a finished app makes fixes expensive. Test early prototypes when changes cost minutes.
• Collecting insights nobody acts on. If findings don’t change the design, the test was just a nice conversation.