Blog / Research
Market Research Methods: Which Method Fits Which Decision
Match market research methods to the decision you need to make, with practical guidance on interviews, surveys, desk research, and research timing today.
On this page
- Common Market Research Methods: What’s on the Table?
- Qualitative vs. Quantitative vs. Secondary: The Honest Comparison
- Matching Research Methods to Decision Questions
- Decision → Method Matrix
- Timing Matters: Discovery vs. Validation
- The TRACE Framework: From Decision to Method in Five Steps
- Navigating B2B Buying Group Complexity
- A Triangulation Sequence That Reduces Risk
- Real-World Cases: What Works and What Doesn’t
- A Practical Decision-Tree for Method Selection
- Why Mixed-Method Strategies Are Your Best Bet
- Avoid These Common Pitfalls
- Conclusion: Audit Your Market Research Methods Before Your Next Big Decision
When founders and product teams face critical decisions—whether launching a new product, pivoting strategy, or validating features—the quality of market research can make or break the outcome. Yet many teams waste time and money on poorly chosen research methods that don’t answer their core questions or fit their decision stage. This article cuts through the noise with a no-nonsense, evidence-backed guide to selecting the right market research methods based on your specific decision needs, timing, and market context.
The core principle is simple, and most teams get it wrong: start from the decision, not the method. You do not need “some research.” You need to reduce the uncertainty that is currently blocking a specific choice—price, feature, segment, positioning, build-or-kill. The right method is whichever one removes that uncertainty fastest and cheapest. Everything below is a way to work backward from the decision to the method, instead of forward from a method you already like.
Common Market Research Methods: What’s on the Table?
Before diving into method selection, here’s a quick rundown of the main research approaches you’ll encounter:
- Quantitative Surveys: Structured questionnaires that generate numeric data. Best for measuring how many customers think or behave a certain way.
- Expert Interviews: Conversations with industry insiders or domain experts to uncover deep insights and validate assumptions.
- Customer/User Interviews: One-to-one conversations with people in your target market to surface motivations, jobs-to-be-done (the progress a customer is trying to make), and the real reasons behind behavior.
- Usability Testing: Observing users interact with a product or prototype to identify friction points and improve design.
- Desk Research: Analyzing existing data sources such as market reports, competitor analysis, and internal analytics. Also called secondary research—you reuse data someone else already collected.
Each method has strengths and weaknesses. The key is matching the method to the decision question. To make that concrete, here is how the three families of research compare on the dimensions that actually drive a choice.
Qualitative vs. Quantitative vs. Secondary: The Honest Comparison
These three families answer fundamentally different questions. Qualitative research tells you why and how. Quantitative research tells you how many and how much. Secondary research tells you what is already known before you spend a cent collecting new data. Confusing them is the single most common—and most expensive—research mistake.
| Dimension | Qualitative (interviews, usability) | Quantitative (surveys, analytics) | Secondary / desk research |
|---|---|---|---|
| Core question answered | Why? How? What’s going on? | How many? How much? Which is bigger? | What’s already known? |
| Output | Themes, quotes, mental models | Percentages, distributions, correlations | Synthesized prior knowledge |
| Typical sample | 5–8 per segment | n≥200 overall; n≥100 per subgroup | N/A (existing data) |
| Typical timeline | 1–3 weeks | 2–4 weeks | 2–5 days |
| Statistical projection | No—don’t quote percentages | Yes, within margin of error | Depends on source |
| Greatest strength | Depth, discovery, surprise | Scale, sizing, ranking | Speed, cost, context |
| Where it fails | Can’t size a market | Can’t explain a number | Stale, generic, mis-scoped |
| Cost profile | Moderate (time-intensive) | Low–moderate per response | Lowest |
Two rules fall straight out of this table. First, never report a percentage from eight interviews. “Six of eight users mentioned X” is not “75% of the market wants X”—it is a signal to go measure X at scale. Second, always run desk research first. It is the cheapest method on the table, and it routinely answers part of your question for free or reframes it entirely before you commission anything new.
Matching Research Methods to Decision Questions
Your choice hinges on what you need to know:
- “How many?” or “How much?” → Quantitative surveys provide statistically significant answers. For example, a SaaS team wanting to know what percentage of target users would pay for a new feature needs survey data.
- “Why?” or “How?” → Qualitative methods like expert or customer interviews uncover motivations, pain points, and decision drivers.
- Product interaction questions → Usability testing reveals real-world user experience issues that surveys can’t capture.
Avoid the trap of using surveys to answer “why” questions or jumping to usability testing before understanding user needs.
The table below maps the decisions product teams actually face to a recommended primary method, the reason it fits, and a realistic sample and timeline. Treat the samples as floors, not targets—if you can afford more, the data only gets more reliable.
Decision → Method Matrix
| Decision you’re making | Recommended primary method | Why it fits | Typical sample | Typical timeline |
|---|---|---|---|---|
| Is this problem worth solving at all? | Customer interviews + desk research | You need to discover the problem space before measuring it | 6–10 interviews per segment | 2–3 weeks |
| Which of several segments to target? | Survey with segment cuts | You need to compare sizes and needs across groups | n≥200, ≥100 per segment | 3–4 weeks |
| What to charge / will they pay? | Survey (Van Westendorp or Gabor-Granger) + a few interviews | Pricing needs distribution, not anecdote | n≥200 buyers | 2–4 weeks |
| Which feature to build next? | Interviews to frame + survey to rank (e.g., MaxDiff) | Discover candidates, then prioritize at scale | 6–8 interviews, then n≥150 | 3–5 weeks |
| Why is adoption / activation low? | Usability testing + funnel analytics | You need to see the friction, not guess at it | 5–8 sessions | 1–2 weeks |
| Is our positioning landing? | Message testing survey + interviews | Comprehension is qualitative; preference is quantitative | 5 interviews, then n≥150 | 2–3 weeks |
| Build, pivot, or kill? | Mixed: interviews → survey → analytics | High-stakes decisions need triangulation | Full sequence | 4–6 weeks |
| Sizing a market quickly | Desk research first | Someone has likely already estimated it | Existing data | 2–5 days |
| Mapping a B2B buying group | Interviews across roles + role-segmented survey | Each role weighs criteria differently | 2–3 per role | 3–5 weeks |
A note on the named techniques in that table: Van Westendorp and Gabor-Granger are two standard survey approaches to price sensitivity (the first asks at what prices a product feels too cheap or too expensive; the second tests willingness to buy at specific price points). MaxDiff (maximum-difference scaling) forces respondents to choose the most and least important items from small sets, producing a cleaner priority ranking than a plain “rate these 1–5” question, where everything tends to score “important.”
Timing Matters: Discovery vs. Validation
Research timing shapes method choice:
- Early-stage discovery calls for qualitative, exploratory research. Interviews and desk research help identify problems worth solving.
- Late-stage validation demands quantitative confirmation. Surveys and usage data validate hypotheses before costly investments.
Jumping to quantitative validation too early risks chasing the wrong problems and wasting resources. The reverse error is just as costly: staying in open-ended interviews long after you have a clear hypothesis, when you should be sizing it. A practical tell is saturation—when your next two interviews stop surprising you and simply confirm what you already heard, discovery is done. That is your signal to switch from “why” to “how many.”
The TRACE Framework: From Decision to Method in Five Steps
Most teams need a repeatable way to choose, not a one-off judgment call. Use TRACE—a five-step sequence you can run for any decision before you brief a single respondent. It is deliberately ordered so the cheap, fast steps come first.
- T — Target the decision. Write the actual decision in one sentence and the date it must be made. “Should we launch tier 3 pricing in Q3?” is a decision. “Learn about our users” is not. If you can’t name the decision, stop—you are not ready to research.
- R — Reduce with what you already have. Run desk research and pull internal analytics first. Often 30–50% of the question is already answerable from prior reports, support tickets, sales call notes, or product telemetry. Only research what’s genuinely unknown.
- A — Ask the right question type. Classify the remaining uncertainty as why/how (qualitative) or how many/how much (quantitative). Most real decisions contain both, in sequence—not at once.
- C — Choose the method and sample. Map the question type and decision stage to a method using the matrix above. Set the minimum sample now (5–8 for qualitative depth; n≥200 for quantitative projection; n≥100 per subgroup you intend to cut).
- E — Establish the evidence bar. Before fielding, decide what result would change the decision. “If fewer than 40% would pay $X, we don’t launch.” Pre-committing to a threshold stops post-hoc rationalization—the trap where any result gets read as supporting the plan you already wanted.
Run TRACE top to bottom and you will catch the two failures that waste the most money: researching something you already knew (caught at R), and collecting the wrong kind of data for the question (caught at A and C).
Navigating B2B Buying Group Complexity
B2B markets aren’t single-decision-maker environments. Buying groups include influencers, gatekeepers, users, and economic buyers—each with distinct concerns.
Research must map this complexity:
- Conduct interviews across roles to capture diverse perspectives.
- Use surveys segmented by role to quantify priority differences.
- Avoid treating the company as a monolith; decisions are multi-faceted.
Ignoring this complexity leads to incomplete insights and flawed go-to-market strategies. In practice, this means your sample math changes. A B2B study that needs three roles covered—economic buyer, technical evaluator, and end user—needs depth in each, so plan for 2–3 interviews per role rather than 6–8 overall. The economic buyer cares about ROI and risk; the end user cares about daily friction; the technical evaluator cares about integration and security. A survey that averages across all three hides exactly the disagreements that determine whether a deal closes. Cut every B2B survey by role before you read a single top-line number.
A Triangulation Sequence That Reduces Risk
For high-stakes decisions—build/pivot/kill, a major pricing change, entering a new segment—no single method is enough. Triangulation means confirming a finding through more than one independent method, so a conclusion only survives if multiple lenses agree. The reliable sequence is:
- Desk research to establish what’s known and frame hypotheses (days).
- Customer interviews to discover the real problem and language (1–2 weeks).
- Survey to size and rank what the interviews surfaced (2–4 weeks).
- Behavioral data (analytics, usage, a small experiment) to check whether what people say matches what they do (ongoing).
The order matters. Each step de-risks the next: interviews tell you what to ask in the survey; the survey tells you what’s worth measuring in behavior. When all four point the same way, you can act with real confidence. When they diverge—people say they’d pay but never click “upgrade”—you’ve found something more valuable than agreement: a gap between stated and revealed preference that, left undetected, would have sunk the launch.
Real-World Cases: What Works and What Doesn’t
- Success: A SaaS startup combined expert interviews and customer surveys during a pivot. Early qualitative work revealed unmet needs; subsequent surveys quantified opportunity size, guiding a focused product redesign.
- Failure: Another team relied solely on surveys to validate a new feature. They missed critical usability issues uncovered later, resulting in poor adoption and costly rework.
These examples underscore the value of mixed-method approaches and timing awareness. The pattern is consistent across both: the winners sequenced qualitative discovery before quantitative validation and checked claims against behavior; the losers picked one method, skipped a stage, and treated a single data source as the whole truth.
A Practical Decision-Tree for Method Selection
- What is your primary question? (How many vs. why/how)
- What is your decision stage? (Discovery vs. validation)
- Are you dealing with a complex buying group? (Yes/No)
- What resources and time do you have?
Use this to pick:
- Early discovery + why/how → Customer/expert interviews + desk research
- Late validation + how many → Quantitative surveys
- Product usability questions → Usability testing
- Complex B2B → Mixed qualitative and quantitative across roles
Why Mixed-Method Strategies Are Your Best Bet
Combining qualitative and quantitative methods balances depth and scale. Start with qualitative research to identify hypotheses and refine questions. Follow with quantitative surveys to confirm findings and measure impact. Iterate as needed.
This approach reduces risk, uncovers hidden insights, and ensures decisions rest on solid evidence. The trade-off is honest to name: mixed-method takes longer and costs more than a single quick survey. So reserve it for decisions where being wrong is expensive. For a low-stakes copy tweak, one quick test is fine. For a build/pivot/kill call or a pricing reset, the cost of the full sequence is trivial against the cost of getting it wrong.
Avoid These Common Pitfalls
- Using surveys to answer “why” questions leads to shallow insights.
- Reporting percentages from a handful of interviews—qualitative samples signal direction, they don’t measure magnitude.
- Ignoring buying group complexity results in incomplete data.
- Skipping early qualitative research wastes money on validating the wrong assumptions.
- Skipping desk research and paying to rediscover what a free report already says.
- Asking leading questions (“Wouldn’t you love a feature that…”)—you’ll get the answer you fished for, not the truth.
- Treating research as a one-off instead of iterative misses evolving market signals.
Conclusion: Audit Your Market Research Methods Before Your Next Big Decision
Choosing the right market research methods isn’t optional—it’s essential. The wrong method wastes time, money, and can steer your product or strategy off course. Use the decision framework here to review your current research stack and method choices. Are you answering the right questions with the right tools at the right time? If not, course-correct now.
Don’t gamble your next major decision on guesswork. Audit your market research approach today and build a foundation for smarter, evidence-driven choices.
Your next step: take the one decision in front of you this quarter and run it through TRACE on a single page. Write the decision and its deadline, list what you already know, classify the remaining unknowns as why or how-many, pick the method and minimum sample from the matrix, and set the threshold that would change your mind. If you can fill that page in twenty minutes, you’re ready to field. If you can’t, you’ve just found the real gap—and saved yourself a research budget spent answering the wrong question.
Author
About Vadim Glazkov
Vadim Glazkov is the founder of Glasgow Research and a product research expert working with founders and B2B SaaS teams on customer interviews, JTBD, market validation, and decision-ready research.