Enabling Data Mesh in Large Organizations with InnerSource
summary
Kering (19.5B revenue, 48,000 employees) builds a shared self-serve data platform using InnerSource: platform code is open to brand teams, contributions follow architecture decision records (ADRs) tracked in Jira with a 10 working day objection window and a Teams channel per ADR; the central service team becomes an InnerSource advocacy team, running 15‑minute syncs and shepherding PRs. Result: faster feature delivery when a brand funds work, measurable increases in cross‑brand innovation and reuse (brands publish shared reports and data products).
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:44Why data mesh at Kering
- 4:07Core vs context in data mesh
- 7:20InnerSource adoption for platform
- 9:07InnerSource advocacy team role
- 10:10ADR contribution framework
- 14:30Benefits of InnerSource
- 15:57InnerSource beyond the platform
related talks
18mScaling Data Mesh @ Allianz Direct - Insights, achievements & learnings
15mInnerSource Contribution Insights
50mAmy Raygada | Data Track | Compass AI & Data Summit 2025
31mData Mesh In Practice – How To Set Up A Data Driven Organization
23mCan you measure InnerSource?
23mApplying Data Mesh to Your Organization
43mWhen design meets data: Using Data Mesh for a consumer and business-driven data strategy
39mData Mesh symphony: Orchestrating a synchronized data and business strategy ensemble