
Sign up to save your podcasts
Or
A/B testing is a pretty common technique in tech companies these days. That said it’s often overlooked as a form of design feedback.
A/B testing is handy. When you have enough traffic to run the test. In a reasonable amount of time. You’re testing just one single change versus another. You have the right infrastructure to run the test. And you have at least a week to run the test.
What are some common failure points for A/B testing?
Why should I A/B test?
The benefits of A/B testing is that you’re comparing apples-to-apples in the best possible way. You’re comparing one version to another in real time.
A/B testing is the best. And perhaps only way to know for sure the real impact of a change that you’re going to make.
So when should you AB test?
A/B testing is a pretty common technique in tech companies these days. That said it’s often overlooked as a form of design feedback.
A/B testing is handy. When you have enough traffic to run the test. In a reasonable amount of time. You’re testing just one single change versus another. You have the right infrastructure to run the test. And you have at least a week to run the test.
What are some common failure points for A/B testing?
Why should I A/B test?
The benefits of A/B testing is that you’re comparing apples-to-apples in the best possible way. You’re comparing one version to another in real time.
A/B testing is the best. And perhaps only way to know for sure the real impact of a change that you’re going to make.
So when should you AB test?