Page 110 -

Overview 89

Business Benefits and Ramifications

We stated earlier that some resistance to DG is inevitable. This step consolidates the reasons you need
to do DG. In conjunction with the elevator speech, you are beginning to develop the compelling
message that will be required for successful organizational change.
Approach Considerations

Take the time to consider business needs, as well as the other information mentioned earlier, in
a formal manner. Do not throw it all in a document and say, “there it is.” Remember, DG is all about
making sure that information asset management is being done, so you need to examine all of the points
where information management affects what the business wants to accomplish. At a minimum, you
should break major business needs into subject areas or content used and identify what types of
policies and standards may be required.
Sample Output

FIGURE 8-5
Sample Initial Data Governance Requirements.
Tips for Success

Sadly, we often run into a lack of transparency when trying to align business needs with information
management pursuits, including data governance. If your organization is the sort where IT is told to
“do what you are told,” and information has evolved into the inevitable rat’s nest of applications and
shadow IT, look to external sources. Most industries have trade journals. Many companies must
publicly disclose intentions. Use this type of data to interpolate a business plan.
Activity: Develop Future Representation of DG

The DG requirements will enable the team to get an idea of where and how DG will enable business
activity. This activity is where the team designs a clear representation of what that “day-in-the-life”
will look like. The emphasis is again on simple and straightforward.