Page 50 -

Elements of Data Governance Programs 29

amendments to the United States Constitution. It’s easy to see the historical significance of the
application of these principles to United States history. It is the same for data principles (maybe a bit
less historical).
As you deploy DG, you will need to revisit and repeat your enterprise-level principles. Not revise,
but repeat. Since they are foundational and represent beliefs, repetition will be necessary. Figure 3-4
lists some sample principles we have collected. (Please note that in this book we refer to an organi-
zation named “Farfel.” This is the name of the fictional company we will occasionally use as a sample
case study where we are unable to reveal the real client.)

Policies

Another element we previously defined is policies. Policies are formally defined processes with
strength of supportdthat is, they are a codification of a principle. They give it “teeth.” Policies include
standardsdone area where IT personnel will be very intense as DG becomes real. Most likely, you
already have most of your DG policies floating around in the form of a disconnected IT, data, or
compliance policy. And, like most places, the policy sits happily in its notebook while life goes on and
the policy is disregarded. The marriage of principle and policy prevents this in the DG program.

Functions

We use the term function to describe the “what” has to happen in DG. This is done because early in the
DG program these functions will appear to be embedded in the DG “department” but over time they
need to evolve into day-to-day activities within all areas. Using the word “process” would immediately

FIGURE 3-4
Sample Principles.