Propose two research methods to investigate checkout abandonment
Tests pairing behavioral and attitudinal research. Great answers match funnel analytics to find drop-offs with usability tests to uncover why users cannot complete fields or leave in anger.
What's really being asked
The interviewer wants to see if you understand research triangulation. Checkout abandonment is a messy problem with multiple causes, price sensitivity, usability failures, technical bugs, and trust issues. Picking two methods that yield the same data type shows a junior mindset. The question tests whether you can map method to insight: one method to locate the leak and quantify it, another to explain the human reasoning behind it.
The full answer
First, a quantitative behavioral method such as funnel analytics or session replay. This tells you exactly where users drop off, whether it is at shipping, payment, or account creation, and whether the pattern is device-specific. Second, a qualitative observational method such as moderated usability testing. This reveals why users abandon: Baymard research shows users often leave because they cannot complete fields, encounter unexpected costs, or become infuriated by forced account creation. The two methods work in sequence; analytics narrows the scope, and usability testing generates hypotheses about cognitive load and emotional response. A senior candidate also mentions sequencing, running the quantitative sweep first to prioritize which checkout steps to observe in the qualitative sessions.
The mistakes people make
Proposing two self-report methods like exit surveys and user interviews. Both capture what users say, not what they do, and self-reported data about checkout is notoriously unreliable because users post-rationalize leaving. Suggesting A/B testing as a research method; testing is for validation, not discovery. Proposing analytics without a follow-up qualitative layer, which leaves you with a dashboard but no actionable redesign target. Ignoring the distinction between checkout flow issues and general price sensitivity; Baymard data shows checkout design itself is frequently the sole cause of abandonment, not just the product cost.
What usually comes next
How would you recruit participants for the usability tests? How do you distinguish between a usability issue and a pricing issue? What would you do if analytics showed a 40% drop at the shipping step but users in testing said the price was fine? How would you prioritize fixes if you have limited engineering resources?
A concrete example
Say analytics show a 35% drop-off at the shipping information step. Session replay shows users hesitating and returning to the cart page. You then run moderated usability tests with five participants and observe three of them struggling to find the apartment number field, causing validation errors. One participant says, "I am worried my order will ship to the wrong place," and abandons. The quantitative data localized the problem; the qualitative data revealed it was a form layout issue, not a shipping cost surprise. You now have a specific fix: expose the secondary address line by default.
Interview question
Which research pairing best applies triangulation to checkout abandonment by first locating the drop-off and then explaining the human reasoning behind it?
- a.A/B testing and funnel analytics to validate checkout changes and measure conversion shifts
- b.Session replay and heatmaps to watch hesitations and visualize click patterns across devices
- c.Funnel analytics followed by moderated usability testing to find leaks and observe behavioral barriersCorrect
- d.Exit surveys and user interviews to capture stated reasons and emotional feedback
Why? this is the answer
Funnel analytics pinpoints exactly where users abandon, while moderated usability testing reveals cognitive and emotional causes like form confusion; option D is a common trap because two self-report methods only capture post-rationalized excuses, not actual behavior.
Just read this? Test yourself on what you have been reading.
Read the original → baymard.com
- #ux research
- #checkout abandonment
- #research methods
- #triangulation
- #e-commerce
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on ux research — each one lists the topics its interview covers.
See open roles