This company piloted Data Mesh with 2 domains in 6 months. Here's what worked (a

This company piloted Data Mesh with 2 domains in 6 months. Here’s what worked (and what didn’t).

200-person company. Centralized data team bottleneck. Request queue was 6 weeks long.

They didn’t rip-and-replace to full Data Mesh. They piloted: 2 domains, 6-month timeline.

Month 1-2: Define operating model. Who owns what? What’s the central platform responsible for? What’s domain responsibility? Governance structure. Platform services. Decision-making authority.

Month 3-4: Assign ownership. First two data products built by domain teams (not central). Platform provides tools, standards, security enforcement. Central team starts unlocking.

Month 5-6: Cross-domain data products. Interoperability. Contracts between domains. Now domains can consume each other’s data without central team as intermediary.

Result: Two domains self-sufficient. Central team actually had time for strategic work. Request queue collapsed to 2 weeks. They’re now expanding to 4 more domains using the same model.

Key lesson: Start small. Prove the model works. Then expand. Most organizations fail because they go all-in immediately.

If you piloted Data Mesh with one domain, what would you learn in 3 months that would inform expansion?