The Mesh MandatePipeline · medium · ~12 minYour VP returns from a conference with a mandate: "We're doing data mesh. Plan by end of quarter."The company: 220 people. Eight product teams (4–9 engineers each). One central data team — five people — that owns ingestion, the warehouse, dbt, and every dashboard. The central team is genuinely drowning: a 6-week request backlog, and two product teams have started building shadow pipelines out of frustration.The diagnosis (central bottleneck) is correct. You've been asked to write the plan — and you know from the production literature that the same diagnosis has produced both restored trust and expensive relabeled silos, depending on preconditions the mandate never mentions.Evidence

Org snapshot

Precondition audit notes

The mandate's assumptions

Checkpoints

Against the published readiness preconditions, what is this org's standing?

The literature's scale guidance: ~100-person orgs with 2–3 data FTEs are below the mesh threshold. This org is 220 people with 5 data FTEs and 8 domains, 6 of which have zero data skills. If ownership transferred today, roughly how many of the 8 domains could actually operate their pipelines?

Which plan honors the correct diagnosis without failing the preconditions?

Write the plan's first page for the VP: how you honor the diagnosis, the sequenced phases with their gates, what happens to the shadow pipelines, and the metric that tells you when a domain is ready for real ownership.