The 17 Activities — Recognition Map
Do not memorize numbering as a rigid workflow. Be able to recognize what each activity is trying to accomplish.
| # | Activity | Decisive cue |
|---|---|---|
| 2.1 | Define DG for the organization | Clarify what/who is governed, who governs and scope. |
| 2.2 | Perform readiness assessment | Maturity, capacity to change, collaboration, business alignment. |
| 2.3 | Discovery and business alignment | Existing practices/issues/risks/benefits → governance requirements/business case. |
| 2.4 | Develop organizational touchpoints | Procurement, funding, compliance, SDLC, DQ/architecture integration. |
| 2.5 | Develop DG strategy | Charter, framework/accountabilities, roadmap, operational-success plan. |
| 2.6 | Define operating framework | Fit structure/roles/issue paths to data value, business model, culture, regulation. |
| 2.7 | Develop goals, principles, policies | Establish/adopt guidance; communicate/monitor/enforce/re-evaluate. |
| 2.8 | Underwrite DM projects | Sponsor/business-case/coordinate significant data improvements with PMO/projects. |
| 2.9 | Engage change management | Sponsorship, training, feedback, incentives, SDLC/policy integration, reinforcement. |
| 2.10 | Engage in issue management | Log, prioritize, resolve, track, communicate, facilitate, escalate. |
| 2.11 | Assess regulatory compliance | Applicability, controls/policies, evidence, monitoring, penalties, remediation. |
| 2.12 | Implement DG | Execute roadmap incrementally; establish foundational capabilities. |
| 2.13 | Sponsor standards/procedures | Mandatory measurable standards + documented repeatable methods; monitor/enforce. |
| 2.14 | Develop Business Glossary | Shared governed definitions plus associated Metadata/context. |
| 2.15 | Coordinate with Architecture groups | Stewards + architects align enterprise structures; DGC may adopt key artifacts. |
| 2.16 | Define data-asset valuation method | Consistent organizational value method; no universal formula. |
| 2.17 | Embed DG | Fund, operate, monitor, measure and normalize Governance as sustainable operations. |
Four-movement study synthesis
This grouping is a Mastery Lab memory aid, not a DAMA taxonomy:
- Define/assess/align/strategize: 2.1–2.5.
- Design/change/control: 2.6–2.11.
- Implement foundations: 2.12–2.16.
- Embed: 2.17.
Key sequence distinctions
- Readiness before broad rollout does not mean every issue must be perfect first.
- Governance requirements should enter projects early, not at testing.
- Implementation is usually incremental and tailored.
- Embedding continues after initial roadmap delivery.