Six regions, six definitions of pipeline

The most expensive meeting in a lot of companies is the one where leadership argues about whose number is right. Not what to do about the number. Whose number is even real. I have sat in that meeting more than once, and it almost always traces back to a single unglamorous cause: the regions are each computing the basics differently, so nobody is comparing the same thing.

Six regions, six definitions of "pipeline." One counts everything with a dollar amount. One counts only deals past a qualification stage. One includes renewals, one does not. One dates by created, one by expected close. Each definition is defensible on its own. Together they guarantee that when the six roll up, the total means nothing, and everyone in the room can feel it even if they cannot name it.

The tell is the argument itself

You know you have this problem when the forecast call runs long and generates heat instead of decisions. People are not really disagreeing about the business. They are silently using different definitions and talking past each other, each certain their own report is the honest one.

That is the quiet cost. Not just wasted meeting time, though there is plenty of that. It is that leadership stops trusting any of the numbers, because they have learned the numbers do not reconcile. And once the forecast is not trusted, every downstream decision gets slower and more political, because it has to survive a debate about the data before it can even be a debate about the choice.

Why this is upstream of everything

This is what I look for when a team tells me their reporting does not drive action or their forecast is not believed. Usually the reporting is fine and the forecast math is fine. The definitions underneath them are not shared. You cannot build trusted reporting on top of metrics that mean six different things, any more than you can average six currencies without agreeing on an exchange rate.

It also compounds. Every new dashboard, every new region, every new leader inherits the ambiguity and often adds a seventh definition trying to fix it. The drift is not malicious. It is what happens when definitions live in people's heads instead of in one governed place.

The one-page fix

The good news is that the highest-leverage move here is also one of the cheapest in all of revenue operations: a metrics dictionary. One page. One canonical definition per metric. Open pipeline, forecast categories, activity, win rate, conversion, stage meanings, each defined once, owned by someone, and used everywhere.

It sounds too simple to matter. It matters more than almost anything else you can do in a quarter, because it removes the argument at its source. When everyone computes open pipeline the same way, the forecast call stops being a definitions fight and becomes an actual conversation about the business. The dictionary does not need a platform or a project. It needs a decision and an owner.

The foundational version, once the dictionary exists, is to push those definitions down into the systems themselves, a governed semantic layer so every report draws from the same source instead of each analyst rebuilding the logic their own way. But that is the upgrade. The dictionary is the fix, and you can start it this week.

What changes when the number means one thing

When there is one definition per metric, the reconciliation cycles disappear. The regions roll up to a total that actually means something. Leadership argues about the business instead of the data. And the forecast becomes something people are willing to stand behind, because for the first time they are all standing on the same ground.

If your forecast meeting is long and hot and never quite lands, listen for the tell. It is probably not a disagreement about strategy. It is six definitions in a room pretending to be one.

I write about making revenue operations legible, and I run a productized Revenue Engine Audit that scores single-source-of-truth alongside four other dimensions. A metrics dictionary is usually the first thing I hand a client.