Thinking about making a change to your website or app?  But will the change be better or worse?  What do you do?  Determining if a change in software is good or bad is done as a controlled experiment called A/B testing.   Our guest writer, Leona Henryson is a seasoned blogger and UX designer and discusses A/B testing in this article.

A beginner’s guide to A/B testing

To be at your most effective, you need to know whether a change you’ve made is actually beneficial or not. Now you can simply guess, assume, or judge based on your own observations. All of those choices come with problems, however. And that is that they’re not very accurate.

A much better way to know what’s actually going on is by comparing what you had with what you have and seeing how the numbers compare. This will give you a far more unbiased and honest idea of what’s going on, which will then let you make far better-informed decisions about how to proceed.

Tests that let you work in this way are like turning on the lights in the darkness. Suddenly you can understand the landscape and stop stumbling about without knowing where you’re trying to go.

Keep reading this article on Apptology