Having spent years leading AI product teams at places like Google and Amazon, I saw firsthand how the best in the world operate. They don't use the generic frameworks you read about online. I'm sharing the internal playbook we used to launch AI products that reached millions of users.
What I've Learned From 98 Companies
A few patterns in A/B testing come up again and again.
The founders who handle A/B testing well understand that the market doesn't care about your roadmap.
Why Most Approaches Fail
Many common approaches to A/B testing are flawed at the root.
The root cause is usually one of three things:
Copying what big companies do without understanding why they do it. What works for Google doesn't work for a 10-person startup.
Over-engineering the solution when a simple approach would work better. I've seen teams spend six months building something that could have been done in two weeks.
Ignoring the human element. Technology is the easy part. Getting people to actually use it is where the real challenge lives.
Lessons From the Trenches
I want to share a few specific lessons I've picked up over the years. These aren't theoretical. They come from real companies, real failures, and real successes.
Lesson 1: The best time to start thinking about A/B testing was yesterday. The second best time is now. Don't wait until you have the perfect plan.
Lesson 2: Hire for attitude, train for skill. The best people at A/B testing are rarely the most technically gifted. They are the most curious and persistent.
Lesson 3: Your competitors are probably getting this wrong too. That's your opportunity. While everyone else is following the same playbook, you can zig when they zag.
This connects to broader themes around a/b testing ai, growth hacking, case study that I've been thinking about a lot lately.
What's Next
Best practice in A/B testing is changing fast. What worked last year might not work next year. That's both the challenge and the opportunity.
My advice: stay curious, stay humble, and stay close to the people who are actually doing the work. Read less thought leadership and do more experiments. Talk to fewer consultants and more practitioners.
If you're building in this space, the best time to get A/B testing right is before you need to. Don't wait for a crisis to force your hand.
I'll keep sharing what I learn. This stuff matters too much to keep to myself.
Frequently Asked Questions
Q:What experience informs this perspective?
This perspective comes from over a decade of building companies in Silicon Valley, two successful exits (RemoteTeam to Gusto, MovieLaLa to Gfycat), and investing in 234 startups including Anthropic, OpenAI, and Scale AI. I write about what I've lived.
Q:How can I apply this thinking to my own situation?
Start by identifying the core principle behind the opinion, not the specific example. Then ask yourself: does this principle apply to my context? If yes, test it in a small, low-risk way before going all in.
Q:How has this view evolved over time?
My thinking on most topics has changed significantly over the years. Early in my career, I held many conventional views that experience proved wrong. I try to update my beliefs when the evidence changes.