64 products left, but today eppo
Hi friend 👋,
In my opinion, "A/B testing" is one of the most overused terms in the field of software product management. When it comes to really putting it into practice, however, everyone has trouble despite everyone else's enthusiasm for talking about it. Perhaps the clue is already in the name. People often think of A/B testing in terms of two groups, A and B, each of which sees a slightly different version of the test material. Even during the interview process with a candidate, how they create the A/B testing demonstrates how well the individual understands scientific thinking processes. Learning statistics and understanding what constitutes a "statistically important" shift are prerequisites for conducting an A/B test. You should be aware of the current flow and take precautions by selecting an adequate sample size for your test. When choosing a control group, it's best to use deep segmentation in addition to randomization. Many more examples might be given.
I've attempted over the years to invest more into A/B testing, but the upfront costs of doing it right were always too high. I am aware that there are numerous tools available that allow you to perform basic frontend tests by interacting with the UI by means of a chrome extension or something similar; however, it is always challenging to do so with feature flags and all the new goodies you have. Consider how often you encounter a new user interface in Twitter or Instagram while your friends were seeing something completely different. That doesn't happen with the trendy new product from a buzzing startup that everyone seems to be using these days. Because these tests are all done by large setups with a team behind them. Today's product has the potential to change that.
Today, eppo is our product.
The video above explains their CUPED method, which is the most fascinating aspect of testing with eppo. It removes all of the noise from your data points, allowing you to get to the true results faster and with less volume. It has a direct impact on the amount of work required to do proper testing. So, even if you have fewer employees than large corporations, you will be able to conduct testing. The journey with eppo begins with feature flags, and once you're comfortable using them for all new features, you may perform tests. It is a paradigm change for product teams.
The details are what will take your team to the next level. Your level of success is determined by how you operate and how deeply you think. And it is one of these things that distinguish between good and great teams. You should give eppo a shot, and please let me know if you already use something similar.
We’ll talk again tomorrow.