Finance counts an active customer as an account with a billable event in the period. Product counts it as an account with a login in ninety days.
Both definitions are in production. Both are correct. The two numbers differ by a factor that shows up in a board deck, and someone has asked you to sort it out.
The instinct is to convene the teams and pick a winner. That instinct is the failure mode, and it's worth understanding why before the meeting gets booked.
Why picking a winner loses
The losing team keeps their number. They have to: it drives a review they own, a target they're measured on, or a report a regulator expects in the shape they've always sent it.
So the definition doesn't disappear. It moves somewhere you can't see, into a spreadsheet, a local BI model, or a retrieval configuration. You have converted a visible disagreement between two governed definitions into an invisible one between a governed definition and a shadow copy.
That is strictly worse. The disagreement was at least legible before.
There's a second cost. A team that loses a definitional ruling stops bringing you the next one, and the practice needs those disclosures more than it needs the ruling.
Most conflicts are one of three kinds
Sort before resolving, because the three have different answers and only one of them is genuinely contested.
Same word, different scope. The most common. Finance means active for billing, product means active for engagement. Neither is wrong. Both are badly named.
Same word, same scope, different rule. Both mean billing, and they disagree about whether a refunded transaction counts. This one has a right answer, and someone in the business knows it.
Same word, and one is stale. The rule changed a year ago, one system inherited the change and the other did not. This looks like a conflict. It is a drift incident.
Ask one question to sort them: does each team's rule serve a different decision? If yes, it's the first kind. If no, and both can state their rule precisely, it's the second. If one team's rule surprises the person who supposedly owns it, it's the third.
Scope conflicts: rename both, deprecate neither
The resolution is a naming decision rather than a ruling on who is right.
Neither team keeps the bare word. Finance gets billing active customer. Product gets engaged active customer. Each gets a named owner, its own binding, and its own version history. The unqualified term is retired from the estate and, if your tooling allows, made unresolvable so a query for it fails loudly rather than picking one.
That last part is what makes this stick. As long as the bare word resolves to something, systems will keep using it, and you will hold this meeting again next year.
Both teams keep their number, which is why they cooperate. What they give up is the claim on the generic word, which is the part neither one actually needed.
Rule conflicts: escalate to the decision, not the teams
When both mean the same thing and disagree about the rule, the resolution runs through whoever owns the business decision, and your job is to make the choice legible rather than to make it.
Put one page in front of them: each rule stated precisely, the population each includes, the numeric difference on a recent period, and which reports and obligations currently run on each. Numbers settle these conversations quickly, because the two rules stop being philosophical positions and become a gap someone recognizes.
Then record the ruling in the change history with the decider's name on it. A definitional decision with no attribution is one personnel change away from being reopened.
Stale conflicts: run the incident review
This is not a definitional conflict, and treating it as one wastes a meeting and embarrasses someone.
Run it as a definition incident. Which dimension failed, which stage failed, root cause in one sentence, estate fix or consumer fix. The template is on the cadence page. Usually the answer is that a change shipped without an impact list and one consumer never inherited it.
Deprecation is a project with a date
Whichever path resolved it, a definition is now on its way out, and this is where the work usually stops too early.
Deprecating a definition means: mark it deprecated with a retirement date, publish the list of consumers still reading it, notify each owner with the replacement named, and confirm zero consumers remain before you remove it. Then remove it.
A deprecated definition with no retirement date is a live definition with a warning label. Estates accumulate four versions of revenue exactly this way, one reasonable deferral at a time.
Sweep these quarterly. It belongs in the same review as the rescore.
What to write down while it is fresh
Every resolved conflict should leave four things behind: which kind it was, the resolution, the person who decided, and the date. That record is what stops the same argument recurring, and it is also the most useful evidence you will have the next time an auditor asks whether definitional change is controlled.
Record a fifth: the reason each rule existed. A future reader who understands why finance excluded refunds will not propose including them again.
The pattern underneath
Most definitional conflict is a naming failure that has been running long enough to look like a disagreement.
Two teams needed two concepts. The estate offered one word. Everything after that was the predictable consequence, and the fix is almost always to add a word rather than to remove a team's number.
Written by the team at MetaKarta and released under CC BY 4.0: free to use, adapt, and republish with attribution.
