The Experimentation Edge

Close every losing test with two questions: did it work for a granular segment, and is the idea worth further investment?

The biggest thing that gets a team testing is to just do it. Stop designing the perfect experiment and get something simple live to take away the mystery.

Documenting experiments in a centralized Wiki creates a growth flywheel: Fanatics' Wiki feeds their roadmap with iterations on already-built features, reducing tech dependency and accelerating velocity.

When you struggle to land a result, lead with the story of what the customer did, then bring the numbers.

Share losses as openly as wins. Wins build credibility, and losses build the psychological safety a testing culture runs on.

Democratize experimentation with a centralized platform and self-serve tooling; reset baselines regularly.

Reposition features around how users actually feel, not how you assume they should feel

Friction can increase revenue. Blocking the "view all" grid and forcing a style choice sent shoppers deeper and lifted conversion and revenue, because the extra click added value.

Chase estimates over a billion dollars of value from experimentation, and most of the lasting learning comes from the losing tests, not the winners.

Purge “anti-knowledge” by standardizing design, instituting cross-functional reviews, and only codifying learnings supported by repeatable data.

Test metrics before you test features — usage time could signal engagement or just mean your product takes too long to do its job.

Simplification has a limit. Removing too much can strip away the cues and context buyers actually need to decide.

Accept that being wrong is the point—experimentation only works when leadership embraces humility

Scale experimentation with AI: use Cursor desktop/cloud agents for parallel builds and visual QA; orchestrate docs/analysis via Claude; automate cleanups and reporting.

False negatives are more dangerous than false positives — they get institutionalized as "we tried that, it didn't work" and quietly kill good ideas for years.

Build the triad: pair an easy-to-use platform with training, top-down sponsorship, and clear launch processes.

A feature that fails early in a flow can succeed later; placement and timing often matter more than the idea itself.

Separate your two experimentation modes: high-volume CRO chases many small wins, while big uncertain bets deserve multiple shots to de-risk.

One centralized team of about 40 people tests every major change to Home Depot's $25B online business, serving 40–50 business teams with consistent hypothesis and analysis standards.

Twitch used geo-fenced experiments with matched markets and causal inference to measure true price elasticity, turning a feared pricing decision into a measured, accretive one.

Unblock teams: create a center of excellence for data science and enable rapid variants with AI-powered tooling.