When Every Team Holds a Different Version of the Customer

← Playbooks

Playbook · Recurring coordination problem · Organisations × Technology

Fragmented customer understanding rarely appears as one failure. It appears as constant small contradiction. This is a way to examine whether consolidation is the right response.

This is reusable guidance, not a record of what happened and not a procedure. It is a starting point for a situation that recurs in different forms — useful while its conditions hold, and worth abandoning where they do not.

The situation

Marketing, product, support and analytics each hold a partial customer. Each version is defensible in its own context. Decisions get taken about whichever version is closest to the room, and the experience contradicts itself in ways nobody chose.

The question

Does this organisation need one shared model of the customer, or better-connected partial ones?

Conditions

What needs to be true, or examined, before this approach applies.

• The same customer is genuinely being served by several teams, not different customer types.
• Contradictions are traceable to differing definitions rather than differing timing.
• Someone can own definitions across team boundaries.
• The cost of current fragmentation can be described concretely, not just felt.

Signals

What is worth paying attention to.

• Whether teams reporting the same metric produce the same number, and whether they know why not.
• Where identity resolution actually happens, and how often it is wrong.
• Which team's definition wins in practice, and whether that was decided.
• What customers experience when two teams act on different versions of them.

Decisions

What may need to be decided, and by whom.

• Which parts of the customer model must be shared, and which can legitimately differ by team.
• Who owns each shared definition.
• Whether the shared model is read-only or written to, and by whom.
• What happens to existing definitions that will not be consolidated.

A first useful move

Take one decision that recently went wrong and trace which version of the customer each team was using. That single trace usually reveals whether the problem is definition, timing or ownership — three problems with different fixes.

Not yet

Do not start a platform consolidation, and do not select a customer data tool. Both encode definitions before the definitional disagreement has been resolved, which makes the disagreement permanent and expensive.

The trade-off

A shared model makes decisions coherent across teams and removes the local nuance some teams were relying on. Coherence is bought partly with expressiveness, and the teams that lose most nuance are often the ones closest to the customer.

Assumptions

What this rests on, and what would change it.

What informed this

Observation in consumer-facing environments where fragmentation was visible, plus reasoning about coordination cost. Qualitative; the cost of fragmentation was described by the organisations involved rather than measured independently.

What would change this approach

This changes where teams genuinely serve different customers, where regulation requires separation, or where fragmentation is a symptom of unresolved organisational ownership. In the last case, consolidating data will not settle a question about authority.

Where this stops being useful

It stops being useful where the difficulty is technical identity resolution at scale, which is a distinct problem, and it does not address customer understanding that is shared but wrong.

Related

Related reading

Industry

• Retail
• D2C
• Consumer Brands
• BFSI
• Telecom

Knowledge · Architecture

• Connecting customer identity across commerce and service systems
• Keeping commerce truth outside the channel that reads it

Evidence · Observed Situation

• When growth outpaced the organisation's ability to read itself
• When every team had a dashboard and no team had a decision

The situations linked above informed this guidance. They do not establish that it transfers to another environment — that remains a question about the specific organisation.

Knowledge →Work with Cralgo →