Integrated Capstone — “Install Governance Software”
A global company has inconsistent Customer definitions across regions, repeated regulatory findings, no clear Data Owners, duplicate cloud contracts and a culture that resists enterprise standards. A new CDO is told to “install governance software.”
1. What should the CDO do first?
Best response: define Governance around the business drivers/scope, then perform readiness and discovery/business alignment before selecting an operating model or tool.
Why
The source puts business need, culture/change capacity, decision rights and operating design ahead of tooling. The CDO should identify: - concrete risks/benefits; - current practices/issues; - maturity/change/collaboration readiness; - organizational touchpoints; - accountabilities/roles; - issue paths; - governance requirements.
Weaker: buy the platform first and let product features define the operating model.
Source: pp. 72–85, 94–95.
2. Which operating model is automatically correct?
Answer: None.
A global/distributed company may make Federated governance plausible, but Chapter 3 says the model must fit business strategy, organizational/cultural context, regulation, data value and authority pattern. “Global” alone is not a sufficient clue.
Source: pp. 75–78.
3. What would prove Governance is becoming sustainable?
Look for evidence such as: - embedded processes; - active stewardship/ownership; - enforceable policies/standards; - issues resolved through defined pathways; - meaningful metrics/scorecards; - continued funding; - accepted cross-functional behavior; - ongoing monitoring/change reinforcement; - business/risk outcomes improving.
Committees or tool deployment alone are launch evidence, not sustainability evidence.
Seven-part capstone answer
- Primary problem: governance is being reduced to software despite unresolved authority, compliance, semantic, procurement and change issues.
- Leading KA: Data Governance.
- Supporting KAs: Metadata, DQ, Architecture, Security/Compliance-related Data Management, Reference/Master Data as relevant.
- Roles: CDO/sponsor, Steering/DGC/DGO as designed, Data Owners, Business/Technical Stewards, Legal/Compliance, Procurement/PMO/Architecture.
- Best action: business-driver definition → readiness/discovery → strategy/framework → change/issue/compliance → incremental implementation → embedding/metrics.
- Weaker: tool-first implementation.
- Changed fact: if all governance authority/roles/processes/requirements are mature and only manual workflow causes inefficiency, tool selection can appropriately become the next action.