W3_ANLY640_Example

Example:

Data-Driven Decision Making

Select the Start button to begin

Start

Select the Listen button to play the narration for this slide

Navigation

Listen

buttons

Use the following buttons to navigate through the course content

Listen

Play the audio for the current page

hOME

nEXT

PREVIOUS

Return to the previous page

Return to the course home page

Move to the next page

home

next

previous

Select the Listen button to play the narration for this slide

Listen

Hi, my name is Harper, and I want to share an experience from my time as Senior Director of Enterprise Data Programs at Atlas Financial Services, a mid-size insurance and wealth management company serving clients across the mid-Atlantic region. This experience taught me that the most critical phase of any data governance initiative is not implementation. It is the initiation, because how you build the foundation and launch the program determines everything that follows.

home

next

previous

Select the Listen button to play the narration for this slide.

Listen

Part I - The Situation

Atlas Financial Services had attempted to launch a data governance program twice before I joined. Both attempts followed the same pattern.

A data quality crisis would trigger executive concern; a team would be assembled, ambitious plans would be drafted, and within six months the initiative would quietly dissolve as organizational attention shifted to other priorities.

home

next

previous

Select the Listen button to play the narration for this slide.

Listen

The Situation

The first attempt had been led by the IT department and was perceived by the business as a technology project that did not understand business needs.

The second attempt was led by the compliance department and focused so narrowly on regulatory requirements that it failed to demonstrate value to business units that did not face direct regulatory pressure.

home

next

previous

Select the Listen button to play the narration for this slide.

Listen

The Situation

When I was brought in, the CEO was clear about the situation.

The organization needed data governance; everybody acknowledged that fact, but nobody believed it could actually succeed because two previous failures had created deep organizational skepticism.

My mandate was not just to build a governance program but to build one that would survive the inevitable moment when executive attention turned elsewhere, and competing priorities began to erode support.

That meant I needed to get the initiation right in ways that both previous attempts had failed to do. I also needed to build trust in the data so organizationally this attempt would stick.

home

next

previous

Select the Listen button to play the narration for this slide.

Listen

Part II – The Shift

The first thing I did was resist the pressure to start building.

Everyone wanted to see action immediately, but I spent the first eight weeks focused entirely on three activities: building the right scope, securing the right sponsorship, and assessing organizational readiness.

For scope, I conducted interviews with leaders from every business unit to understand their specific data pain points. Rather than defining governance scope based on what the textbook said it should cover, I built scope based on what the organization needed.

home

next

previous

Select the Listen button to play the narration for this slide.

Listen

The Shift

The wealth management division was struggling with client data that was fragmented across three systems, making it impossible to provide holistic financial advice.

The insurance underwriting team was making pricing decisions based on actuarial data that was eighteen months out of date because nobody owned the refresh process.

The compliance team was spending forty percent of its time manually compiling regulatory reports because the data they needed was scattered across incompatible systems.

home

next

previous

Select the Listen button to play the narration for this slide.

Listen

The Shift

For executive sponsorship, I deliberately avoided the pattern of both previous attempts. Instead of anchoring governance in a single department, I built a governance council with co-sponsors from IT, compliance, wealth management, and insurance operations.

Each co-sponsor had a personal stake in governance success because it would solve a specific problem in their domain.

This was not ceremonial sponsorship where an executive lent their name to a project they did not care about. It was invested in sponsorship where each leader had committed governance because it directly addressed a pain point; they could not solve without it.

home

next

previous

Select the Listen button to play the narration for this slide.

Listen

The Shift

For organizational readiness, I conducted a detailed assessment that examined data maturity, leadership support, resource availability, and change readiness across every department. The results were sobering but essential.

• Three departments had strong data cultures and would be early adopters.
• Two departments were neutral and would follow if they saw results.
• Two departments were actively resistant because they viewed governance as bureaucratic overhead that would slow down their operations.

home

next

previous

Select the Listen button to play the narration for this slide.

Listen

The Shift

Rather than ignoring the resistance or trying to overcome it immediately, I designed the program to launch in the three receptive departments first, building tangible results and case studies that would gradually convert the neutral and resistant departments through demonstrated value rather than executive mandate.

home

next

previous

Select the Listen button to play the narration for this slide.

Listen

Part III – Results

The phased approach based on honest readiness assessment proved transformative. Within six months of launching in the three receptive departments, the wealth management division had unified its client data and could demonstrate a twelve percent increase in cross-selling revenue directly attributable to having complete client profiles.

• The insurance underwriting team had implemented automated data refresh processes that eliminated the eighteen-month lag and improved pricing accuracy by eight percent.
• The compliance team had reduced manual report compilation time by sixty percent through governed data pipelines that automated data collection and formatting.

home

next

previous

Select the Listen button to play the narration for this slide.

Listen

Results

These results did exactly what I had designed them to do. The neutral departments saw tangible value and requested inclusion in the governance program. Even one of the two resistant departments approached my team to explore how governance could address their data integration challenges, because they saw their peers benefiting and did not want to be left behind.

By the end of the first year, all seven business units were participating in the governance program voluntarily, and the governance council had become one of the most influential cross-functional bodies in the organization.

home

next

previous

Listen

Select the Listen button to play the narration for this slide.

Part IV - Takeaway

The Atlas experience taught me three essential lessons about building and initiating data governance.

First, scope must be built from organizational reality, not from governance frameworks found in textbooks.

The right scope is the one that addresses the specific data problems that business leaders care about, because scope that aligns with strategic objectives earns the sustained investment that governance programs need to survive.

home

next

previous

Listen

Select the Listen button to play the narration for this slide.

Takeaway

Second, executive sponsorship must be invested, not ceremonial. Sponsors who have a personal stake in governance success because it solves their problems will defend the program when competing priorities threaten to divert resources.

Sponsors who agreed to attach their name without genuine investment will abandon the program at the first sign of organizational headwinds.

home

next

previous

Select the Listen button to play the narration for this slide.

Listen

Takeaway

Third, organizational readiness is not an optional assessment. It is strategic intelligence. Understanding where the organization is ready, where it is neutral, and where it is resistant allows you to design launch strategies that build momentum through early wins rather than stalling against organizational barriers that could have been anticipated and addressed.

home

next

previous

Select the Listen button to play the narration for this slide

Listen

Congratulations!

You've successfully completed the example

home

previous