AB Testing
Description:
AB testing is a methodic approach to find out which version of the product is suited most for the project or might lead to higher conversions. Since both (or more) versions are compared to the similar sample of users, traffic value, etc., results of testing are great method to get a definite (and objective) answer if we cant decide which path to take.
Links:
https://en.wikipedia.org/wiki/A/B_testing
Keywords:
ux, ab, users
Motivation:
As I stated in description, A/B testing is a great method to distinguish between great and poor solution for any problem. Since evniroment is for both measured solutions same, we get an objective results out from testing.
Requirements/Prerequisities:
Analytical tools that supports A/B testing, such as Matomo.
Level:
concret: specific best practice (e.g. use microservice)
Application domain:
Medicine/Healthcare, Education (Technology enhanced learning), Data science (analysis & visualisation), Industry (Production), Mobility, Energy, Software engineering
Main phase:
Generic: Design/Plan, Development: Testing
Related literature:
https://en.wikipedia.org/wiki/A/B_testing
In which projects do/did you use this practice?
In none so far.
UX/UI Designer
3–5 years of experiences
Masaryk University
| 1. How do you rate the potential benefit for your projects? | 3 |
| 2. How often are you using that practice? | 2 |
| 3. What is the effort to introduce the practice in your project upfront? | 3 |
| 4. What is the effort to apply the best practice in your project daily basis? | 1 |
Questions 1, 3 and 4 (1 = Low, 5 = High)
Question 2 (1 = Never, 5 = Always)