Shipping a new feature is easy. Knowing if it actually improved anything? That's the hard part.

Many teams ship features based on intuition rather than evidence.

This makes it impossible to understand user behaviour or build confidence in product decisions.

Experimentation is the only reliable way for engineering teams to uncover the true impact of the features they ship.

In this talk, I’ll walk through the experimentation lifecycle from an engineering perspective - forming a hypothesis, adding instrumentation, gathering data, and learning from the results - showing how teams can embed this process into their feature release practices at scale.