Product: Product Page
Hypothesis
If we test a similar change on our product pages as rejected, we should be cautious
Test Results
Key Learning
Problem: This product has conversion optimization opportunities worth testing.
What was tried: rejected this UI change (Mar 18, 2021). Rejection suggests the change underperformed the control
Why it failed: The control was closer to optimal for this audience. Test more conservative variations next time.
How to Apply This to Your Site
This test showed that product: product page hurt conversions. The change was tested on a product page page in the travel industry. Avoid replicating this exact approach — instead, consider testing the opposite direction or a more subtle variation.
Before you test: Consider that layout tests typically require adequate traffic to reach statistical significance. Run your test for at least 2 full business cycles to account for weekly traffic patterns.
What Was Tested
Once again a/b tested an idea of surfacing the next available dates near their calendar picker. And once again the experiment looks like it was rejected just like previously.
Methodology
Build On These Learnings
Save your own experiments, spot winning patterns across your test history, and stop repeating what's already been tried.
Related Experiments
Checkout: Multiple Steps
Problem: Friction during the checkout process causes users to abandon right when they're closest to converting.
Product: Welcome Mat - Partial
Context: Capturing visitor attention on the product with modals or overlays is a balance between engagement and annoyance.
Content Page: Maybe Later on Content Page
Context: Key actions on the content page disappear as users scroll, creating a gap between intent and the ability to act.
Product: Least Or Most Expensive First
Context: How prices are displayed on the product directly influences perceived value and willingness to buy.