Data Context Diagnostic
Find where meaning breaks.

Find where semantics, identifiers, and system boundaries are breaking your data flow.

SCOPE

1 flow, 2–4 systems

BEST FOR

Data, IT, or operations lead

What's included

Source and consumer systems for one business process, with owners and access paths.

How the same customer, product, order, or event is identified in each system.

Where units, hierarchies, names, and meanings disagree.

Integration risks, target state, and an estimated implementation backlog.

WHAT YOU RECEIVE · SEMANTIC-GAP MATRIX (EXCERPT)Sample format with synthetic values

Entity: Customer: Northwind Supply, Denver
ERP: C-100142 (sold-to account)
CRM: 0018c00002Xy (account; parent rollup differs)
Billing: "Northwind Supply Co." (free-text name)
Gap: No shared key; revenue rolls up to different parents
Recommendation: Identity map owned in the context layer; hierarchy normalized at ingest

OUTPUT

An implementation decision, with a prioritized backlog behind it.

Usual next step: Contextualization ArchitectureNext step →