Live Prompt: High Drop-off on the Cart Page Itself
An interviewer gives you a new live prompt: "Same e-commerce app. This time the data shows the drop-off isn't at payment — it's on the Cart page itself, before checkout even begins. 45% of users who add at least one item to their cart never click 'Proceed to Checkout' at all. You have 20 minutes."
Work through this the way the payment-step case study modeled:
- What clarifying questions would you ask before proposing anything, and why does the fact that this drop-off happens before checkout (not during it) change which questions matter most compared to the payment-step case?
- Generate 4 distinct, falsifiable hypotheses for why users would abandon at the cart page specifically, each grounded in a different concept (pricing/IA, trust, content, interaction design).
- Given no further data than what's in the prompt, which hypothesis would you prioritize first, and justify the choice the same way the case study justified its own prioritization — by reasoning about what's structurally specific to this step.
- Sketch, in words, the one or two most important changes you'd make, tying each to a named design principle.
1. Clarifying questions, and why the framing shifts
Because the drop-off is before checkout begins, questions should probe what's visible on the cart page itself rather than what's revealed deep in a multi-step flow: "Is minimum order value, free- shipping threshold, or estimated delivery date shown on this page?" "Is this drop-off higher for first-time visitors versus returning customers, which would point to a trust or unfamiliarity problem rather than a pricing one?" "Is the 'Proceed to Checkout' button visible without scrolling, on both mobile and desktop?" "Is there a persistent 'save for later' or wishlist option, or is cart the only place items can sit — because some cart abandonment isn't a breakdown, it's users intentionally cart-parking items they're not ready to buy yet, which is a different problem entirely and not a UX defect at all." That last question matters specifically here in a way it didn't in the payment-step case, because cart abandonment before checkout begins is far more likely to include a benign "I'm just comparing prices" segment than abandonment mid-payment, where someone has already committed enough intent to enter card details.
2. Four distinct hypotheses
- Unexpected minimum-order or shipping-threshold friction (pricing/ IA): the user discovers only on the cart page that they're $12 short of free shipping and leaves to "add more" but never returns — a structurally cart-page-specific friction.
- Low trust at first commitment point (trust): this is the first moment the user is asked to commit real intent (as opposed to idly browsing), and if the cart page lacks return-policy or security messaging present elsewhere in the site, hesitation peaks here.
- Unclear or missing next-step affordance (interaction design): if "Proceed to Checkout" is visually similar to "Continue Shopping" or buried below saved-for-later items, users may not register it as the primary action at all.
- Legitimate price-comparison behavior, not a UX defect (content/ behavioral): some fraction of cart-adds are users using the cart as a wishlist or comparison tool with no intent to purchase yet — this hypothesis, uniquely, implies the "problem" may be partly a measurement-framing issue rather than a flow defect.
3. Prioritization
The strongest first candidate is the unexpected minimum-order or shipping-threshold friction hypothesis, because it — like the payment case's "surprise costs" hypothesis — can only manifest at the specific point full cart contents and their total are visible together, which is the cart page itself, not earlier product pages. The trust hypothesis is plausible but harder to distinguish from the benign "just comparing" hypothesis without more data (e.g. return- visitor cart-completion rates), so it's demoted to second pending that data. The legitimate-comparison-behavior hypothesis should be raised explicitly to the interviewer as worth ruling out with a segment cut (new vs. returning, or a session-count filter) before treating the whole 45% as a flow defect — proposing to fix 100% of a number that may only be 60% "real" abandonment would be a measurement mistake, not a design one.
4. Sketch of the top changes
Surface shipping-threshold and minimum-order information as early as the product page and again, prominently, on the cart page itself ("You're $12 away from free shipping" as a persistent, non-modal banner) — an application of progressive disclosure again, giving the user the information before the point where it becomes a frustrating surprise rather than only when they'd otherwise leave. Second, make "Proceed to Checkout" the single unambiguous primary action via clear visual hierarchy (larger, higher-contrast, positioned above saved- for-later or recommended-product content that currently competes for attention) — the same visual-hierarchy principle used in the payment-step case to differentiate guest checkout from account creation, applied here to differentiate the primary conversion action from secondary browsing content.
Share this question