Activities 2.12–2.17 — Implement & Embed
2.12 Implement Data Governance
Execute the roadmap incrementally, fitted to maturity, engagement, funding and business priorities.
Foundational implementation often includes procedures, governed terminology/Business Glossary, architecture coordination and data valuation. Implementation is not “install a governance tool.”
2.13 Sponsor Data Standards and Procedures
Create authoritative measurable standards and repeatable procedures; communicate, monitor, audit/review, update and enforce them.
Governance sponsors/approves the enterprise requirements. Knowledge Area experts often draft detailed technical/functional standards.
2.14 Develop a Business Glossary
Establish rigorous shared business terminology, including synonyms/variants, exceptions, approval/stewardship and related Metadata. Reduce ambiguity across business and technology.
2.15 Coordinate with Architecture Groups
Data Stewards and Data Architects jointly maintain enterprise data structures/meaning alignment. The DGC may review, approve and formally adopt key architecture artifacts.
Governance does not replace Architecture; it supplies decision rights and enterprise authorization/coordination.
2.16 Define Data Asset Valuation Method
Organize a consistent organizational method for valuing information/data. Use replacement, market, opportunity, sale/packaging and risk-related perspectives as appropriate.
Do not invent a universal DAMA formula.
2.17 Embed Data Governance
Make Governance an ongoing funded, monitored, measured and accepted operating function rather than a finite project.
Evidence of embedding includes: - recurring operating routines/bodies; - active stewardship and ownership; - enforceable policies/standards; - issue resolution; - metrics/scorecards; - stable funding; - continued monitoring; - change reinforcement and accepted behavior.
Community of Interest
A Data Management Community of Interest can help early maturity by building awareness, relationships, common vocabulary and evidence of recurring problems.
It is not automatically a formal DGO or governance authority. Formal authority requires sponsorship, explicit decision rights, accountabilities, operating framework and issue/policy paths.
Implementation vs embedding
- Implementation: initial/staged rollout of governance capabilities.
- Embedding: governance continues to perform and adapt as normal operations.
A website, council launch or completed first roadmap proves launch, not sustainability.
Chapter-wide implementation story
Business problem / drivers
→ readiness + discovery / alignment
→ strategy + operating framework
→ change management + issue/compliance mechanisms
→ standards / glossary / architecture / valuation implementation
→ embed / monitor / measure / fund / improve
↺ iterate and tailor
This is a Mastery Lab learning synthesis of the chapter's activity logic, not a new rigid DAMA waterfall.
Source anchors: Chapter 3 pp. 90–96.