Starting a Data Governance Program

Getting Started

A successful Data Governance program does not begin with the design of the program!

Before you start deciding who goes on what committee, you should be clear about your program’s value statement.
You should have developed a roadmap to share with stakeholders.

Starting a Data Governance Program

Those stakeholders will want to know the WHO / WHAT / WHEN / WHERE / WHY / HOW of your program before they decide to support it, so you’ll need to anticipate their questions and have preliminary answers, even if they’re only assumptions until you do your actual program design.

You’ll want to build the type of program that your stakeholders will be excited about. The Data Governance programs we’ve seen that are the most successful are ones with a clear focus, metrics that excite leadership, a value proposition that everyone can get behind, and a clear message.

Don’t worry if this isn’t real obvious to you. After all, we’re all familiar with the concept of not being able to see the forest for the trees. What if you ARE one of the trees?

Consider getting a fresh viewpoint from someone within your organization (or from outside) who can help you describe your vision and set an approach to:

Develop a value statement
Prepare a roadmap
Plan and fund
Design
Deploy
Govern
Monitor, measure, report

Read Next:

Goals and Principles for Data Governance

What do you want Data Governance to accomplish? Regardless of the focus of your program, chances are you hope to accomplish the following universal goals for Data Governance programs: Goal – Enable better decision-making Goal – Reduce operational friction Goal –...

Choosing Governance Models

It’s important to define the organizational structure of your Data Governance program. But before you can do that you have to define your governance model at a higher level. You need to consider what types of decisions your governance bodies will be called upon to...

Working with Data Stewards

Approaches to Assigning Data Ownership and Stewardship Organizations can take multiple approaches to assigning Data Owners and Data Stewards for enterprise data. In doing so, they need to consider several factors and answer the following questions.Question #1: Should...

Defining Organizational Structures

There is no single “right” way to organize Data Governance and Stewardship. Some organizations have distinct Data Governance programs. Others embed Data Governance activities into Data Quality or Master Data Management programs.

Governance and Alignment

Data Governance is a balancing act. On the one hand, you need to exert control over how groups create data, manage data, and use data. On the other hand, you need to promote appropriate levels of flexibility. You need to ensure that data-related efforts support the...

Demonstrating Value

Everything an organization does should tie to one of three universal value drivers. Data Governance efforts MUST tie back to one or more of these drivers. And YOU must communicate how it does.

Engaging Stewards and Stakeholders

It seems like there are two types of Data Governance and Stewardship programs: Thriving ones, with highly-engaged stakeholders, and Ones whose futures are in question, since stakeholders and stewards are only sporadically involved or give only weak support to the...

Focus Areas for Data Governance: Architecture, Integration

This type of program typically comes into existence in conjunction with a major system acquisition, development effort, or update that requires new levels of cross-functional decision-making and accountabilities.What other types of groups and initiatives might want...

Governance Communications

At a Data Governance Conference in Orlando, Florida (USA), a group of managers of successful Data Governance programs reached a startling consensus: They agreed that Data Governance is actually somewhere between 80 and 95% communications!How can this be? They said...

Focus Areas for Data Governance: Policy, Standards, Strategy

This type of program typically comes into existence because some group within the organization needs support from a cross-functional leadership body. For example, companies moving from silo development to enterprise systems may find their application development teams...