Tom De Wolf joins expert panel on Data Mesh Operating Models

On May 2nd, 2024, Tom De Wolf, expert in Data Mesh Operating Models, participated in an online roundtable hosted by the International Data Mesh Learning Community. He joined industry leaders Eric Broda, Data Strategy Specialist, and Jean-Georges Perrin, renowned author and Data Mesh advocate, to discuss next-generation operating models for data mesh journeys.

Data Mesh, known for its decentralized and federated approach, presents unique challenges, especially for enterprises used to centralized data management. The roundtable focused on defining an effective data mesh operating model, addressing structuring incentives, team dynamics, and governance to ensure successful data mesh implementation.

Key Discussion Points

Team Structures and Interaction Modes:

The need for multiple teams and their interaction modes is crucial for effective Data Mesh implementation. In line with Team Topologies terminology, data products are managed by Stream-aligned (domain) teams, while a Platform team manages the self-service platform. Initially, intense collaboration is needed to bootstrap the first version of the platform and data products. As the platform stabilizes, the interaction mode shifts to 'platform as a service,' allowing domain teams to use the self-service tools autonomously.

Enabling Teams:

Enabling teams plays a critical role in supporting other teams with expertise, guidance, and best practices. These include federated governance teams that promote collaboration and ensure interoperability, enterprise architect teams that guide architectural best practices, and teams dedicated to onboarding domain teams into the Data Mesh journey.

Federated Governance:

Federated governance is essential to stimulate collaboration and ensure smooth interoperability between various teams. This governance model helps maintain the balance between decentralized ownership of data products and centralized control of the self-service platform.

Fit-for-Purpose Team Topologies:

The design of team topologies must be tailored to fit the specific context and culture of an organization. For instance, in sectors with many smaller organizations, intermediary organizations might assume ownership on behalf of a group of smaller entities. Another example, larger organizations a single platform team might not be enough, there can be a need for a core platform team that collaborates with an ecosystem of technology platform teams.

📺 Rewatch the recording of the live event on YouTube.

💻 Join the ongoing conversation in the Data Mesh Learning Community Slack channel. Don't miss out on the opportunity to connect with peers by joining the Data Mesh Belgium Meetup group!