Page 63 -

42 CHAPTER 5 Process overview for deploying data governance

understanding is once the “proof” (i.e., a business case) is shown, there is acceptance that DG is designed and
deployed in the context of an enterprise, not a business area.

Whether or not you use the term EIM, DG is crucial for managing information as an asset. The
other path to DG is as a component of an EIM effort.
Lastly, DG can stem from concerns originating from a specific set of content. Strangely, while
structured or “row-and-column” content is the first target of DG, many companies find themselves
building fine DG programs when they clean up and manage documents. Databases and “row-and-
column” data sets are governed long after non-structured content, or a regulatory surge makes
a company focus on a specific subject area. This happened in 2009–2010 as fallout from the mortgage
crisis and recession. Suddenly, DG became “hip.”

THE DG “METHODOLOGY”

While we show eight distinct phases, the process for starting and sustaining DG is shown as a cycle
because it is usually iterative. Obviously, we need to show what the entire process looks like, but you
will execute all or part of this cycle several times. Additionally, you will not do every step the same way
every time.
Many factors contribute to how the DG programs rolls out:
1. Are you doing DG as part of a single master-data-management effort? If you are doing a typical
project to consolidate customer data, you may have to focus your governance on the MDM event.
Your organization may not yet have an appetite for enterprise DG. You will execute the entire
process, albeit on a more limited scope. This does not mean you treat the DG program as a stand-
alone effort. (Remember that you are doing EIM, even if you are not using the name.) Often, there
is another MDM project on the heels of the first one (assuming they are successful). Then you will
immediately see why DG needs to be treated with an enterprise perspective, regardless of its roots.
2. Do you work in a very large company? If so, our guess is you have simultaneous instances of DG
percolating. They may not all be called DG, but they are there. A uniform process allows various
efforts to leverage and combine their efforts under a common protocol.
3. Do you have a formal EIM program or IM area? If so, you will execute this approach probably once to
stand up the larger DG “area,” and then several times as you support various projects requiring DG.
Therefore, the process we are going to review is not a recipe, but rather a methodology that needs to be
adapted to your situation.

PROCESS OVERVIEW

There are eight steps or phases to our stand-up process. As we stated earlier, this is a more granular
2
process that focuses on the actual “how-to.” This and subsequent chapters will be fairly detailed.
2
We are always asked at conferences or by clients to provide “how-to” advice. Admittedly, it seems many consultants tend
to provide “box and arrows” solutions, and seem to be scarce when the hard questions are being asked. To be fair, you
cannot understand the detailed steps unless you get a good dose of “box and arrows” learning. So, the earlier chapters were
the framing chapters. Now it is time for the details. Remember, you asked for this. You have been warned.