Your checkout page has a 68% drop-out. That number shrieks at you from the Google Analytics. Something is broken, obviously. But what? The data shows users dropping off on the payment screen. It doesn’t tell you why. Are they lost in the layout? Worried about security? Surprised by shipping costs? Tired of having too many form fields?
You could guess. Most teams do. They redesign on the basis of intuition, ship changes and hope the conversion rates are better. Sometimes they do. Often they don’t. And when they don’t work, no one has any idea why, because you started with a number and ended up with a slightly different number, having learned nothing in between.
This is what happens when teams rely on using only one type of research. The numbers tell you that something’s wrong. They don’t tell you how to fix it up. The stories from user interviews identify frustrations. How many people do they have in common with those frustrations? You need both. The question is not which to choose. It’s when to use what.
Quantitative research measures what is happening. How many users do the checkout? How long do you spend on an average session? What% click the primary CTA? Which variation is better in A/B tests? It provides you with numbers, percentages, and statistics. Data that you can graph and trend, and show to the executives who love hard facts.
Qualitative research is why it’s happening. Why are users leaving their carts? What is the people’s confusion about navigating? What is their perception of the onboarding process? What issues are they trying to address when they visit your site? It provides you with stories, observations, quotes, and patterns. Insights you can’t boil down to the results of one metric but that change the way you understand your users.
Neither is better. Both have answers to different questions. Treating them as competitive rather than complementary tools is the way research projects waste money answering questions nobody needed answering.
Use quantitative research when you need to know scope, scale or significance. When the question begins with “how many,” “how much” or “how often,” you need numbers.
Currently, 87% of organisations use user research to make important decisions. Most of that research at critical decision points is quantitative because the people who need to be convinced of the need for solutions need the confidence that the problems are bothering enough users to justify solutions.
Patterns impossible to detect in conversations are revealed using analytics. Task completion times depend on the device. Drop-off rates are spiking on certain form fields. Changing conversion rates per traffic source. These patterns only appear when measuring hundreds or thousands of interactions.
A/B testing calls for the use of quantitative methods. You can’t work out which design variant works better without large-scale measurement of completion rates, time on task and conversion metrics with statistical significance.
Benchmarking requires numbers. Comparing your product against your competitors or measuring performance over time requires that your metrics are consistent and measured the same way each time.
Use qualitative research when you need to know motivations, frustrations, mental models or contexts. When the question begins with “why”, “how”, or “what experience”, you need stories.
Numbers reveal that there is a problem. Qualitative research – illustrates why it exists and how to solve it. Your analytics indicate that users are leaving the signup flow at step three. Great. You know where. You still don’t know why. Are the instructions unclear? Is the required information hard to find? Does the form seem too long? Are users concerned with privacy? You will not answer these kinds of questions by staring at analytics dashboards.
User interviews find problems you did not know existed. You can’t measure something that you’re not looking for. Analytics tracks what you instrument. Surveys ask questions that you already thought of asking. Qualitative methods allow users to surprise you with pain points, workarounds and use cases your team never thought of.
To understand context, you have to look. Users don’t interact with your product in a vacuum. They’re interrupted by notifications, distracted by colleagues, working on tiny phone screens during their commute or multitasking with three other apps open. Watching people use your product in their natural environment shows you the friction that is invisible in your controlled tests.
Testing of new concepts requires qualitative feedback. Before investing in development, show the prototypes to users. Watch them interact. Listen to their reactions. Ask what they think different elements ought to do? This exploratory research informs what you build instead of validating what you’ve already built.
Choosing by Comfort over Need. Teams that are accustomed to surveys default to surveys even when interviews would answer the question better. Teams comfortable with analytics don’t venture into qualitative research even when numbers can’t explain behaviour.
Anecdotal Treatment of Qualitative Research: Three users having difficulty performing the same task in usability testing isn’t anecdotal. It’s a pattern worth redressing.
Using quantitative research for the “why” questions: Users rate satisfaction as 6/10. Why? Time on page declining – analytics show. Why? Numbers document problems. They rarely explain them.
The best research incorporates both approaches strategically. Start with one way of identifying problems, and use the other to understand/validate them.
Run some analytics to identify points of friction, and then conduct user interviews to identify reasons why those points are causing friction. Numbers indicate where users are having difficulties. Interviews reveal the reasons for their difficulty and how to eliminate that difficulty.
Conduct interviews to find out what unexpected user needs exist, and then survey a larger population to find out how common the user needs are. A couple of users refer to wanting a particular functionality. Before constructing it, ensure that those users are a large enough group worth serving.
In order to measure the impact of A/B testing, use qualitative follow-up to understand why one was better than the other. The variant B increased conversions by 15%. Great. Why? Understanding the reason is what allows you to apply what you learned to other situations, rather than just “this specific button colour worked better on this specific page”.
Research has been conducted by Weetech Solution to find out that 74% of high-growth companies conduct qualitative and quantitative research before major launches. They don’t pick one method. They use both because big decisions merit in-depth understanding from a variety of viewpoints.
Prototype testing is a combination of both. Measure task completion rates and time on task (quantitative) and observe struggles and listen to think-aloud commentary (qualitative). You’re learning not only what users can do, but why they can do it easily or not and why they find certain things.
Your e-commerce company wants to enhance the product detail page. Here are the ways to approach it with both methods:
First, look at the data. Analytics indicate high bounce rates on product pages. Users spend an seconds on before leaving. Scroll depth data reveals that 60% of users never scroll below the fold.
These identify problems but don’t explain them. Why such high bounces? Why aren’t people scrolling? Why are so few adding to the cart?
Then, talk to users. Usability test with 8-10 target customers. Watch them look at pages of products. Ask them to fill out realistic shopping tasks. Use think aloud protocol to listen to their thought process.
You discover that users can’t quickly find size information, product images are too small to see the details, that shipping cost isn’t visible until checkout, and that reviews are buried below specifications that most users don’t reach.
Now you can solve real problems rather than guessing. Shift size information to the top. Enlarge product images. List shipping costs on product pages. Elevate reviews. These changes reflect actual user frustrations that were uncovered during qualitative research.
Finally, check with numbers. Conduct A/B tests with measurements of the impact. Track bounce rates, time on page, scroll depth, and add to cart rates. The combination of methods led to informed changes, which you can measure for impact.
Ask yourself what you really need to know. Are you trying to catch the size of a known problem? Go quantitative. Are you trying to understand something that you’ve observed? Go qualitative.
Consider your project phase. The early discovery has the advantage of qualitative exploration. Validation later becomes requirements for quantitative measurement. Continuous improvement employs both of them in alternating cycles.
Match the method to the question, not the question to your favourite method. Start with clear questions, and then select methods that answer those particular questions best.
Stop thinking of qualitative and quantitative research as opposed choices. They’re different tools for different jobs. You don’t take a hammer when you need a screwdriver. Don’t settle on surveys when you need interviews, or vice versa.
The organisations making the best decisions are using both. They measure to quantify problems and prioritise priorities. They observe to understand problems and design solutions. They don’t make the choice between data and empathy. They use stories and numbers to combine and build a complete understanding.
Your 68% checkout abandonment rate is a symptom. The number alone won’t cure it. Go talk to your users. Watch them struggle. Understand their frustrations. Then measure whether your fixes actually work. This is how research leads to real improvement rather than just creating reports nobody does anything with.
Because at the end of the day, you’re not trying to collect data and do interviews. You’re trying to make products people can use. Both quantitative and qualitative research help you do that when you use them right.
For qualitative research, 5-8 participants usually find the majority of usability problems – as more people are added the marginal gains become lower after 5 users for basic usability testing. User interviews usually require 8-12 participants in order to discover patterns. For quantitative you need only sufficient number of participants to reach statistical significance, which depends on the method but normally consists of 100+ for surveys, 30-50 per each variant for A/B tests, and thousands for reliable analytics patterns. The key difference: qualitative research, which attempts to gain depth and understanding with fewer people; quantitative research, which attempts to gain statistical confidence with larger amounts of people.
Yes, well designed surveys involve a combination of both. Closed-ended questions with rating scales or multiple choice or yes/no answers yield quantitative data that you can analyze statistically. Open-ended questions that asked “why” or “how” produce qualitative data that reveal motivations and context. For example, ask users to rate satisfaction. 1-10 (quantitative) then, ask “What influenced your rating?” (qualitative). This mixed approach gives you both measurable data and explanatory insights, and that makes surveys powerful when you need both breadth and a little depth.
Start with qualitative research when you have exploratory projects in which you are trying to understand user needs, problems, and contexts. User interviews and/or contextual inquiries or observational studies can help you find out what you should measure. Once you know the landscape, use quantitative research to prove assumptions, prioritize problems, and measure baselines. However, if you’re working on optimizing an existing product and you already have existing metrics that are being tracked, try to use a quantitative analysis first to determine where the problems are occurring, then qualitative methods to determine why those problems are occurring.
C – 81C, Sector – 8, Noida 201301, India
1025 Beamon Drive, Franklin 37064 Tennessee, USA
Sveavagen 34 111 34 Stockholm, Sweden
A-10, Sahastradhara Rd, Doon IT Park, Dehradun, Uttarakhand
© 2026 UX STALWARTS. All rights reserved.
