Ever spent months crafting a product feature you were sure was a game-changer, only to launch it and hear… crickets? Or worse, see a flood of support tickets from confused users? It’s a classic story. The gap between how we think people will use our product and how they actually use it can be a humbling experience. This is where usability testing comes in, acting as your bridge over that gap.

This article gives you a step-by-step overview of how to conduct usability testing at scale & practical strategies to improve it, so you can create products users actually love using.

What is usability testing?

So, what exactly is usability testing? Before we get into the nitty-gritty, let's make sure we're on the same page. Think of it as watching a real person try to use your product to accomplish a specific goal.

Unlike other forms of user research, usability testing focuses specifically on the user’s ability to use a product effectively, efficiently, and satisfactorily.

When conducted properly, usability testing provides invaluable insights into how real users interact with your product - revealing pain points, confusion, and barriers that might otherwise go unnoticed by those too close to the product development process.

This is a foundational practice in countless UX design methodologies for a good reason. The entire point is to uncover moments of friction. Where do people get stuck? What makes them hesitate or feel frustrated? What parts of the experience actually make them happy?

Usability testing gives you raw, unfiltered insights directly from the people you're designing for. It's the fastest way to see your product through fresh eyes and fix the problems you’re simply too close to notice.

Types of Usability Testing Every Product Team Needs to Know

One of the biggest mistakes you can make is treating usability testing like a one-size-fits-all tool. The right method really depends on what you need to learn, how much time you have, and the budget you're working with.

Let's break down the main categories to help you choose the right approach:

1. Qualitative vs. Quantitative Usability Testing

• Qualitative usability testing focuses on collecting insights, findings, and anecdotes about how people use a product or service. The goal here is to understand the why behind their actions.
  
  You're observing their behavior, listening to their thought process, and uncovering pain points.

  Think of it as a deep conversation. You’ll typically work with a smaller sample size (around 5-8 users) because the data you're collecting is rich and detailed.

  
  This usability testing method is perfect for discovering usability issues you didn't even know existed and getting direct feedback on design elements.
  
  
  

• Quantitative usability testing, on the other hand, focuses on collecting metrics that measure the user experience. You're looking for the how much or how many. This type of testing involves a much larger sample size to ensure statistical significance.
  
  

  The data you gather might include success rates (e.g., what percentage of users completed a task?), the time it took to complete a task, or the number of errors made.

  
  This usability testing approach is excellent for benchmarking your product's performance against competitors or tracking improvements over time.
  
  

2. Moderated vs. Unmoderated Usability Testing

• Moderated usability testing involves a facilitator who guides the participant through the session in real-time. This can be done in person or remotely. The moderator’s role is to introduce the test, answer the participant's questions, and ask follow-up questions to dig deeper into their behavior and feedback.
  
  

  This "live" interaction is incredibly valuable for complex tasks or for exploring user motivations in-depth. If a user gets stuck, the moderator can probe to understand their thought process without leading them to a solution.
  
  

• Unmoderated usability testing is conducted without a facilitator present. Participants complete tasks on their own time, often in their own environment using their own devices. Their screens and voices are typically recorded by a testing platform.
  
  

  This usability testing method is faster, more affordable, and allows you to test with a larger number of users across different geographic locations.

  
  It’s ideal for testing specific, straightforward tasks and gathering feedback on a larger scale, but you lose the ability to ask spontaneous follow-up questions.

Image source: TestingTime

3. Remote vs. In-person Usability Testing

• Remote usability testing, as the name suggests, is conducted with the participant and facilitator in different physical locations. This method has become the default for many teams due to its convenience and cost-effectiveness. It also allows you to recruit participants from a much wider geographic pool, giving you a more diverse sample.
  
  

  Remote tests can be either moderated (via video conferencing tools) or unmoderated, offering great flexibility. You get to see users interact with your product in their natural environment, which can lead to more realistic insights.
  
  

• In-person usability testing requires the participant and facilitator to be in the same physical location, usually a lab or office. While this method requires more logistical planning and is often more expensive, it offers unique benefits.
  
  

  Being in the same room allows the facilitator to observe non-verbal cues like body language and facial expressions, which can provide a deeper layer of understanding.

  
  It’s particularly useful when testing physical products, complex prototypes, or when working with participants who may not be tech-savvy.

5 Benefits of Usability Testing

Investing in usability testing isn't just a "nice-to-have" for making users happy. It's a rock-solid business decision that directly impacts your bottom line.

Here are 5 key benefits you can expect:

1. Reduces development costs & risks: Catching a major design flaw before your developers write a single line of code can save an absolute fortune in expensive, time-consuming fixes down the road. It’s the classic "measure twice, cut once" principle applied to digital products.

   
   By identifying and fixing issues early, you minimize wasted engineering effort and ensure you're building a product that people can actually use.

   
   

2. Increases user satisfaction & loyalty: When you create a genuinely seamless and intuitive experience, you're not just increasing user satisfaction, but building loyalty. A product that is easy and enjoyable to use makes customers feel competent and valued.

   
   This positive experience encourages them to return, engage more deeply with your product, and become dedicated brand advocates who stick around and recommend you to others.
   
   

   
   

3. Provides actionable, evidence-based insights: What I love most is that watching real people interact with your product gives you insights that raw analytics simply can't provide. You see the why behind the clicks. This qualitative data is gold, helping you understand user motivations, frustrations, and mental models.

   
   Usability testing takes the guesswork out of product development and arms your team with evidence to make confident, user-centric decisions.
   
   
   

4. Improves conversion rates: Every point of friction in a user's journey is a potential drop-off point. Whether it's a confusing checkout process, a hard-to-find call-to-action, or unclear navigation, these issues directly impact your conversion rates.
   
   Usability testing helps you pinpoint and eliminate these barriers, creating a smoother path for users to achieve their goals, and for product teams to achieve their business objectives.
   
   
   

5. Offers a competitive edge: In a crowded market, a superior user experience can be your key differentiator. Many companies still rely on assumptions or internal feedback to guide their design decisions.

   
   By systematically testing with real users, you can create a product that is demonstrably easier and more pleasant to use than your competitors'. This user-centric approach is a non-negotiable, often used by some of the best UX agencies for design-led startups.
   
   

6. Builds user empathy: Watching real people struggle with aspects of your product builds empathy within development teams. This firsthand experience often motivates designers and developers to create more user-friendly solutions.

Companies often underestimate the benefits of usability testing until they see the positive impact on their bottom line.

Even a single round of testing can reveal critical insights that dramatically improve your product’s performance.

When should you do usability testing?

A common misconception is that usability testing is a one-time event that happens right before launch. In reality, it's most effective when integrated throughout the entire product development lifecycle. Testing early and often is the key to building successful products.

That said, while testing can be beneficial at any stage, certain points in the development process yield particularly valuable insights - some of which are:|

1. Early concept & design phase

Testing early concepts, even with paper prototypes or wireframes, can validate ideas before significant resources are invested in development.

Early testing helps:

• Validate that your concept addresses real user needs
  
  

• Identify major usability issues in the initial design
  
  

• Compare multiple design approaches
  
  

• Set a baseline for future improvements
  
  

2. During development

Iterative testing throughout development allows you to refine the product as it’s being built:

• Test individual features as they’re developed
  
  

• Validate navigation and information architecture
  
  

• Ensure new features integrate well with existing ones
  
  

• Catch issues when they’re less expensive to fix
  
  

3. Pre-launch

Before launching your product, comprehensive testing helps ensure it’s ready for users:

• Validate the end-to-end user experience
  
  

• Identify any critical issues that would impact launch
  
  

• Gather baseline metrics for post-launch comparison
  
  

• Test edge cases and less common scenarios
  
  

4. Post-launch

Testing shouldn’t stop after launch. Ongoing testing helps:

• Evaluate how real users are adopting the product
  
  

• Identify issues that weren’t caught in pre-launch testing
  
  

• Test new features before rolling them out to all users
  
  

• Measure improvements against baseline metrics
  
  

5. When making significant changes

Any time you’re planning major updates or redesigns, usability testing should be part of the process:

• Test new designs against current versions
  
  

• Ensure changes actually improve the user experience
  
  

• Identify any new issues introduced by the changes

The ideal approach is to incorporate usability testing throughout the product lifecycle, creating a continuous feedback loop that informs ongoing improvements.

How to conduct usability testing?

Alright, let's get into the step-by-step process. This is where the rubber meets the road - moving from theory to a hands-on process that gets you real, actionable insights.

Here's a stepwise approach on how to conduct usability testing like a pro:

1. Define clear objectives: Before you do anything else, you need to know what you’re trying to learn. A vague goal like "see if the design is good" will lead to vague results. Instead, define sharp, focused research questions. For example: "Can users successfully find and use the new calendar filtering feature?" or "What are the main points of friction in our user onboarding flow?"

   
   Your objectives will guide every other decision in your study, from who you recruit to the tasks you design. Make sure your goals are specific, measurable, and tied to your team's priorities.

   
   This clarity ensures that you end up with actionable insights, not just a collection of random observations.
   
   
   

2. Create a test plan: A test plan is your roadmap. It’s a document that outlines all the key details of your study to keep everyone aligned.

   
   It should include your research objectives, the methodology you’ve chosen (e.g., moderated remote testing), participant criteria, the tasks you’ll ask users to perform, and the key usability metrics you'll be tracking (like task success rate or time on task).

   
   This document doesn't need to be a 50-page file, but it should be thorough enough to communicate the what, why, and how of your study to stakeholders. It forces you to think through the details ahead of time and serves as a central source of truth for the entire project.
   
   
   

3. Select the right testing method: There are several usability testing methods to choose from, including moderated, unmoderated, remote, and in-person approaches. Your choice should align with your objectives, budget, timeline, and the nature of what you’re testing.

   
   For early-stage concepts or complex products, moderated testing often yields richer insights.
   
   For more refined products or when you need a larger sample size, unmoderated testing might be more appropriate.
   
   
   

4. Recruit the right participants: This step is critical. Testing with the wrong people is one of the fastest ways to get misleading results. Your participants should genuinely reflect your target audience. Create a screener survey with specific questions to filter for the demographics, behaviors, and technical abilities that match your ideal users.

   
   Don’t just recruit your friends or colleagues; they are likely biased and too familiar with your product. Aim for 5-8 participants for qualitative studies.

   
   You can also use recruiting services like UserTesting or UserInterviews, or leverage your own customer lists or social media channels to find the right people.
   
   
   

5. Write a test script & design tasks: Your test script ensures consistency across all sessions. It should include an introduction to welcome the participant and set expectations, the task scenarios, and follow-up questions. The tasks themselves should be realistic scenarios, not leading instructions.

   
   Instead of saying "Click the 'Add to Cart' button," frame it as a goal: "You've decided to buy a new pair of headphones. Show me how you would go about purchasing them."

   
   This scenario-based approach encourages users to think and act naturally. Remember to ask them to "think aloud" as they go through the tasks, so you can understand their thought process, expectations, and frustrations.

   
   It’s no surprise that this approach has become standard practice. A recent report on the latest UX research trends found that 71% of organizations now conduct usability testing on a regular basis.
   
   
   

6. Conduct the sessions: It's showtime! Whether you're in person or on a video call, your primary job as a facilitator is to make the participant feel comfortable. Reassure them that you're testing the product, not them, and that there are no right or wrong answers. Encourage them to be honest and vocal with their feedback.

   
   During the session, be an active listener and a neutral observer. Avoid reacting to their feedback or correcting them if they struggle. Your goal is to see how they navigate the interface on their own. Take detailed notes, or better yet, record the sessions (with permission, ofcourse) so you can review them later.

   
   You can also offer incentives (financial incentives, product access, donation or recognition) to participants in order to encourage them to share their insights or partake in the usability testing process.
   
   
   

7. Analyze the findings & create a report: Once the sessions are done, the real work begins. Review your notes and recordings to identify recurring patterns, key pain points, and insightful quotes.
   
   Group similar findings together into themes. This is where you connect the dots and turn raw observations into a compelling story about the user experience. Applying the right qualitative data analysis techniques is what truly turns those observations into powerful insights.
   
   Your final report should be concise and action-oriented. Don't just list the problems; prioritize them based on severity and provide clear, actionable recommendations for how to fix them.

   Use quotes, video clips, and screenshots to bring the user's struggle to life for stakeholders who weren't there. The goal is to inspire action, not to write a novel.
   
   

10 Usability Testing Methods You Can Use

The tools and methods you choose can make or break your research. Let's walk through 10 proven techniques to add to your toolkit:

1. Guerilla Testing

This is a fast, low-cost method where you go to a public place like a coffee shop and ask people to test your product for a few minutes, often in exchange for a coffee or small treat.

• When to Use: It’s great for getting quick feedback on early-stage concepts, wireframes, or specific design elements when you have limited time and budget.
  
  

• Limitations:
  
  

  • Participants may not be from your target audience.
    
    

  • Feedback is often high-level and not in-depth.
    
    

  • The environment can be distracting.
    
    

2. Five-Second Test

You show a participant a single screen (like a homepage) for just five seconds and then ask them questions like "What do you remember?" or "What was the purpose of this page?"

• When to Use: Perfect for testing the clarity of your visual design, messaging, and overall first impression. A compelling hero section often performs well in these tests.
  
  

• Limitations:
  
  

  • Doesn't test interaction or task flows.
    
    

  • Relies on user memory, which can be unreliable.
    
    

  • Only suitable for evaluating a single screen at a time.
    
    

3. Card Sorting

Image Source: UX Design Institute

Participants are given a set of digital or physical "cards," each with a topic, and are asked to group them in a way that makes sense to them. This helps inform your information architecture.

• When to Use: Ideal for designing or evaluating the navigation and structure of a website or app. Use it early in the design process.
  
  

• Limitations:
  
  

  • Results can be time-consuming to analyze.
    
    

  • Doesn't evaluate the user interface itself.
    
    

  • Can be abstract for some participants.
    
    
    

4. Tree Testing

Image source: Interaction Design Foundation

This is the reverse of card sorting. You give participants a task and ask them to find the right information within a simplified text-only version of your site's navigation structure (the "tree").

• When to Use: Excellent for validating your information architecture after card sorting to see if people can actually find things.
  
  

• Limitations:
  
  

  • Provides no insight into visual design or page content.
    
    

  • Doesn't reveal why users get lost, only where.
    
    

  • Can feel unnatural to some users.
    
    

5. A/B Testing

Image source: Optimizely

You create two different versions of a design element (e.g., a button, a headline) and show them to different segments of your audience to see which one performs better against a specific metric, like click-through rate.

• When to Use: Best for optimizing specific elements on high-traffic pages to improve conversion rates. Requires a live product with significant traffic.
  
  

• Limitations:
  
  

  • Only tells you what happened, not why.
    
    

  • Not suitable for testing major design changes.
    
    

  • Requires a large sample size for statistical significance.
    
    
    

6. First click testing

You give a participant a task and ask them where they would click first on the interface to complete it. This test reveals whether your design aligns with user expectations.

• When to Use: Useful for evaluating the effectiveness of navigation, labels, and calls-to-action on a specific screen or in a workflow.
  
  

• Limitations:
  
  

  • Only tests the very first interaction.
    
    

  • Doesn't tell you if the user would be successful after the first click.
    
    

  • Ignores the rest of the user journey.
    
    
    

7. Session Recordings

Image source: VWO

This unmoderated method uses tools to record real user sessions on your live website or app. You can watch anonymous recordings of users navigating, clicking, and scrolling through your product.

• When to Use: Great for identifying unexpected user behaviors, bugs, and points of friction in your live product on a large scale.
  
  

• Limitations:
  
  

  • You lack context on who the user is or what their goal was.
    
    

  • You can't ask follow-up questions.
    
    

  • Watching many recordings can be very time-consuming.
    
    

8. Surveys & Questionnaires

While not a direct observation method, standardized questionnaires like the System Usability Scale (SUS) or post-task surveys can be used to gather quantitative data on user satisfaction and perceived ease of use.

• When to Use: To benchmark usability over time, compare your product to competitors, or gather user satisfaction data after a test or redesign.
  
  

• Limitations:
  
  

  • Relies on self-reported data, which can be subjective.
    
    

  • Doesn't explain why users feel a certain way.
    
    

  • Low response rates can skew data.
    
    

9. Contextual Inquiry

This is a deep qualitative method where you observe and interview users in their own environment (e.g., their office or home) as they perform their regular tasks.

• When to Use: When you need a deep understanding of your users' workflows, challenges, and environment to inform complex product design.
  
  

• Limitations:
  
  

  • Extremely time-consuming and expensive.
    
    

  • Requires a small sample size.
    
    

  • The researcher's presence can influence participant behavior.
    
    

10. . Prototype Testing

    
    

Image source: UXPin

This involves testing an interactive but not fully coded prototype of your product. Prototypes can range from low-fidelity (clickable wireframes) to high-fidelity (visually detailed mockups).

• When to Use: Throughout the design process to get feedback on flows, interactions, and layouts before committing to code. It's one of the most common and versatile methods.
  
  

• Limitations:
  
  

  • Users might get hung up on the prototype's limitations (e.g., "lorem ipsum" text, non-working links).
    
    

  • High-fidelity prototypes can be time-consuming to create.
    
    

  • Feedback may focus on visual details rather than the core experience if the prototype is too polished.

How to write & ask usability testing questions?

The quality of your insights is directly tied to the quality of your questions. Asking the right questions in the right way can unlock a deeper understanding of the user experience.

The goal is to ask open-ended, non-leading questions that encourage users to share their thoughts and experiences.

Avoid simple "yes/no" questions. Instead of "Is this easy to use?", ask "How would you describe your experience using this?" Instead of leading them with "Click the green button," give them a scenario and ask, "How would you go about saving your progress?"

Your role is to be a curious observer, not an instructor. Listen more than you speak and get comfortable with silence - it often prompts participants to elaborate on their thoughts.

Examples of Usability Testing Questions You Can Ask

Given the crucial role these questions play in the testing process, here are a few sample questions you can use:

1. Before you begin, what are your initial impressions of this page?
   
   

2. What is the purpose of this page, in your own words?
   
   

3. What do you expect to happen when you click on this?
   
   

4. As you're doing that, what are you thinking right now? (The classic "think-aloud" prompt)
   
   

5. Was that what you expected to happen?
   
   

6. If you were looking for [X], where would you expect to find it?
   
   

7. How would you rate the difficulty of that task on a scale of 1 to 5? Why did you give it that rating?
   
   

8. Is there anything on this screen that you find confusing or unclear?
   
   

9. If you could change one thing about this process, what would it be and why?
   
   

10. What was the most frustrating part of this experience for you?
    
    

Top 5 Usability Testing Tools to Use

The right platform can handle everything from recruiting participants to analyzing data, making your job much easier.

Here are 5 of the best tools out there:

1. UserTesting: A giant in the industry, UserTesting provides access to a massive and diverse panel of participants. You can get video feedback from users completing your tests in as little as an hour.

Here are a few of its standout features for usability testing:

• Access to a global panel of testers.
  
  

• Fast turnaround times for unmoderated tests.
  
  

• Advanced filtering and demographic targeting.
  
  

• Tools for creating highlight reels and transcripts.
  
  
  

2. Maze: Maze is fantastic for rapid, unmoderated testing directly from your design prototypes (Figma, Adobe XD, Sketch). It provides quantitative metrics and beautiful, shareable reports.
   
   Here's what makes Maze the perfect usability testing tool:
   
   

• Seamless integration with design tools.
  
  

• Quantitative data like mis-click rates, heatmaps, and success rates.
  
  

• Card sorting and tree testing capabilities.
  
  

• Great for A/B testing different design variations.
  
  

3. Lookback: Lookback is a powerful tool for conducting live, moderated remote usability tests. It allows you to see the participant's screen, face, and hear their voice in real-time, alongside offering the following key features:
   
   

• Live, moderated interviews on desktop and mobile.
  
  

• Timestamped note-taking during sessions.
  
  

• Ability for team members to observe sessions live without being seen.
  
  

• Easy to create and share video clips of key moments.
  
  

4. Optimal Workshop: Optimal Workshop's platform is a suite of tools specifically designed for testing information architecture. If you're focused on navigation and structure, this is a must-have.
   
   Some of its standout features are as follows:
   
   

• Dedicated tools for card sorting (OptimalSort), tree testing (Treejack), and first-click testing (Chalkmark).
  
  

• Powerful analysis and visualization features.
  
  

• Recruiting services to find participants for your studies.
  
  

5. Hotjar: While often seen as an analytics tool, Hotjar’s "Observe" features (like heatmaps and session recordings) are a form of unmoderated usability testing on your live site. It helps you see how real users are behaving at scale.
   
   Some of the platform's prominent features include:
   
   

• Visual heatmaps showing where users click, move, and scroll.
  
  

• Recordings of real user sessions on your live product.
  
  

• On-site feedback polls and surveys to gather user sentiment.
  
  
  

8 Usability Testing Tips to Make the Most of Your Research

Conducting a successful study goes beyond just following the steps.

Here are 8 tips to help you gather higher-quality insights and make a bigger impact.

1. Do a pilot test first: Before you run your full study, conduct a pilot session with a colleague or friend. This rehearsal helps you iron out any kinks in your script, find technical glitches, and ensure your tasks are clear.
   
   It's a simple step that can save you from major headaches later on.
   
   
   

2. Make participants feel comfortable: Start each session by building rapport. Reiterate that you are testing the product, not them, and there are no wrong answers.

   
   An anxious participant is a quiet participant. When they feel comfortable, they're more likely to share honest, critical feedback.
   
   
   

3. Embrace the "think aloud" protocol: The most valuable insights come from understanding a user's thought process. Constantly encourage participants to "think aloud" as they work through tasks.
   
   If they go quiet, gently prompt them with questions like, "What are you thinking right now?" or "What are you looking at on the screen?"
   
   

4. Listen more, talk less: Your job as a facilitator is to listen, not to talk. Avoid the temptation to explain the interface or defend design decisions. Ask open-ended questions and then get comfortable with silence.
   
   Pauses often encourage participants to elaborate on their thoughts without you needing to prompt them.
   
   

5. Don't lead the user: Be very careful not to use words from your interface in your task descriptions. If your button is labeled "Submit Application," don't ask them to "submit the application."
   
   Instead, frame the task around their goal: "Now that you've filled out the form, show me how you would send it to the company."
   
   

6. Record everything (with permission): Your memory is not as reliable as you think. Always get permission to record the audio and screen of your sessions. This allows you to go back and catch nuances you might have missed while taking notes.

   
   Video clips are also incredibly powerful for showing stakeholders the reality of a user's struggle.
   
   
   

7. Involve your team as observers: Invite designers, developers, and product managers to observe the sessions live (but on mute!). There is nothing more impactful than watching a real person struggle with the feature you helped build.
   
   It creates empathy and a shared understanding of the problems that need to be solved.
   
   

8. Focus on behaviors, not opinions: While it’s fine to ask users what they think, pay closer attention to what they do. Users are often polite and may not want to hurt your feelings by saying they dislike a design.
   
   Their behavior, however, doesn't lie. Where they get stuck, hesitate, or take an unexpected path is where the real insights are.
   
   

Conclusion

Conducting usability testing is no longer a luxury; it’s a fundamental part of a smart, user-centered design process. By moving beyond assumptions and observing real user behavior, you can reduce costs, increase loyalty, and build products that genuinely solve problems.

This guide has given you the framework and methods to get started. Now it’s time to put them into practice and begin that crucial conversation with your users.

If you need help implementing a robust user research & UX design process for your product, the team at Bricx can help. To know more about how we do this, simply book a call today!

FAQs

How many users do I need for a usability test?

For qualitative usability testing, the widely accepted recommendation is 5 users. Research by the Nielsen Norman Group shows that testing with just 5 participants will uncover around 85% of the usability problems in an interface.

For quantitative testing, you'll need a much larger sample size (40+) to achieve statistical significance.

What's the difference between usability testing and user research?

User research is the broad discipline of understanding user behaviors, needs, and motivations through various methods like interviews, surveys, and field studies.

Usability testing is a specific user research technique focused on evaluating a product's ease of use by observing people as they interact with it.

Think of usability testing as one important tool in the larger user research toolbox, which includes many other user research techniques.

How long should a usability testing session be?

A typical moderated usability testing session lasts between 30 and 60 minutes. This is usually enough time to build rapport, have the user complete 3-5 key tasks, and ask follow-up questions without causing participant fatigue.

Unmoderated tests are often much shorter, typically lasting 10-20 minutes.

What's the difference between usability testing and focus groups?

Usability testing is about observing individual behavior as a user interacts with a product to complete specific tasks.

The focus is on action. A focus group is a moderated group discussion designed to collect opinions, attitudes, and beliefs about a concept or product. The focus is on discussion and opinions, not on observing use.

Can I do usability testing on a small budget?

Absolutely! Guerilla testing is a great low-cost option where you can offer small incentives like a coffee in exchange for a few minutes of feedback.

You can also use free or low-cost tools for screen recording and recruit participants from your personal network or social media (just be mindful of potential bias).

The key is to get your product in front of people who aren't on your team.