Define Metrics That Endure Reorganizations

Reorganizations are a fact of life in business. They're disruptive. They often break reporting.

Data teams feel this acutely. Metrics defined for one organizational structure suddenly make no sense in another.

This isn't about the data itself, but about how the metrics were defined in the first place.

The Problem with Organizational Dependencies

Many metric definitions implicitly rely on the current organizational chart.

Example. 'Sales Qualified Leads from the EMEA BDR Team.' What happens when the BDR team splits into two, or gets absorbed by marketing?

The definition is tied to a specific team and its current function. When that team or function changes, the metric breaks.

It requires immediate redefinition, often with retrospective data needing adjustment, which is a mess.

Build for Longevity: Focus on Process and Source

We advocate for definitions that stand independently of transient organizational structures.

Focus on the process generating the data, not the team performing it. This makes the definition more robust.

Instead of 'Sales Qualified Leads from the EMEA BDR Team,' define it as 'Leads marked as 'SQL' in Salesforce, originated from activities within the EMEA region, prior to opportunity creation.'

This definition holds regardless of who marks the lead or which team covers EMEA. It describes the state and origin in the system.

Define the data source and specific fields. This removes ambiguity.

• Metric Name: Active Users
• Definition: The count of unique user IDs that have performed at least one 'login' event within the last 30 days.
• Source System: Product Analytics Database, `events` table
• Key Fields: `user_id`, `event_name`, `event_timestamp`

This structured approach ensures that when a new team inherits responsibility for 'Active Users,' the definition is clear, verifiable, and doesn't require a committee meeting to interpret.