Every data governance initiative starts with good intentions. A steering committee is formed. A framework is selected — usually DAMA-DMBOK or a derivative. Policies are written. A data catalogue is procured. And then, 18 months later, the steering committee has stopped meeting, the catalogue has 40% coverage and is already out of date, and the policies exist only as PDF documents on a SharePoint site that nobody visits.
Why Governance Programmes Fail
The failure mode is almost always the same: governance is treated as a project with a defined end state, rather than as an ongoing operational practice. Projects have budgets, timelines, and completion criteria. Governance has none of these — it is a continuous discipline that requires sustained organisational commitment, embedded accountability, and regular reinforcement.
- Governance ownership sits in IT, not in the business units that own the data
- Data stewards are appointed without time allocation or performance incentives
- Policies are written for compliance, not for practical use
- Tooling is procured before processes are defined
- Executive sponsorship evaporates after the launch event
The DAMA Framework: What It Gets Right
DAMA-DMBOK provides a comprehensive knowledge body that covers eleven data management knowledge areas, from data architecture to data quality to metadata management. Its value is not as a prescriptive implementation guide — it is too comprehensive for that — but as a vocabulary and a completeness check. Organisations that use DAMA well treat it as a reference architecture, not a project plan.
Key Principle
Start with two or three DAMA knowledge areas that address your most acute pain points. Achieve demonstrable results in those areas before expanding scope. Governance credibility is built through visible wins, not comprehensive frameworks.
What Sustainable Governance Looks Like
In our public-sector engagements, the governance programmes that have survived beyond two years share a common set of characteristics. They have named data owners at the executive level who are accountable for data quality in their domains. They have embedded data stewards in business units — not in IT — who spend at least 20% of their time on governance activities. And they have a small, empowered central governance team that sets standards, resolves disputes, and reports progress to the executive.
“The best data governance framework is the one your organisation will actually follow. A simple, enforced standard beats a comprehensive, ignored one every time.”
Metrics That Matter
Governance programmes need to demonstrate value in business terms, not technical ones. The metrics that resonate with executives are: reduction in time spent reconciling conflicting reports, reduction in audit findings related to data quality, and improvement in regulatory reporting accuracy. These are measurable, attributable to governance activities, and meaningful to the people who fund the programme.