🇮🇩 Baca artikel ini dalam Bahasa Indonesia
TL;DR: Most organizations treat data governance as a compliance checkbox or a future-state aspiration. It is neither. A data governance foundation is the structural prerequisite for every major digital initiative — from ERP implementations to analytics programs — and skipping it is the most expensive shortcut in enterprise IT.
The Root Cause Behind Every “Data Problem”
Every few months, I get a call from a CFO or CIO who wants to discuss their “data problem.” The conversation usually starts with a specific symptom: duplicate vendor records, inconsistent financial reports across business units, an ERP migration that has gone sideways. But the root cause is almost always the same — the organization never built a proper data governance foundation. They jumped straight to technology, assuming a new platform would fix what was fundamentally a structural and organizational issue.
I have watched this pattern repeat across industries for more than two decades. And if anything, the rush to cloud platforms and remote-work infrastructure over the past eighteen months has made the problem worse, not better. Companies accelerated their digital timelines by years but did not accelerate the governance work that makes those investments pay off.
This article is about why that happens, what it costs, and how to fix it.
Why Companies Skip Data Governance
The honest answer is that data governance is not exciting. It does not produce a flashy dashboard or a press release. It is slow, cross-functional, politically messy work that requires sustained executive attention — exactly the kind of initiative that gets deprioritized when the next technology purchase comes along.
Here are the patterns I see most often:
The “new system will fix it” fallacy. An organization has data quality issues in its legacy ERP. Leadership approves a migration to SAP S/4HANA or Oracle Cloud, expecting the new platform to enforce consistency. But dirty data migrated into a new system is still dirty data — now it is just in a more expensive container.
Governance is treated as an IT project. Data governance gets assigned to the IT department, staffed with a junior analyst, and given no authority over business processes. Six months later, nothing has changed because the people who create and own the data — finance, operations, sales — were never meaningfully involved.
The urgency trap. Especially after 2020, the pressure to move fast has been enormous. When leadership is focused on keeping the business running, standing up a governance program feels like a luxury. The irony is that organizations with governance already in place before the pandemic were the ones that adapted fastest.
Nobody owns it. Data governance sits at the intersection of IT, finance, operations, and compliance. In many organizations, that intersection is a no-man’s-land. Without clear ownership and executive sponsorship, governance initiatives die from neglect.
The Cost of Skipping the Data Governance Foundation
The costs are real, measurable, and compounding. Let me describe what I have seen firsthand.
Failed or over-budget ERP implementations. Gartner has estimated that poor data quality costs organizations an average of $12.9 million per year [Source: Gartner Data Quality Research]. In ERP projects specifically, data issues are one of the top three reasons for budget overruns and timeline delays. I worked with a mid-market manufacturer last year that spent an additional $1.2 million on data cleansing during their ERP go-live — work that should have been done months earlier under a governance framework.
Inconsistent financial reporting. When the same customer or product is coded differently across systems, reconciliation becomes a manual, error-prone exercise. I have seen finance teams spend the first week of every close period just normalizing data before they can begin actual analysis. That is not a technology problem. That is a governance problem.
Security and compliance exposure. The ransomware attacks dominating headlines this year — Colonial Pipeline, JBS, Kaseya — have forced boards to pay attention to data management. But security controls are only as good as your understanding of what data you have, where it lives, and who has access. Without a governance framework that includes data classification and lineage, your security posture has blind spots you cannot see until it is too late.
Missed analytics potential. Every executive wants better analytics. Fewer want to do the work of ensuring the underlying data is accurate, consistent, and well-defined. The result: dashboards that look impressive but produce numbers no one trusts. I have sat in too many executive meetings where the first twenty minutes are spent debating whose numbers are right rather than making decisions.
Building a Data Governance Foundation That Actually Works
Notice I said “that actually works.” The industry is littered with governance programs that produced beautiful policy documents and nothing else. Here is what separates the ones that succeed from the ones that become shelfware.
Start With Business Outcomes, Not Policies
The governance programs that succeed are the ones tied to specific, measurable business problems. Do not start by writing a data governance policy. Start by asking: what decisions are we unable to make because we do not trust our data? What is the cost of that uncertainty?
For a financial services client I advised, the starting point was a simple fact: their customer data was so fragmented that they could not accurately calculate customer lifetime value. That single business problem became the anchor for their entire governance initiative — and it kept executive attention because it tied directly to revenue.
Define Ownership at the Business Level
Data stewardship must live with the business, not IT. The finance team owns financial master data. Sales owns customer data. Operations owns product and inventory data. IT provides the tools, platforms, and technical standards, but the business defines what “correct” looks like.
This is where the DAMA-DMBOK framework provides useful structure. It defines data governance as “the exercise of authority, control, and shared decision-making over the management of data assets.” The key word is “shared.” This is a cross-functional discipline that cannot be delegated entirely to any single department.
A practical governance structure looks like this:
- Executive Sponsor: A C-level executive (ideally the CFO or COO) who provides authority and removes roadblocks
- Data Governance Council: Cross-functional leadership team that sets priorities and resolves disputes
- Data Stewards: Business-side owners responsible for data quality within their domains
- Data Custodians: IT staff responsible for technical implementation of governance policies
Prioritize Ruthlessly
You cannot govern all data at once. Start with the data domains that cause the most pain or represent the highest risk. For most organizations, this means:
- Financial master data — chart of accounts, cost centers, vendor and customer records
- Customer data — especially if you are dealing with regulatory requirements like GDPR or CCPA
- Product and inventory data — critical for supply chain accuracy and financial reporting
Get one domain right. Prove the value. Then expand.
Invest in Data Quality Measurement
You cannot improve what you do not measure. Establish data quality metrics — completeness, accuracy, consistency, timeliness — and report on them with the same discipline you apply to financial metrics. This is not a one-time data cleansing exercise. It is an ongoing operational function.
Some organizations I have worked with add data quality scorecards to their monthly operational reviews. When data quality sits alongside revenue and margin numbers, it gets executive attention. That visibility alone changes behavior.
Align Governance With Your Technology Roadmap
If you are planning an ERP migration, a cloud migration, or a data warehouse modernization, governance is not a parallel workstream — it is a prerequisite. Build governance milestones into your technology project plan. Do not start data migration without agreed-upon data standards, validated business rules, and assigned data stewards.
This is where I see the most expensive failures. The technology project has a deadline. The governance work “isn’t ready.” So the project team migrates the data anyway, promising to “clean it up later.” Later never comes, and the organization inherits a new system with old problems baked into its foundation.
Data Governance as a Financial Control
Since much of my work sits at the intersection of technology and finance, I want to emphasize something specific: for financial systems, data governance is not optional. It is a control.
SOX compliance, IFRS and GAAP reporting, audit readiness — all of these depend on the integrity of your financial data. When your chart of accounts is inconsistent across subsidiaries, when intercompany transactions do not reconcile cleanly, when vendor master records are duplicated — these are not just operational inconveniences. They are control deficiencies that auditors will flag and regulators will question.
The organizations that treat data governance as part of their internal control framework, rather than a standalone IT initiative, are the ones that sustain it over time. The CFO who has to sign off on financial statements will care about this. Frame it accordingly.
What the Current Environment Demands
The events of 2021 have made this more urgent, not less. Three forces are converging:
Cloud acceleration. As organizations move financial systems, ERP platforms, and data warehouses to the cloud, they are making architectural decisions that will persist for years. Embedding governance into those decisions now is far cheaper than retrofitting it later.
Hybrid work. With teams distributed across locations, the informal hallway conversations that used to resolve data questions — “What does this account code mean?” or “Which vendor record is the correct one?” — no longer happen reliably. Formal data definitions, business glossaries, and documented ownership become essential infrastructure for distributed teams.
Cybersecurity pressure. The surge in ransomware attacks has put data management on the board’s agenda. Knowing what data you have, where it is stored, how it is classified, and who can access it — that is data governance. Security and governance are two sides of the same coin, and boards are finally starting to see that connection.
Frequently Asked Questions
How long does it take to implement a data governance program?
A realistic timeline for an initial governance framework — covering one to two priority data domains — is three to six months. Full enterprise-wide governance is a multi-year journey, not a project with a defined end date. The key is to start small, demonstrate value quickly, and expand incrementally. Organizations that try to address everything in year one typically produce documentation rather than results.
Who should own data governance — IT or the business?
The business must own data governance, with IT providing technical enablement. Data stewards within finance, operations, and sales should be accountable for the quality and definitions of data in their domains. IT manages the tools, infrastructure, and enforcement mechanisms. Executive sponsorship from a C-suite leader — often the CFO or COO — is non-negotiable. Without it, governance lacks the authority to drive change across organizational boundaries.
How does data governance relate to ERP implementation success?
Data governance is one of the strongest predictors of ERP implementation success. Poor data quality and undefined data standards are consistently cited among the top causes of ERP project delays and cost overruns. Organizations that establish governance before migration — defining master data standards, cleansing existing records, and assigning data ownership — experience smoother deployments and faster time-to-value. Treating governance as a phase within the ERP project, rather than a separate initiative, is the most effective approach I have seen.
Is data governance only relevant for large enterprises?
No. The complexity may differ, but the principles apply at any scale. A 200-person company with a single ERP instance still needs consistent data definitions, clear ownership, and quality standards. In fact, smaller organizations often benefit faster because they have fewer stakeholders, shorter decision cycles, and less legacy baggage. The governance framework should be proportional to the organization’s size and complexity — but it should exist.
The Foundation Comes First
Every technology investment your organization makes — every ERP migration, analytics platform, cloud initiative, and security program — depends on the quality, consistency, and trustworthiness of your data. A data governance foundation is not a nice-to-have initiative for when things settle down. It is the structural prerequisite that determines whether those investments deliver value or become expensive disappointments.
The organizations I see thriving right now are not the ones with the most advanced technology stacks. They are the ones that did the unglamorous work of getting their data house in order. They defined who owns what. They established standards and measured compliance. They treated data as a business asset, not an IT afterthought.
If your organization has not started this work, the best time was five years ago. The second-best time is now — before your next major technology decision locks in data problems for another decade.
