Ben White
Strategic systems

Building a shared measurement standard

Role: Product Design Lead, 2025

Goal: Replacing anecdote with evidence in product decisions

Product teams can’t make well-informed decisions without data about how people use their products. Across the product teams I worked with, behavioural data wasn’t being collected consistently, so decisions about product direction often relied on anecdotes.

I started and led an initiative to change that - a standard event framework that gives every team the same way to plan, name and capture behavioural events. It matters more as our products add AI capabilities, because understanding how people work with AI-assisted features depends on measuring the right things from the start.

The impact

  • A shared picture of the gaps Mapping how products tracked events gave teams a clear view of what was being measured.
  • One standard across teams Two product teams now plan, document and capture events in the same way, so their data can be compared and journeys followed across products.
  • A foundation for measuring AI features Teams have a consistent way to measure behaviour that they can extend as AI-assisted features are introduced, rather than starting from scratch each time.

Data as an afterthought

In teams focused on delivery, measurement is easy to defer. Data requirements were often pushed back to protect release dates, so when someone needed an insight, the tracking that would have answered it hadn’t been built. Teams were also tracking events in different ways, which made it hard to compare products or follow a journey from end to end. And as parts of our products became less linear, counting clicks wasn’t going to provide the information needed.

Making the case for measuring early

The framework itself was the simpler part. The harder work was persuading teams that planning measurement at the start of a piece of work saves time later, rather than slowing delivery down. I mapped how each product was tracking events at the time, which made the gaps and inconsistencies visible to everyone, and used that to agree a shared direction with Product and Engineering. From there I wrote a three-phase plan and a north star for what good measurement should look like.

Very nice. I’m expecting more teams to adopt this model next year!

— Design Director

A shared standard

The result is a standard event framework and template that teams use to document the events in a journey. Adoption is being phased team by team - with the aim that every team measures in the same way, so decisions across the area are based on how people actually use the products.

What did I do on this project?

  • Started the initiative Identified the gap in how behavioural data was collected and proposed a standard way of doing it, as part of a wider data vision.
  • Mapped the current state Audited how events were being tracked across every product in the area, giving teams and leadership a shared picture of the gaps.
  • Wrote the framework and plan Wrote the standard event framework and template, a three-phase rollout plan, and a north star for what good measurement looks like.
  • Brought Product and Engineering together Ran cross-functional workshops to agree the approach and the measures that matter most.
  • Supported teams through rollout Worked with each product team as they adopted the framework, and refined it based on the problems they ran into.