Real experiments. Real outcomes. Actionable patterns. Browse A/B tests with problem-to-solution framing, results, and recommendations for what to test next.
Test the variable users actually complain about — not the variable that's easiest to redesign. This test is a textbook case of treating form when the problem is content. Cross-brand qualitative research had consistently flagged three specific confusion themes: (1) pricing structure is opaque — users can't predict what they'll pay; (2) plan names are brand-driven rather than benefit-driven, so the names themselves don't communicate what the user is buying; (3) no side-by-side comparison — vertical layouts force users to scroll and remember instead of compare in parallel. Visual hierarchy is a presentation improvement; it does nothing about pricing opacity, naming clarity, or comparison difficulty. The test reached its planned sample size and produced a directionally-negative result at the noise floor — because organizing unclear content doesn't make the content clearer. The transferable insight isn't about visual hierarchy specifically; it's about the importance of mapping qualitative complaints to the test variable. If the user research says 'I don't understand what this plan costs,' the test should manipulate cost-clarity. If it says 'I can't tell these plans apart,' the test should manipulate differentiation. Layout tests are appropriate when the complaint is about layout — not when they're a default reflex.
Context: The primary call-to-action on the product isn't converting at its potential — design, copy, or placement may be the bottleneck.
Context: Friction during the checkout process causes users to abandon right when they're closest to converting.
Context: The primary call-to-action on the product isn't converting at its potential — design, copy, or placement may be the bottleneck.
Context: Multi-step processes on the home landing can overwhelm users if they can't see how far along they are or how much is left.
Context: Each additional form field adds friction to the checkout, increasing the chance users abandon before completing their submission.
Context: Users arriving at the product can't efficiently find what they're looking for, increasing bounce rates.
Context: Visual emphasis on the general may not be drawing attention to the right elements — size, color, and contrast guide the eye.
Context: Friction during the checkout process causes users to abandon right when they're closest to converting.
Context: How prices are displayed on the shopping cart directly influences perceived value and willingness to buy.
Problem: Visual elements on the listing aren't doing enough to communicate value, build trust, or guide users toward the next step.
Context: Users on the general need validation from others before committing — without visible proof of success, they hesitate.
Context: Friction during the signup process causes users to abandon right when they're closest to converting.
Context: The primary call-to-action on the product isn't converting at its potential — design, copy, or placement may be the bottleneck.
Context: Multi-step processes on the product can overwhelm users if they can't see how far along they are or how much is left.
Problem: How prices are displayed on the pricing page directly influences perceived value and willingness to buy.
Sticky mobile CTAs can compress time-on-page meaningfully (~15% faster) without sacrificing engagement signals — users converted at a directionally higher rate AND moved through the page faster, suggesting reduced hesitation rather than rushed clicks. The result was shipped via 90/10 holdout monitoring rather than traditional 50/50 A/B inference — the high baseline (~85%) and limited mobile traffic made full A/B underpowered, so the team chose a holdout-validated rollout as the deliberate methodology. Bayesian P(variant > control) was ~0.90, supporting the directional ship call. Worth noting: external research flags sticky CTAs as context-dependent — they help when the primary action is buried below the fold, but can hurt on shorter pages where the original CTA is already visible.
Context: Users on the checkout need validation from others before committing — without visible proof of success, they hesitate.
Ambiguity > absence. A vague benefit callout can create more friction than no callout at all: visitor diagnostics showed users were drawn in by the badge (time-on-page up, bounce rate down) but exit rate rose and FAQ-section attractiveness spiked — a signature of users searching for answers and not finding them. The same concept won at a sister brand whose variant used descriptive benefit-framed copy ("we'll help you find the right plan if this isn't a fit"); the variant in this test used short labelled-badge copy that raised more questions than it answered. The lesson is not that benefit guarantees fail — it's that surfacing one with insufficient context can backfire by introducing uncertainty the page doesn't resolve.
Problem: The primary call-to-action on the general isn't converting at its potential — design, copy, or placement may be the bottleneck.
Build on what's already been learned. Save your own experiments, surface winning patterns, and make every test count.