Shifting Your Team’s Perspective

Once you know why your team is resistant to A/B testing, you can then focus your energy on framing the benefits and process so it addresses their concerns. Let’s look at how to manage a few common reasons teams are not implementing A/B tests on their product.

Prototyping for Quicker Iterations and Insights

Let’s say your team is worried about the extra time it takes to evaluate product ideas. Is it quicker to ship your code straight from development to production for all your users to engage with? Yes, definitely. However, there are ways you can combat this concern.

If this is the case, lean into building prototypes. Aim to build a minimal version of the new feature or change, and A/B test that to avoid over-engineering ...

Get Practical A/B Testing now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.