The Reconciled Customer Count That Nobody Trusts
A retail bank's Chief Data Officer is told by the CFO that three reports circulated in the same week show 4.12M, 4.38M, and 4.61M active customers. Each report was built by a different team: Finance uses the general ledger's customer-of-record flag, Marketing uses the CRM's active-account definition, and Risk uses any customer with a transaction in 90 days. The CDO has one data steward, no enterprise glossary, and a 6-week deadline before an investor disclosure. Executive sponsors disagree about which number is 'correct' and two of them have escalated to the CEO. A vendor has offered to sell a 'golden customer record' tool for $400K with a 9-month implementation.
1. Diagnose the root cause and recommend what the CDO should deliver in the 6 weeks. Justify your prioritization.
Read the worked answer
Diagnosis. This is not a data-quality defect; it is a definitional and ownership problem. Three legitimate business definitions are being conflated into one contested metric. The 490K spread across reports (4.12M to 4.61M) is consistent with different inclusion rules (GL flag vs. CRM status vs. 90-day activity), not with random error. Buying a golden-record tool would not resolve it because the tool cannot adjudicate which definition is authoritative - that is a governance decision.
What to deliver in 6 weeks:
- A metric definition for 'active customer' with an explicit, testable rule (e.g., has an open product and a qualifying transaction in 90 days), signed off by CFO, CMO, and CRO. Documented as the enterprise definition.
- A reconciliation bridge showing how each of the three legacy numbers maps to the new definition, so each team can explain its number to its own stakeholders. The bridge converts a political fight into arithmetic.
- Named data owners for the source systems feeding the metric, with accountability for the rule.
- A disclosure memo stating which definition underpins the investor number and why.
Prioritization rationale. The deadline is a disclosure event, so the binding constraint is a defensible, documented definition plus traceability - not a 9-month platform. Deferring the vendor decision is correct: revisit after the definition is stable, because tooling requirements depend on the agreed rule. The glossary can start as a single-metric entry; a full enterprise glossary is not achievable in 6 weeks and is not what the CEO escalation requires.
2. The CMO refuses to adopt the enterprise definition, arguing Marketing's number drives campaign spend and changing it would 'reset the pipeline.' How should the CDO proceed?
Read the worked answer
Reframe from compliance to consequence. The CDO should not demand adoption on authority; they should quantify what the divergence costs. If Marketing's 4.61M includes customers with no transacting relationship, campaign ROI is being computed on an inflated base - meaning cost-per-responder is understated and budget is being misallocated. Presenting that arithmetic to the CMO (and CFO) changes the conversation from 'give up your number' to 'your number is overstating your performance.'
Practical resolution:
- Allow contextual variants with mandatory disclosure: Marketing may use a broader 'reachable customer' definition for campaign targeting, provided it is labeled distinctly and never presented as the enterprise active-customer count. This is standard practice - one governed metric, documented variants.
- Require the variant to carry the same reconciliation bridge so any number can be traced to the base definition.
- Escalate only the labeling question, not the definition question: the CEO's concern is inconsistent external numbers, and labeled variants solve that without stripping Marketing of a fit-for-purpose measure.
Governance lesson. Adoption fails when governance is experienced as loss of autonomy. Giving the CMO a legitimate, bounded variant preserves the enterprise metric's integrity while making the CMO a participant rather than a loser. If the CMO still publishes the broad number as 'active customers,' that is a policy breach and belongs with the data governance council, not a bilateral negotiation.