Two teams, one number, two answers, and a monthly meeting where everyone argues about whose report is right instead of what to do.
Date basis: one report uses created date, the other uses close date, so the same deal lands in different months. Filters: one excludes a record type or a pipeline the other includes. Definitions: both say qualified and mean different things. Grain: one counts contacts, the other counts companies.
The instinct when two reports disagree is to build a neutral one. Now three numbers exist and the argument has more surface area. The only thing that resolves it is agreeing what the metric means and then deleting whatever contradicts it.
One page, one definition per metric, naming the field, the filter, the date basis and the owner. It sounds bureaucratic until the first month where nobody argues.
Each team built the measure it needed at the time, and with no written definition and no owner, those drifted apart quietly. One document fixes it, signed by all three leaders before any dashboard is touched.
| Element | What it says | Why it matters |
|---|---|---|
| The field | Which field, on which object | The concept is not enough |
| The filter | Stages, record types, owners, anything excluded | Where most drift lives |
| The date basis | Created, closed, stage entry or modified | The biggest single cause of disagreement |
| The owner | One named person who can change it | A committee produces drift |
| The review date | When it gets checked again | Definitions decay as the business changes |
| Who signed it | Sales, marketing and CS leaders | Makes it stick |
Dashboards are downstream. Rebuild them from the agreed definitions rather than patching the existing ones, because a patched report carries its old assumptions invisibly.
Usually different date bases, different filters, different definitions of the same stage, or one counting contacts while the other counts accounts.
Revenue operations, with written sign off from every team that reports on them.
Only after the definitions are agreed. A new dashboard on top of an unresolved disagreement becomes a third opinion.
A written definition per metric, an owner, and a review when the sales motion changes. Most recurrences trace back to a change nobody propagated.
Because each team built the measure it needed and no written definition existed. The usual differences are the date basis, which object is counted, and which stages are included.
One document, per metric: the field, the filter, the date basis, the owner and a review date, signed by all three leaders before any dashboard is rebuilt.
Because each team built the measure it needed and no written definition existed. The usual differences are date basis, which object is counted, and which stages are included.
One document, per metric: the field, the filter, the date basis, the owner and a review date, signed by all three leaders before any dashboard is rebuilt.
All of it free.
Leave an email and I will reply myself, usually the same day. No sequence, and no calendar link unless you ask for one.
Would rather just book time? Here is the calendar.
We use browser storage to run the site and to understand how it is used. You can accept all or necessary only. See our privacy notice.