Data as a product, organised by domain. Why this is more of an org question than a tech one.
Category · Data & Analytics
Data as a product, by domain.
Data Mesh inverts the central data team: instead of one place that manages all the data of all departments, each business domain owns its own data and makes it available as a product — documented, versioned, with quality commitments.
Sales owns the sales data, marketing owns its own. A central platform provides only the shared infrastructure, not the content.
When the approach earns its keep.
Data Mesh solves an organisational problem, not a technical one: when the central data team becomes the bottleneck because it can never know the domain expertise of twelve departments deeply enough. Then it helps to put responsibility where the domain knowledge sits.
The honest constraint.
Mesh assumes that every domain is both able and willing to maintain data as a product — with its own people and its own standards. Sell that to a mid-sized firm with three data people and you build bureaucracy instead of acceleration. At that size, a good central warehouse beats any mesh.
