Data Mesh Readiness For 50+

A 60-person scaleup asked me to design their data mesh. After the readiness check, we kept the central team.

Mesh is an org design decision more than an architecture one. Domain teams own their data as products. That only works if the domains can actually carry the ownership.

The three gates I check before any mesh talk:

1. Do domains have real engineering ownership already? If backend teams don’t own their services’ operations, they won’t own data products either. Mesh inherits your existing ownership culture, whatever it is.
2. Is the platform self-serve enough? Domain teams need to ship a pipeline without filing a ticket to the data team. No self-serve platform means mesh just distributes the ticket queue.
3. Are there people in the domains who could own definitions and quality? Federated governance is those people, or it is a slide. At 50-80 people, those people usually don’t exist yet, and hiring 4 of them costs more than the central team you’re replacing.

Fail a gate and the honest answer is a strong central team with clean domain interfaces, which is what that scaleup runs today. Contracts at the boundaries deliver most of what they wanted from mesh, at their size.

Mesh solves a scaling problem. First have the problem.

Which of the three gates would your org pass today?