A | B Testing

A/B testing is an important part of a product lifecycle, is part of the iterative process and tends to provide solid data which designers and developers can appreciate the most, as it helps reduce some wiggle of a other way balancing act.

"in this age of digital saturation, a successful product most likely is one that does something complicated in a simple way"

How can we measure usability?

Usability can be measured behaviorally and attitudinally. ISO defines usability and user experience design as “designing products to be effective, efficient, and satisfying.” Let’s break down each of these factors:

Effectiveness: Did the users achieve their goals?

Ways to measure: errors rates, quality of completion, and accuracy
Efficiency: How much energy did it take for users to get there?

Ways to measure: time to task completion
Satisfaction: What are the users’ attitudes toward the system?

User testing is done in order to:

Understand user needs
Validate product ideas
Generate concepts

As a part of its methods, user testing can involve:

Surveys
Interviews
Card sorting
Heuristic evaluation
Contextual inquiries
Focus groups
Quantitative methods such as A/B testing

Usability testing is done in order to:

Evaluate a product/service
Improve functionality
Test a concept or product against user expectations

How to get the most of your A/B testing

classify and limit the amount of users, single feature/change test tends to provide the most solid data focus in features that matter most and that are part of the defined goal to achieve in the current iteration cycle.