Validation method: A/B testing across platforms
To validate the cognitive load hypothesis, I worked with our lead data analyst to design a controlled A/B test comparing the original experience against my optimized designs.
Test structure
Control (A): Original payment flow
Variant (B): Optimized for cognitive load
Platforms: Mobile app + Responsive Web
Key metric
Deposit conversion rate
Percentage of trial users who successfully add funds
A/B Testing Framework Limits
Working within the existing testing framework meant several variables were locked:
Cannot change
- Time users had to make a choice (1 minute)
- Number of options presented
- Backend logic for price bucket options or min/max custom amounts
My strategic bet
Focused on mobile-specific UI/UX optimizations requiring no backend changes while maximizing behavioral impact—specifically reducing cognitive load via mobile-native design patterns and streamlined information architecture.
Then a change of scope happened
This constraint analysis justified our VP of Product changing the scope where this key moment could (and should) be tested everywhere via an A/B test.
However, I was ready for this scope change because I was already thinking about how we could easily tweak these designs to scale our approach.