Why Enterprise MDM Governance Fails After Go-Live — and How to Make Ownership Real
In Brief
Enterprise MDM governance often looks strongest before go-live. Data Owners have been nominated, Data Stewards appear in the operating model, governance councils have charters and workflows contain approval roles. The real test begins later—when two business units disagree, an exception affects several domains or a recurring data problem requires one function to change the process that creates it.
Governance fails when ownership is defined as a role but not as decision authority. A Data Owner who cannot approve a standard, a Steward who can identify an error but cannot trigger corrective action and a council that receives reports but cannot resolve cross-domain conflicts are governance structures in name only.
Sustainable MDM governance therefore needs explicit decision classes, delegated authority, evidence, escalation paths and durable decision records. The question is not simply “Who owns the data?” It is “Who can decide what, using which evidence, within which authority boundary—and what happens when the decision is contested?”
Enterprise MDM governance often looks strongest on the day it is designed.
The governance council has been named. Data Owners and Data Stewards appear in the organization chart. RACI matrices have been approved. Workflow roles exist in the MDM platform.
Then the system goes live.
A country organization requests an exception to a global customer standard. Two business units disagree about whether supplier records represent the same legal entity. A product attribute fails repeatedly, but nobody wants to change the upstream process that creates the error.
A Data Steward can identify the problem but cannot compel the responsible business function to resolve it.
At this point, the real governance model becomes visible.
MDM governance is not proven by the existence of governance roles. It is proven by what happens when people disagree about data.
Ownership is not a name in a RACI matrix
RACI matrices are useful for describing participation.
They are less useful when the real issue is authority.
Suppose a Data Owner is marked Accountable for supplier master data.
Can that person approve an enterprise supplier definition? Can the owner reject a regional exception? Can the owner require an upstream process to change? Can the owner accept a known data risk temporarily? Can the owner override another business function?
If the answer is unclear, ownership remains descriptive rather than operational.
Accountability without decision authority is responsibility without control.
Start with decisions, not roles
Instead of beginning with an organization chart, I would begin with the decisions the enterprise repeatedly needs to make.
Seven decision classes cover much of the practical governance work in enterprise MDM.
| Decision class | Typical question |
|---|---|
| Identity | Do these records represent the same real-world customer, supplier, product or organization? Should an existing identity be merged, split or preserved separately? |
| Definition | What does a critical attribute, classification or business term mean across the enterprise? |
| Authority | Which source or process is authoritative for a particular attribute, and what happens when authoritative sources disagree? |
| Hierarchy & Relationship | Which parent-child, ownership, product, organizational or other relationship should become governed enterprise context? |
| Exception | When may a business unit operate outside the enterprise standard, for what reason and for how long? |
| Policy Change | When recurring exceptions indicate that the enterprise rule itself should change, who may change it? |
| Risk Acceptance | Who may knowingly accept an unresolved data risk when immediate correction is impractical or disproportionately costly? |
Define the decisions first. Then assign the role with the authority to make each decision.
A workflow approval is not the same as enterprise decision authority
MDM platforms can enforce workflow.
SAP Master Data Governance, for example, supports change-request processes in which predefined processor groups perform specific actions at particular workflow steps. Current SAP documentation also defines specialist roles with authorization to process and approve master-data change requests.
This provides an important technical control.
But the organization must still decide what that approval actually means.
Approving a supplier-address change and deciding whether two legal suppliers should become one enterprise identity are not necessarily equivalent decisions.
Workflow determines how a decision moves. Governance determines who has the authority to make the decision and under which conditions.
Separate Data Owner and Data Steward authority
One of the most common governance ambiguities is the relationship between the Data Owner and the Data Steward.
If both roles are simply described as “responsible for data quality,” neither role has a useful operating boundary.
| Role | Primary governance responsibility |
|---|---|
| Data Owner | Accountable business authority for domain policy, important definitions, decision-right delegation, material exceptions and accepted business risk. |
| Data Steward | Operates governance within delegated authority: reviews evidence, resolves defined operational issues, monitors quality, executes approved policy and escalates cases outside the delegated boundary. |
| Governance Council | Resolves cross-domain or cross-business conflicts, approves enterprise-wide policy where required and handles decisions that exceed one domain owner's authority. |
| Platform / Custodian | Implements workflow, access, integration, monitoring and technical controls. It should not become the default owner of business policy simply because it operates the platform. |
IBM similarly distinguishes multiple Steward roles and a Master Data Governance Council, with Advanced Stewards handling areas such as identity resolution, hierarchies and business rules while the council steers governance at program level.
Stewardship should have delegated authority
A Steward should not need a committee meeting for every operational decision.
Nor should a Steward be expected to make policy decisions that belong to accountable business leadership.
The practical answer is delegated authority.
A Steward may be authorized to resolve potential matches under defined evidence criteria, correct selected quality defects or approve ordinary changes within established policy.
A legal-entity merge, enterprise-definition change or high-impact exception may require Data Owner approval.
Effective stewardship is not unlimited authority. It is sufficient delegated authority to resolve normal work without escalating every case.
The escalation path should follow decision consequence
Escalation is often designed according to organizational hierarchy.
A more useful design is based on decision consequence.
| Level | Typical treatment |
|---|---|
| Steward | Resolves routine cases where evidence and approved policy are sufficiently clear. |
| Data Owner | Resolves material domain exceptions, conflicting interpretations or decisions outside Steward authority. |
| Governance Council | Resolves conflicts spanning several domains, functions or enterprise policies. |
| Executive / Risk Authority | Handles exceptional cases where unresolved master-data risk becomes a material business, regulatory or financial decision beyond the normal governance boundary. |
Escalation should move a decision to the lowest level that actually has authority to resolve its consequence.
Use a Decision Authority Record
Instead of describing governance only through roles, important recurring decisions can be documented through a simple decision record.
Decision → Decision Owner → Evidence → Authority Boundary → Escalation → Record
| Element | Question |
|---|---|
| Decision | What specific issue must be decided? |
| Decision Owner | Which role has authority to make this decision? |
| Evidence | Which data, policy, business context and impact information must support the decision? |
| Authority Boundary | Under which conditions may this role decide without further approval? |
| Escalation | Where does the case go when evidence, impact or authority exceeds that boundary? |
| Record | What decision, rationale, exception period and evidence should be preserved? |
Governance becomes operational when authority can be expressed as a repeatable decision pattern.
The Governance Council should decide, not receive status reports
A common governance failure is the transformation of the council into a reporting forum.
Quality metrics are presented. Open issues are reviewed. Project updates are shared.
But difficult cross-business decisions continue to happen elsewhere through informal negotiation.
Reporting has value, but it is not the primary reason to create a governance council.
If a governance council never resolves a contested decision, it may be a reporting committee rather than a governance body.
Keep operational decisions out of the council
The opposite failure also occurs.
A governance council becomes overloaded with individual quality issues, routine approval cases and operational exceptions that Stewards or Data Owners should be able to resolve.
This makes governance slow and encourages teams to bypass it.
Governance should escalate ambiguity and consequence—not every record.
Recurring exceptions belong to the owner of the cause
A Steward may correct a data-quality issue today.
If the same issue returns tomorrow because an upstream business process continues producing it, the governance problem has moved beyond stewardship.
The owner of the source process should become part of the corrective action.
Otherwise, Steward capacity becomes a permanent repair service for another function's process defect.
The person who fixes the record is not necessarily the person who owns the reason the record keeps becoming wrong.
Exception governance needs an expiry mechanism
Enterprise standards will always require legitimate exceptions.
A market may have regulatory requirements. A local business process may genuinely need another attribute. A migration period may require temporary coexistence.
The danger is allowing an approved exception to become a permanent alternative standard simply because nobody reviews it again.
Material exceptions should therefore carry context such as reason, owner, affected scope, effective date and review or expiry condition.
An exception without a review condition is often a second standard being created quietly.
Risk acceptance is also a governance decision
Not every known master-data defect can or should be fixed immediately.
Some issues may be expensive to correct. Others may disappear when a legacy system is retired. A temporary inconsistency may be manageable through an explicit control.
The mistake is allowing such conditions to remain unresolved simply because nobody wants to make the tradeoff visible.
Choosing not to fix a known master-data problem is still a decision. Governance should make clear who is authorized to accept that risk.
Data quality metrics need an accountable response
A dashboard can show that completeness is declining.
It cannot make a business function change its process.
Metrics become governance only when a threshold or pattern triggers a defined response by someone with authority.
Signal → Accountable Owner → Decision → Corrective Action → Verification
Measurement without an accountable response creates visibility, not governance.
Authority should survive organizational change
Governance structures are often designed around named individuals.
Then the organization changes.
A Data Owner moves to another role. Business units merge. A Steward team is reorganized. A council sponsor changes.
If governance knowledge exists only in people's memory, ownership weakens each time the organization changes.
Governance should therefore attach decision authority to enduring roles and preserve the history of important decisions, exceptions and unresolved issues through role transitions.
People change. The enterprise should not have to rediscover its master-data decisions every time the organization chart changes.
Governance and platform permissions must align
A governance design can grant one role decision authority while the technology allows another role to perform the actual action.
That gap should be made explicit.
IBM MDM, for example, distinguishes Data Steward and manager-level permissions, supports workflow authorization for remediation tasks and applies governance controls to protected master data.
SAP MDG similarly uses workflow steps, processor groups, approval roles and authorizations to control which actions particular users may perform.
Governance defines legitimate authority. Platform authorization should enforce that authority wherever practical.
Technical administrators should not become accidental Data Owners
Platform administrators and MDM technical teams often have powerful permissions.
This is operationally necessary.
It does not mean they should define enterprise identity, approve business exceptions or decide which business definition is correct.
Where technical staff must execute an emergency change, the business decision and technical execution should remain distinguishable in the audit trail.
Ability to change the data is not the same as authority to decide what the data should mean.
AI does not remove the ownership problem
AI can make governance more efficient.
Agents can gather evidence, detect anomalies, propose corrections and route exceptions.
But an AI recommendation does not answer who is accountable for the enterprise policy behind the decision.
If an agent repeatedly proposes a different supplier-classification rule, somebody still has to decide whether the enterprise standard should change.
AI can automate governance work. It does not eliminate governance authority.
The governance loop should close
Governance is often treated as a sequence ending with approval.
Sustainable governance needs a feedback loop.
Decide → Execute → Escalate → Learn
Decide: apply policy and evidence to the issue.
Execute: implement the decision through the appropriate workflow or source process.
Escalate: move cases beyond existing authority to the right decision level.
Learn: use recurring issues, overrides and exceptions to improve standards, workflow and upstream processes.
Governance matures when repeated decisions improve the system that produces future decisions.
Measure decision performance, not committee activity
Number of council meetings, number of Data Owners appointed and number of stewardship tasks closed are operational statistics.
They do not show whether governance is effective.
More useful measures examine the decision system itself.
| Measure | What it reveals |
|---|---|
| Decision lead time | Whether governance can make required decisions at business speed. |
| Aging decisions | Whether important issues remain unresolved because authority or evidence is unclear. |
| Exception recurrence | Whether governance is removing root causes or repeatedly approving the same problem. |
| Escalation pattern | Whether too many normal decisions require senior intervention or important cases remain below the appropriate authority. |
| Policy change from evidence | Whether recurring operating evidence actually improves governance rules. |
| Consumer bypass | Whether business teams trust governed master state or continue maintaining parallel versions. |
Governance performance should be measured by the quality and speed of decisions—not by the volume of governance activity.
Different decisions need different service expectations
Governance is sometimes accused of being slow because every issue is expected to pass through the same path.
That is a design problem.
A routine reference-data correction does not require the same treatment as a legal-entity merge. A standard approval does not require the same deliberation as a cross-region policy exception.
Service expectations should therefore be designed according to decision class, consequence and evidence complexity rather than one universal governance SLA.
Fast governance is not governance with fewer controls. It is governance that sends each decision to the right authority without unnecessary escalation.
Governance must be funded as an operating capability
One reason governance weakens after go-live is that implementation funding ends.
During the project, architects, consultants, business SMEs and project managers provide extraordinary capacity.
After go-live, governance is expected to operate with part-time Stewards and periodic councils while transaction volumes, business change and exceptions continue.
Sustainable governance requires capacity for stewardship, policy maintenance, issue analysis, ownership transition, measurement and root-cause improvement.
Governance that depends on project capacity will weaken when the project capacity disappears.
Project exit should have a governance readiness gate
Technical go-live does not prove that the operating model is ready.
Before the project organization withdraws, I would verify at least five conditions.
Named roles have explicit decision authority rather than generic responsibility.
Normal operational cases can be resolved without project-team intervention.
Cross-domain conflicts have a functioning escalation path.
Recurring exceptions have owners and root-cause mechanisms.
Governance performance can be measured after the implementation team leaves.
The project is not finished when MDM is technically live. It is finished when ordinary governance no longer depends on the project.
Seven questions for a post-go-live governance review
1. Which recurring master-data decisions does the organization actually make, and who has authority for each one?
2. Which decisions can Stewards make independently, and which must be escalated to a Data Owner?
3. What does the Governance Council decide that individual domain owners cannot?
4. Which recurring quality issues originate in upstream business processes, and who owns removing those causes?
5. Do approved exceptions have owners, rationale and review conditions?
6. Can the enterprise reconstruct why an important master-data decision was made and under whose authority?
7. Could the operating organization continue making these decisions if the original implementation team disappeared tomorrow?
If several answers are unclear, the organization has governance roles but not yet a complete governance operating model.
Governance becomes real when decisions survive disagreement
MDM governance is easy when everybody agrees.
The real test occurs when global and local requirements conflict, when two authoritative sources disagree, when a Steward challenges an established process or when correcting master data requires another business function to change the way it works.
Organization charts cannot resolve those situations.
Decision rights can.
That is why mature MDM governance should be designed as an operating decision system rather than a collection of committees and role descriptions.
Ownership becomes real when the enterprise knows who can decide, what evidence is required, where authority ends and how a contested decision is resolved.
Sources & Further Reading
SAP Help Portal — Concept of Change Requests
Current SAP MDG documentation describing change requests as governed processes in which predefined processor groups are authorized to perform specific activities at each workflow step, including processing, checking and approval.
SAP Help Portal
SAP Help Portal — Master Data Governance for Customer: Specialist
SAP S/4HANA 2025 FPS02 documentation defining a specialist role with authorization to process and approve customer master-data change requests.
SAP Help Portal
SAP Help Portal — Change Request Processing
Current SAP MDG documentation illustrating requester, reviewer and approval responsibilities and how approved master-data changes move from the staging area into active master data.
SAP Help Portal
IBM — User Roles for Master Data Management
Current IBM documentation distinguishing Data Steward, Advanced Data Steward, Data Steward Manager, Master Data Governance Council and other MDM roles, including responsibilities for identity resolution, hierarchy maintenance, business rules and governance oversight.
IBM Documentation
IBM — Governing and Maintaining Master Data
IBM documentation describing data governance as a combination of governance councils, data policies and Steward tools for reviewing and improving master-data quality.
IBM Documentation
IBM — Completing Data Stewardship Tasks
Current IBM documentation describing governed remediation of potential matches and potential overlays, task ownership and authorization requirements for Data Stewards.
IBM Documentation
IBM — Configuring Master Data Workflows
Current IBM documentation describing task workflows for Steward review and remediation, including potential-match decisions and quarantine of potential identity-breaking updates.
IBM Documentation
Informatica — Master Data Governance: Framework & Implementation Guide
Current Informatica guidance describing accountability through domain ownership, assigned Stewards, visible approval processes and explicit decision rights rather than informal governance.
Informatica
Method Note
This article treats MDM governance primarily as a decision operating system rather than as an organization-chart or committee-design exercise. It does not imply that all enterprises should use the same organizational model or governance hierarchy.
The seven decision classes Identity / Definition / Authority / Hierarchy & Relationship / Exception / Policy Change / Risk Acceptance are practitioner categories developed for this article. Individual organizations may combine, subdivide or rename these classes according to business model, domain and regulatory requirements.
The framework Decision → Decision Owner → Evidence → Authority Boundary → Escalation → Record, the governance loop Decide → Execute → Escalate → Learn and the escalation levels described in this article are practitioner operating models rather than SAP, IBM or Informatica reference architectures.
The roles Data Owner / Data Steward / Governance Council / Platform or Custodian are used to illustrate authority separation. Actual role names, organizational placement and legal accountability vary across enterprises.
No universal decision SLA, Steward-to-record ratio, council frequency, escalation threshold or governance maturity score is assumed. Appropriate governance intensity should reflect decision consequence, ambiguity, regulatory exposure, business speed and organizational structure.
Vendor documentation in the Sources section is used to demonstrate that modern MDM products support differentiated roles, workflow, authorization, stewardship and governance controls. The practitioner framework in this article should not be interpreted as a description of one vendor's complete governance model.
Reviewed: October 2026
Previous: MDM #8. When Enterprise MDM Goes Off Track — Five Early Warning Signs
Next: MDM #10. Why Master Data Derails SAP S/4HANA Migration — and What to Fix Before Cutover
This article is part of the Enterprise MDM Series exploring how master data is evolving for AI-ready and agentic enterprises.
Comments
Post a Comment