Most organizations have string change management – or at least change control – mechanisms for technology. They usually have change management for software applications. They have change management for websites. And yet, many organizations do not practice structured change management for data.

Implementing Change Management

Why is this important? Some types of data – master data and reference data – should have tightly controlled sets of valid values. These values appear in thousands and millions of transactions; without change control, different repositories storing master and reference data get out of sync.

One role of Data Governance is to set the scope of data-related change management and to oversee change management activities.

 

Examples of data-related change management are:

  • Changes to allowable values for reference tables
  • Changes to physical data stores that impact the ability to access or protect in-scope data
  • Changes to data models
  • Changes to data definitions
  • Changes to data structures
  • Changes to data movement
  • Changes to the structure of metadata repositories
  • Changes to types of metadata included in a metadata repository
  • Changes to stewardship responsibilities

Some of the organizations I’ve assisted have wanted highly-structured, step-by-step change management processes. Having such processes have helped train participants to sync up their activities, and they’ve helped prove to auditors that formal, auditable processes were being followed.

Other organizations did not feel the need for documented processes. These groups were used to managing other types of change; for them, applying this to data was not a stretch.

Another organization I worked with felt it would be considered oppressive to ask all its business units to commit to formal change management. Instead, it set a requirement for change notification. Data Stewards were asked to notify the Data Governance Office (DGO) about certain types of changes. Then the DGO would communicate the changes to all known data stakeholders and would collect feedback about potential issues. If needed, the DGO would facilitate discussions about impacts and issues.

Read Next:

Governance and Decision-Making

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

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

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.

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

Dealing With Politics

It’s essential that Data Governance and Stewardship program facilitators avoid being “caught up” in politics. It’s our jobs to acknowledge the realities of the situations we work with, while avoiding taking sides or engaging in behaviors that could be perceived as favoring one set of data stakeholders at the expense of others.

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

Data Governance Program Phases

As you perform the activities needed to gain support and funding, remember that your program may plan to address multiple focus areas. Each new effort should be introduced using the seven steps of the life cycle. Even specific governance-led projects, such as creating a set of data standards, will want to follow the Data Governance Life Cycle steps.

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…

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