Scenario 24 — Capstone: Governance Transformation Keeps Stalling
Situation
A global company has recurring Data Quality incidents. Leaders bought a governance platform and announced “one source of truth,” but local teams keep old processes. Staff were not involved, regions fear loss of authority, the CDO is the only sponsor, no coalition exists, the vision is a technology slogan, communication is one-way, the successful pilot is treated as proof the work is finished, mainstream teams see no visible benefit, and the regulatory driver is fading.
Seven-part resolution
1. Primary problem
Multiple people-side failures: technology-as-change, imposed change, weak coalition, weak vision, communication credibility, premature victory, diffusion gap and sustainment risk.
2. Leading chapter
Data Management and Organizational Change Management.
3. Supporting areas
Data Governance; Data Quality; Organization & Roles; Metadata/Technology.
4. Roles
CDO/sponsor; Guiding Coalition; Change Agents; regional leaders; Early Adopters; communicators.
5. Best rebuild 1. Understand current history and subjective losses; do not dismiss why regional processes exist. 2. Manage Bridges transition—especially loss and Neutral-Zone ambiguity. 3. Establish focused urgency without panic. 4. Build a credible coalition beyond the CDO. 5. Replace the technology slogan with a business-outcome vision. 6. Communicate simply, repeatedly, in many forums, two-way, and through aligned leader behavior. 7. Define credible first steps and remove structural/psychological resistance. 8. Treat the pilot as a short-term win—not completion. 9. Make relative advantage observable and trialable so Early Majority can move. 10. Broaden sustainment beyond the original regulatory driver. 11. Build audience-specific communication using the 12-element plan and behavior-focused metrics.
6. Tempting weaker response
Mandate platform use and declare the pilot the enterprise template. That repeats several diagnosed Chapter 17 errors and can increase resistance.
7. Changed fact
If coalition, vision, mainstream adoption and anchored behavior are already strong and only one region has a legal technical constraint, the leading issue shifts to managing/explaining a legitimate exception and local implementation.
Source: Chapter 17, pp. 541–575.