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:

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.

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

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

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…

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

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

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

Focus Areas for Data Governance: Data Warehouses and Business Intelligence (BI)

This type of program typically comes into existence in conjunction with a specific data warehouse, data mart, or BI tool. These types of efforts require tough data-related decisions, so organizations often implement governance to help make initial decisions, to...

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