Too Long; Didn't Read
So far in <a href="http://bit.ly/2NCv9b1" target="_blank">this series</a>, I’ve highlighted several pitfalls on the path to product experimentation. We’ve seen how some common mistakes can <a href="https://blog.optimizely.com/2018/05/09/experimenting-without-enough-traffic/" target="_blank">slow down your testing</a>, <a href="https://blog.optimizely.com/2018/05/25/measuring-driving-experiment-velocity/" target="_blank">stall your velocity</a>, <a href="https://blog.optimizely.com/2018/05/17/tricked-by-statistics/" target="_blank">send your team in circles</a>, or <a href="https://blog.optimizely.com/2018/05/03/experimenting-with-wrong-metrics/" target="_blank">lead you down the wrong path entirely</a>. But what if you already have a budding culture of experimentation and you’re seeing a steady stream of successful tests?