3 ms·
He addresses exactly that point with False Premise #2. It really depends on how you use A/B testing, if you only do it to test small incremental changes then ye
by zaguios 13y ago
He addresses exactly that point with False Premise #2. It really depends on how you use A/B testing, if you only do it to test small incremental changes then yes, you're correct, but there's nothing stopping you from testing two totally different features/designs with A/B testing.
- varelse 13y agoTo which I'd respond that from personal experience, on a large corporate project, it's difficult to get authorization to do just that. And even so, testing just two different designs is rolling the dice rather than exploring feature/design space in search of a new optimum. As examples, I personally hate what's happened to the android clients for GMail and Google Maps. The former seems a victim of incremental change while the latter seems the consequence of a radical redesign that hit me out of the blue in the middle of trying to drive somewhere when I was already late.
- CharlesW 13y ago"And even so, testing just two different designs is rolling the dice rather than exploring feature/design space in search of a new optimum." A/B testing doesn't force you to innovate through radical design changes — you can use it just as easily for incremental improvements.