4/2/2024

DG Function
Introduction

4/2/2024 Data Governance & Ethics 292

DG Function
A day in the life

In order to better understand how DG works - and to be able to paint

that picture to an executive you’re trying to pitch - it’s important to be
able to explain what happens, in terms of DG, in an “usual” day in the
life.

4/2/2024 Data Governance & Ethics 293

 4/2/2024

DG Function
A day in the life

Let’s start with the data owner. Let’s say they are the CMO,
responsible for data in the Marketing department.
- They receive their reports from Data Stewards, who indicate there
may be occasional Data Quality (DQ) issues;
- For example, issues with data regarding a prospect list from a
specific event, which has the prospect address in the wrong
format;

- They provide a remediation suggestion + deadline;

3/29/2024 Data Governance & Ethics 294

DG Function
A day in the life
The Marketing executive receives this report and may review the expected Data
Quality rules for this prospect list, since an important report must be generated
from it.
- The rules are: “Every Prospect must have a full address across 3 DB fields. An
address text field, a house number field, and a zip code number sequence field with a
specific length”;
- The data steward report suggests that the data from this prospect list are 80%
complete, but the other 20% are lacking a valid address, or it’s in the wrong
format;
- The Marketing executive needs this DQ issue fixed to consider this a “Trusted” data
source and generate reports;
3/29/2024 Data Governance & Ethics 295
 4/2/2024

DG Function
A day in the life

In order to remedy these data, the Data Steward (DS) coordinates with the
Data Management (DM) team, who creates a project to parse and
standardise addresses, and for prospects with missing addresses, they request
business analysts present in the event to get in touch with the person and
confirm the address.
After this project is complete, the Data Stewards mark the source as being
“Trusted”, with 95% completeness, and a report on prospects by job title
and company location is generated by the Marketing Department.

3/29/2024 Data Governance & Ethics 296

DG Function
A day in the life

The same Data Stewards (DS) may do a random quality check on

the report data, specifically a Consistency one (matching if the
same data are present in the raw DB versus the report), and they
find out that some information has been transformed - that is, the
total prospects by country are not the same in the DB and the
report.
- Maybe in the DB, we have 660 US prospects, and in the
report we have 620;

3/29/2024 Data Governance & Ethics 297

 4/2/2024

DG Function
A day in the life

The DSs coordinate with DM, who clarify that a truncation was
made of some duplicate prospects, which were not detected -
therefore, the report is the correct source.
- DS informs the data owner (the CMO) of this, who suggests a
new policy to filter duplicates at the data capture stage;

3/29/2024 Data Governance & Ethics 298

DG Function
A day in the life

This new policy allows the Marketing department to eliminate duplicate

prospects in future situations.
- In order to get this approved, however, the CMO needs the approval of
the Data Council, which in this case may include the CEO,CIO,
CISO and Legal Counsel;

3/29/2024 Data Governance & Ethics 299

 4/2/2024

DG Function
A day in the life

In their monthly meeting, where each data owner presents a list of DQ

issues prioritised by severity, and with remediation roadmaps and
deadlines, the CMO brings up the new policy to prevent duplicate data
at the creation stage.
- This is validated by the Council, and the CMO coordinates with the
CIO,who tells the DM team to reconfigure the automated DQ
monitoring tool to validate the data;

3/29/2024 Data Governance & Ethics 300

DG Function
A day in the life

This change is made, and the Marketing Data Stewards oversee the
rules in action for future data creation, when new events occur,
concluding the process works well and DQ has been increased.
- The CMO can, in fact, take the performance metrics, which indicate
that prospect data from events have increased in DQ, on average,
from 80% to 87% at the creation stage, through this new policy, and
uses it show DG value, tying it to sales obtained from prospects
with accurate data;

3/29/2024 Data Governance & Ethics 301

 4/2/2024

DG Function
A day in the life

Each data owner, including the CMO, informs their Data Stewards of the new
policy, requesting them to document it in the enterprise metadata hub, and ask
them to oversee data disposal operations to reflect this.
- In the Marketing department, the Data Stewards may even find out that the
required retention dates are not included in the datasets, so they suggest a
policy to include that information in these, which is validated by the CMO and
later approved by the Data Council;
This new information makes the job easier for the DM team, who can, when
purging a data set, simply look at the metadata, showing the retention deadline,
performing the deletion with more accuracy and trust.
3/29/2024 Data Governance & Ethics 302

DG Function
A day in the life
Examples

/01 DATA STEWARDS BRIDGING

Once again, we see Data Stewardship as the
“bridge” between DM and DG, here in practice.
They help implement DG, and generalize
feedback from DM. /03 ATTENTIVE DATA OWNERS
In this example, we also noticed how the data
/02 DATA COUNCIL DECISIONS owner (the CMO in this case) must pay attention to
While many aspects, such as regulation and DQ issue resolution, to DG implementation, and a
technology, can affect data policies, the Data lot more.
Council is who makes decisions that cascade down
3/29/2024
from there. Data Governance & Ethics 303
 4/2/2024

DG Function
A day in the life
Key Takeaways /02 DATA STEWARD INSIGHTS
DSs play an important role here, by mediating
/01 DQ ISSUE MONITORING
between the data owner, which directs policies
In everyday operations, a significant part of the
and processes, and providing feedback from
time for a data owner will be monitoring DQ
issues found.
problems. What are they, how are they fixed, and
by when?

/03 UP AND DOWN THE SCALE /04 ANY STAGE OF THE LC

Feedback collected bottom-up by DSs goes up DG issues (and changes) may occur at any stage
the data owner to the other executives and of the data life cycle. Creation, storage, usage,
Data Council, and the decision is reflected top- disposal, or any combination of these.
down again.

3/29/2024 Data Governance & Ethics 304

Data Governance
Goals

3/29/2024 Data Governance & Ethics 305