Ben Labay and Ruben de Boer talk experimentation teams and change management

In a dynamic conversation, Ruben, an A/B testing and experimentation specialist, discusses the evolution and future of product team strategies. He notes a shift away from output-driven models, which prioritize feature quantity, to outcome-driven approaches that focus on the impact of those features. He emphasizes the importance of aligning experimentation processes with product teams, enhancing the overall quality and effectiveness of product releases.
Ruben argues that while centers of excellence are valuable, they're not the ultimate goal but a step towards a mature experimentation culture. These centers can improve tooling, structure, and testing quality but must be complemented by outcome-driven product teams to be truly effective. He also highlights the importance of automation in the early stages of running experiments, as it simplifies the process and allows teams to focus on learning and quality.
Furthermore, Ruben stresses the significance of creating a supportive environment for those responsible for experimentation. Tools like Slack and regular meetings can foster a team spirit, facilitating shared learning and success celebration. He also advises against imposing new tools and processes on product teams abruptly. Instead, he suggests aligning with existing practices and integrating experimentation organically.
Lastly, Ruben reflects on the potential drawbacks of automation, noting that while it's useful for repetitive tasks and safeguards, it's crucial to understand the process thoroughly before implementing automation fully. He concludes that successful experimentation and product development require a balance of structured strategies, team collaboration, and continuous adaptation to tools and processes.