Articles · Data Foundation

Three teams, three numbers, and why the dashboard will not settle it

The same customer usually exists several times across your systems, and each one resolved that ambiguity differently.

Data foundation practice · 5 min read ·

The pattern is familiar. Sales operations reports one attainment figure, the brand team reports another, the field reports a third, and a new dashboard gets commissioned to reconcile them.

Underneath, the same prescriber exists three times across CRM, claims and the pharmacy feed, affiliated to two accounts and one practice that dissolved last year. Each system made a reasonable call about which record is real. None of them logged the decision, so all three reports are internally consistent and mutually incompatible.

How one unresolved record travels

The path it takes
1
Targeting

The customer lands in the wrong territory, so the coverage plan starts out slightly wrong.

2
Attainment

The coverage plan feeds attainment, the incentive follows, and an appeal gets raised.

3
Promotional response

Attainment enters the response model as a control, so the marketing read inherits it.

4
Confidence

By the time anyone traces it back, three teams have stopped treating one source as authoritative.

What resolution typically moves
+21 ptsMatch rate lift on a first pass
-42%Incentive appeals per cycle
310 hrsReconciliation time returned monthly
A governed data layer is less a platform decision than an agreement about whose number stands when two teams differ.
  • Resolve identity first — customer, account, affiliation, and the journey where consent permits.
  • Give every definition a named owner, so a change is a decision rather than a discovery.
  • Publish the match rate beside the performance figure, so confidence travels with the number.
  • Re-run resolution on a schedule; a spine built once loses meaningful accuracy inside two quarters.
Data foundation practicePrecisionNeXT