Hey fellow indie hackers,
I want to share a critical insight about A/B testing that could save you from making costly mistakes in your product development journey.
We've all been there. You're running an A/B test, and in the first few days, your variant is crushing it. The temptation to end the test early and implement the changes is strong. But here's why you shouldn't:
I recently came across an A/B test with these final results:
Control: 11.31%
Variant: 11.31%
Improvement: 0%
Sounds unremarkable, right?
But here's the kicker: if you looked at the graph of this test, you'd see that the variant was winning by a landslide in the first few days!
This example perfectly illustrates why patience is crucial in A/B testing. Had the testers stopped early, they would have made a decision based on false data.
To quote Ronny Kohavi:
Twyman's Law is a statistical observation that states that data or figures that look interesting or different are usually wrong. It's also known as the idea that if data is too good to be true, it's probably wrong.
In A/B testing, early dramatic results are often misleading and tend to regress towards the mean over time.

As indie hackers, we often work with limited resources. Making decisions based on incomplete or inaccurate data can be costly in terms of time, money, and missed opportunities.
Remember, in A/B testing, patience isn't just a virtue - it's a necessity for accurate results and informed decision-making.
What's your experience with A/B testing? Have you ever been surprised by final results that contradicted early data?
P.S. For those interested in A/B testing, we're launching a free and lightweight A/B testing tool on ProductHunt soon! Here is the link: Mida PH Launch. Would appreciate your support if you find my content resourceful. 🙏