I recently gave a talk at the La Product Conf Paris with Julien Bizet, Head of Experimentation at Fnac Darty, about the "top five reasons" why product teams avoid experimentation. I asked Product Leaders to rank these reasons from most to least accurate, and the top reason mentioned was: "It will slow down my delivery." To all product leaders: if you truly care about the impact of the features your product teams releases to your customers, you should see experimentation as an essential skill set for any Product Manager today, not just a nice-to-have. By experimentation, I mean not only A/B testing but also everything we do to ensure the successful release of new features and enhancements for our users. Think of experimentation as a comprehensive product methodology that includes feature flagging, progressive rollout, and targeted delivery methods. So, how do you get started with it? In this article, I share a few pieces of advice for Product Managers. Let me know your thoughts! #abtesting #experimentation #product #featureflag
Really worth reading, I'm grateful you take the time to write stuffs 🙂
💯 looking forward to discussing this topic with you Fred!
Great read, Fred! Completely agree on feature flagging's potential being so much more than just an if/then condition.
Experimentation for digital teams that care about CX
2moGreat article Frederic. It's imperative that product organisations are measuring their success based on the validated outcomes of the features they're launching, rather than trying desperately to meet last quarter's delivery rate. Enabling feature flagging and experimentation becomes a much easier conversation when you can demonstrate that you've saved/gained revenue.