A working MDM team structure needs four distinct roles — an executive sponsor, a data governance council, data stewards embedded in the business, and a technical MDM architect/administrator — because master data management fails most often not from bad technology but from nobody actually being accountable for the data itself.

Why the org chart matters as much as the platform

Enterprises routinely buy an MDM platform, load it with customer or product data, and then watch match rates and data quality stagnate — not because the tool is wrong, but because nobody owns the decisions the tool surfaces. Survivorship conflicts, duplicate merges, and hierarchy changes all need a human to decide, and if that person doesn’t exist in the org structure, decisions default to whoever shouts loudest or, more often, don’t get made at all.

The core roles

Executive sponsor

Someone senior enough to resolve cross-functional disputes — typically a CDO, CFO, or COO depending on which domain (customer, product, supplier) the programme centres on. Without this, MDM becomes an IT project that business units can quietly ignore.

Data governance council

A standing body, usually meeting monthly, with representation from each business unit that creates or consumes the master data domain. This is where policy decisions — match thresholds, survivorship rules, data ownership disputes — actually get resolved.

Data stewards

Embedded in the business, not IT. A data steward for customer master data typically sits in sales operations or customer service; a product data steward usually sits in merchandising or product management. They’re the people who know what “correct” looks like for their domain and who triage data quality exceptions day to day.

MDM architect and administrator

The technical role: configuring match-and-merge rules, managing data model changes, maintaining integrations with source and consuming systems. This role executes governance council decisions — it shouldn’t be the one making them.

Sizing it realistically

A mid-sized enterprise running a single-domain MDM programme (customer data only, say) can often operate with one or two part-time stewards and a governance council that meets monthly, rather than a large dedicated team. Multi-domain MDM — customer, product, and supplier together — generally needs dedicated stewardship per domain, because the business rules and the people who understand them rarely overlap.

How Agilus approaches this

We build the governance structure alongside the technical MDM implementation, not after it — defining steward roles, escalation paths, and council cadence before go-live so the organisation is ready to actually run the programme once the platform is live, rather than scrambling to assign ownership after the first survivorship conflict lands.

FAQ

Does a data steward need to be technical?
No. Data stewards need deep business knowledge of the domain they own — what a “correct” customer or product record looks like — not technical database skills. Technical execution sits with the MDM architect/administrator role.

How often should the data governance council meet?
Monthly is typical for an established programme; weekly or biweekly often makes sense in the first few months after go-live while survivorship rules and data quality issues are still being worked out.

Leave a Reply

1