There is a common sequence in enterprise analytics projects. Someone decides on a platform — Adobe Analytics, GA4, or another tool — and implementation begins almost immediately. The measurement design conversation, if it happens at all, comes later.

This sequence is backwards. And it is the root cause of most data trust problems we encounter.

What measurement design actually means

Measurement design is not about deciding which events to track. It is about defining what decisions your organization needs to make, and working backwards to understand what data those decisions require.

It means answering questions like:

  • What does success look like for this product or campaign — and how will we know when we've achieved it?
  • Which user behaviors are leading indicators of the outcomes we care about?
  • How will different teams use this data, and what level of granularity do they need?
  • How will this data connect to experimentation, personalization, and downstream BI?

Only once these questions are answered does it make sense to talk about implementation.

What happens when you skip it

When implementation precedes measurement design, teams end up with data that reflects what was easy to collect, not what was important to know. eVars and props get assigned arbitrarily. Event names proliferate without governance. Each new product launch creates new tracking that doesn't connect to existing data models.

"We have all the data we could ever want. We just don't trust any of it."

This is not an uncommon sentiment. It is almost always the product of implementation without design.

The cost of retrofitting

Retrofitting measurement design onto an existing implementation is expensive and disruptive. It typically requires re-tagging, data layer changes, governance conversations that should have happened years earlier, and a period of parallel tracking where old and new data coexist without clear guidance on which to use.

The cost of doing it right the first time is a few weeks of structured thinking before implementation begins. The cost of not doing it is years of reconciliation and eroded trust.

Where to start

The simplest starting point is a measurement brief: a short document that defines the business objectives, the key decisions that need to be supported, the user behaviors that matter, and the governance principles that will govern how data is collected and used.

This document does not need to be perfect. It needs to exist, and it needs to be agreed upon before a single tag is written.