5 tips before exercising your AB testing

1. Before an AB testing, note down your question to test.

Make sure your assumption to test is agreed upon among the team and noted clearly somewhere all your team members could easily notice before and after the testing journey.

2. Avoid double-barreled questions and questions with multiple factors involved.

I mean, yes, you sure can test your current design with an entirely different design that has different features, layout, and flow. However, be cautious about learning little at the end of the test and obtain a pure outcome statement: it is a win or loss. Make sure the test has an only one-factor change in your control group will help your team to focus on the correlation to analyze.

  1. Adding a trust element will cause a positive perception of a company.
  2. A positive perception about a company will drive the action to subscribe.

3. Be prepared for the learning, not win.

When a team marches toward learning, they proceed as they continuously learn something. When a team is expecting a win, they get shocked and can halt easily when the result turns out negatively (unexpectedly).

4. Plan ahead.

If this doesn’t work out, then what’s next? If works out, what’s next? AB testing would benefit from being regards as one small step before a long iterating journey.

5. Testing apple to apple.

One common mistake while designing an AB testing trail is not actually bringing the original version together with the new variation. The benefit of having two versions side by side will guide your team to see clearly what is really being compared against.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store