How do you decide when to do quantitative vs qualitative research?

Analytical Research Decision Matrix: 1) Define the decision stage (exploratory vs evaluative), 2) Identify the question type (why vs how many), 3) Assess confidence level of existing insights, 4) Match method to resources (time, budget, sample size), 5) Plan mixed-method if needed.

What They’re Really Asking

Can you systematically match research methods to design problems and business constraints?

Framework: Use the Research Decision Matrix: 1) Define the decision stage (exploratory vs evaluative), 2) Identify the question type (why vs how many), 3) Assess confidence level of existing insights, 4) Match method to resources (time, budget, sample size), 5) Plan mixed-method if needed. framework to structure your answer.

Strong Sample Answer

I decide by starting with the core question: 'Do I need to understand why users behave a certain way or measure how many do?' For discovery—like when I led a redesign of a checkout flow at Google—I used qualitative methods first. I ran five moderated usability sessions in UserTesting, observing friction points and asking open-ended questions. That revealed why users abandoned carts: unclear shipping options and trust issues. This phase gave me user stories and journey maps. Then, to validate the redesign's impact, I switched to quantitative: an A/B test in Optimizely with 10,000 users across two variants, measuring conversion rate and error recovery. The data showed a 12% lift, confirming the qualitative insights generalized. In contrast, for a Meta onboarding flow, I started with quantitative—analytics on drop-off rates—because we had clear metrics from existing data. That identified the biggest problem funnel, then qualitative interviews explained why. I always weigh triangulation: if both methods align, decision confidence is high. Tools like Figma for quick prototypes and UserTesting for remote sessions speed this. The key is not to default to one method; it's a deliberate, stage-dependent choice that balances depth and breadth.

Common Mistake to Avoid

Don’t do this: A common mistake is leading with quantitative when you don't yet understand the user's context, wasting budget on measuring things you can't interpret.

Company-Specific Variants

Google Variant

At Google, emphasize structured hypothesis testing: use quantitative to identify signals at scale, then qualitative to deep-dive on why those signals matter in product areas like search or ads.

Apple Variant

At Apple, focus on craft and context: start with in-lab qualitative observations of small user groups to uncover hidden needs, then use quantitative only to validate design direction against core human values.

Meta Variant

At Meta, prioritize speed and iteration: run lightweight qualitative tests on prototypes in Figma to learn fast, then use quantitative A/B tests on live builds to measure social engagement metrics like time spent and sharing rates.

📚 Recommended Resource

The 0-1 PM Interview Playbook (2026 Edition)

Product design thinking and UX interview frameworks used at Google, Apple, and Meta.

Get it on Amazon →

Related Analytical Questions

How would you measure the success of a redesigned checkout flow?What metrics would you track for a new onboarding experience?