Remember our (long) definition for Data Governance?

“Data Governance is a system of decision rights and accountabilities for information-related processes, executed according to agreed-upon models which describe who can take what actions with what information, and when, under what circumstances, using what methods.”

Focus on Architecture

Yes, Data Governance is about enforcing rules. But just as important, usually, is ensuring that the right stakeholders are involved in making the rules.

Sometimes – especially for compliance-related rules – it’s easy to know who should decide on a rule. But other times it’s hard. And most organizations have lots of examples from their own histories of decisions that were made without input from key stakeholders. They can tell stories of the problems created when the right groups were not consulted.

So a best practice is that before any rule is created or any data-related decision is made, a prior decision must be addressed: who gets to make the decision, and when, and using what process?

This practice is called establishing “Decision Rights” for the decision.

It is the responsibility of Data Governance program facilitators to know (or discover) who should be involved in making different types of governance decisions. It is also generally a responsibility of the program to facilitate (and to sometimes document and store) the collection of decision rights that are the “metadata” of data-related decisions.

Read Next:

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 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: 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...

Focus Areas for Data Governance: Data Quality

This type of program typically comes into existence because of issues around the quality, integrity, or usability of data. It may be sponsored by a Data Quality group or a business team that needs better quality data. (For example: Data Acquisition or  Mergers &...

Focus Areas for Data Governance

All Data Governance programs are not alike. Quite the contrary: programs can use the same framework, employ the same processes, and still appear very different. Why is this? It’s because of what the organization is trying to make decisions about or enforce rules for....

Governance and Issue Resolution

One of the three most important jobs of a Data Governance program is to help resolve data-related issues. These may be conflicting data definitions, data usage concerns, or problems with how data is sourced, how it is integrated, how it is protected, or a myriad of...

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.

Focus Areas for Data Governance: Privacy, Compliance, Security

This type of program typically comes into existence because of concerns about Data Information Security controls, or compliance. Compliance, in this context, may refer to regulatory compliance, contractual compliance, or compliance with internal requirements.This...

Assigning Data Ownership

One of the tenets of Data Governance is that enterprise data doesn’t “belong” to individuals. It is an asset that belongs to the enterprise. Still, it needs to be managed…

Focus Areas for Data Governance: Management Alignment

This type of program typically comes into existence when managers find it difficult to make “routine” data-related management decisions because of their potential effect on operations or compliance efforts.Managers may realize they need to come together to make...