UX Design Principles: User Research Methods

The four UX research methods every small business website project needs, and how to run them without a dedicated research team.

Published 8 min read
Fredy RodriguezFredy Rodriguez
Blank sticky notes and index cards arranged in affinity clusters on a studio wall, representing user research synthesis and qualitative data grouping
Table of Contents

Good web design starts with a question most businesses skip: what do your users actually need?

Not what you think they need. Not what looks nice in a mockup. What people genuinely try to accomplish when they land on your site, and what stops them from doing it.

User research is the practice of answering that question before you build, redesign, or revise. It is not a luxury for big companies with dedicated UX teams. It is the fastest way to avoid building the wrong thing, and the problems it catches early cost far less to fix than ones discovered after launch. IBM’s research on software defects found that issues caught during the design phase cost up to 30x less to fix than those discovered in production.

This is the first part of our three-part series on UX design principles. It covers the research methods worth knowing and how to apply them without a specialist team. Part two covers information architecture: structuring your site around what users expect, and part three covers usability testing: validating your designs with real users.

Two modes of research

Every user research method fits into one of two modes.

Generative research happens before you design or redesign anything. Its job is to surface what problems exist, what users are trying to accomplish, and what mental models they carry. Skip this mode and you risk building the wrong thing well.

Evaluative research happens after you have a design (even a rough one). Its job is to test whether what you built actually works. It catches friction, confusion, and missed expectations while there is still time to fix them cheaply.

Most small business projects over-invest in aesthetics and skip both modes entirely. The result is a site that looks polished but does not convert, because no one verified that visitors can find what they came for.

Four user research methods worth starting with

You do not need a research lab or specialist software to run effective user research. These four methods cover the majority of what most small business website projects require.

User interviews

One-on-one conversations with current or potential customers, focused on understanding goals, frustrations, and decision-making patterns. Interviews are generative: they tell you what problems your site (or redesign) needs to solve.

A good interview lasts 30–45 minutes, follows a loose script of open-ended questions, and avoids leading the participant toward a preferred answer. According to a systematic review of 23 empirical studies, saturation (the point at which new interviews stop producing new findings) typically occurs between 9 and 17 participants, with a median of 12 to 13. For a focused project, 8 interviews are usually enough to surface the patterns that matter.

On-site surveys

Short, targeted surveys (3–5 questions) shown to visitors at key moments: after they complete a task, when they exit without converting, or when they spend an unusually long time on a page. Surveys collect attitudinal data at scale without requiring you to recruit participants.

The best on-site surveys ask one open-ended question (“What stopped you from contacting us today?”) rather than five closed ones. The friction of answering is low; the signal is often sharper than you expect.

Analytics review

Your existing Google Analytics data is already a form of user research. Before running a single interview, review: which pages have the highest exit rates, where in a multi-step form people drop off, which traffic sources produce the most contact form submissions, and which device types dominate your audience.

Analytics is quantitative and behavioral: it tells you what is happening. It cannot tell you why. That is what interviews and observation are for. The two methods work together.

Usability sessions

A usability session asks a real user to complete a specific task on your site while thinking aloud, so you can observe where they get stuck. You give them a task (“Find and contact the right person to ask about a quote”) and watch without helping.

Research has long held that five users surface roughly 85% of the most common problems. In practice, the range across five-user groups runs from 55% to 99%, so eight to ten participants substantially reduces the risk of missing something important. For a focused redesign, start with five and plan a second round after you have made changes.

How many participants you actually need

The number depends on the method and the question you are trying to answer.

For evaluative usability testing, five participants is a reasonable starting point for a focused qualitative study, particularly in an iterative process where you test, fix, and test again. If you need high confidence before a significant investment, aim for 10.

For generative interviews, plan for 8–12 participants for a homogeneous audience. If your customer base is genuinely diverse (different industries, company sizes, or use cases), segment and aim for 5–8 per segment.

For surveys and analytics, numbers are less about saturation and more about statistical confidence. A few hundred responses give you usable patterns for closed questions; analytics data from real traffic is representative by definition.

The wrong answer is zero. According to a 2024 survey of 444 UX professionals, 75% use user interviews or surveys as their primary research method. For most businesses, the gap between “we did some research” and “we designed based on assumptions” is the difference between a site that works and one that needs a rebuild in 18 months.

What this looks like for a Houston SMB

A full enterprise UX research process is not practical for most Houston small businesses. What is practical: a half-day investment before a redesign.

Five customer phone calls (30 minutes each) with open-ended questions about how they found you, what they were looking for, and what almost stopped them from contacting you. One 45-minute screen-share session asking a colleague or friendly customer to find your services page and attempt to request a quote. A 30-minute review of your Google Analytics, specifically looking at mobile exit rates and form drop-off.

That is roughly six hours of work. It will surface the three to five issues most worth fixing before a single pixel is moved. Energy Corridor service businesses and Montrose retail shops face the same constraint: visitors make decisions fast and leave fast. Research tells you what they are deciding and why.

The motion giraffx video production site rebuild started with exactly this kind of audit: listening to what the client’s customers actually needed from the site rather than what the client assumed they wanted. The result was a site structured around how prospective clients evaluate a video production studio, not around the services the studio was most proud of.

If you want to understand the design principles behind those decisions, our guide to designing for small business covers the fundamentals that good user research feeds into.

The next step in this series is information architecture: how you translate what you learn from research into a site structure visitors can actually navigate. You can also see this approach in the super lap battle motorsport event site, where restructuring the information architecture around what attendees actually searched for doubled the site’s utility as an event resource.

When you are ready to put research into practice, our web design process starts with exactly this kind of discovery work.

Frequently asked questions

What are the main types of user research methods?

UX research methods fall into two modes: generative (discovering what problems to solve before you build) and evaluative (testing whether what you built actually works). Within those modes, methods split further into qualitative (interviews, observation), which answer why something happens, and quantitative (analytics, surveys with numeric data), which answer how often. Most effective projects use at least one method from each mode. The Nielsen Norman Group framework classifies methods across three axes: behavioral vs. attitudinal, qualitative vs. quantitative, and context of use.

How many users do you need for user research?

It depends on the method. For usability testing, five users find roughly 85% of the most common problems on average, though individual sessions vary widely. For interview-based research, a 2022 systematic review of 23 empirical studies found saturation typically occurs between 9 and 17 participants, with a median of 12 to 13. The practical answer for most small business projects: 5 to 8 participants for a usability session and 8 to 12 for discovery interviews.

What is the difference between qualitative and quantitative user research?

Qualitative research (user interviews, contextual observation, think-aloud sessions) answers why users behave a certain way and surfaces motivations and pain points that numbers alone cannot reveal. Quantitative research (analytics, heatmaps, large-scale surveys) answers how many users exhibit a behavior and how often. Both are necessary: qualitative tells you what to fix, quantitative tells you how much it matters and helps you prioritize.

Can a small business do user research without a UX team?

Yes. The highest-leverage methods require no specialist tools: five customer phone calls with structured questions, a task-based screen-share session with three to five real users, and a review of your existing Google Analytics data are enough to surface the majority of critical issues on most small business websites. The goal is not a perfect study; it is enough signal to stop making decisions based on assumptions. Our UX-driven web design service includes this kind of discovery as standard.

Share this postTwitter / XLinkedInBluesky
Fredy Rodriguez
Fredy Rodriguez

Technical Director & Co-Founder

Runs the data-and-code side of Desque: SEO, GEO, AEO, PPC, copywriting, and the engineering behind every site we ship. Builds in Go and TypeScript.

Continue in series: UX Design Principles