A large multi-state energy utility had invested in cloud and analytics, but adoption lagged and data ownership was unclear. We institutionalized governance, built persona-based literacy paths, and formalized change management, so decision-making stayed consistent across domains and the capability outlasted the engagement.
Data governance moved from fragmented, siloed practice toward a managed enterprise model, with change management maturity advancing from 2.7 toward 4.0.
Inconsistent data ownership left stewardship and quality accountability ambiguous, and tool-centric training had not changed how people actually worked.
A domain ownership framework, persona-driven literacy paths, a formalized OCM playbook, and a benefits framework tying initiatives to named owners and KPIs.
Data governance moved from fragmented, siloed practice toward a managed enterprise model, with change management maturity advancing from 2.7 toward 4.0.
Formal domain ownership and stewardship roles with defined responsibilities and measurable goals. Governance councils and escalation paths strengthened accountability and improved data quality standards.
A persona-driven learning architecture aligning roles to responsibilities and decision impact. Structured pathways embedded literacy into professional development rather than one-off sessions.
Standardized playbooks, stakeholder engagement models, and unified KPIs. Change accountability was embedded across initiatives so adoption was somebody's job rather than everybody's hope.
Initiatives linked to measurable outcomes with accountable owners and KPIs tied to revenue, efficiency, and compliance. Centralized tracking held value in view past the implementation milestone.
Structured learning forums and leadership-led reinforcement to sustain data-driven behaviors, with experimentation and accountability built into daily operating rhythms.
Standardized roles, KPIs, and operating procedures to extend governance across business units while preserving local flexibility.
The utility had already spent the money. Cloud was in place, analytics was in place, and adoption still lagged. That pattern is usually mistaken for a tooling problem, and it usually is not one.
What was missing was ownership. Inconsistent data ownership created ambiguity in stewardship and quality accountability across domains, so when a number looked wrong there was no obvious person to ask. Governance was siloed and reactive, which slowed enterprise decision-making rather than protecting it. Uneven change management maturity meant adoption varied by whoever happened to be leading a given initiative.
Training had been tried and had not stuck, because it was built around tools. Tool-centric training teaches people which buttons exist. It does not change the behavior or the operating model around the work, so the skills decay quietly.
We built the program around roles instead. A persona-driven learning architecture aligned each role to its responsibilities and to the decisions it actually influences, and those pathways were embedded into professional development rather than delivered as an event. Alongside it, formal domain ownership gave every domain named stewards with measurable goals, and governance councils gave escalation somewhere to go.
The last piece was measurement of the program itself. Initiatives were linked to accountable owners and KPIs tied to revenue, efficiency, and compliance, tracked centrally so value stayed visible after go-live.
Where to next
