fbpx
Search
Close this search box.

Getting Started with Data Governance: Best Practices

Data Governance Best Practices
Share This Post

Data Governance Best Practices In a recent blog, we discussed effective data governance best practices and Master Data Management (MDM) procedures that enhance enterprise business intelligence, data security, and compliance with data-related regulations. By carefully stewarding its data assets, an organization can ensure that the right people always have easy access to high-quality, complete, and consistent data sets. Given the volume, velocity, and variety of data being gathered by today’s digitally transformed organization, implementing enterprise-grade Data Governance and Master Data Management policies is a complex and often daunting process. And, like most challenging journeys, the first steps are always the hardest. In this post, we provide some best practices for organizations seeking to initiate or expand their DG processes.

Laying the Foundation for Data Governance Implementation

Congratulations! You have been given the mandate by senior management to lead your company’s Data Goverance implementation. In order to lay the foundation for success, there are two crucial things to take care of: (a) assembling the right team, and (b) clarifying the company’s DG goals. DG is not a one-person job. Many companies establish a “data governance council” or a “data stewardship committee” to implement and oversee the company’s Data Governance and Master Data Management frameworks. The team must have the right skill set (data systems, IT, legal), experience and authority across the full range of DG stakeholders in the company—that is, all of the departments and positions that require high-quality, trustworthy data to do their jobs well. The stakeholder list will typically comprise production, QA, HR, operations, finance, accounting, marketing, sales, and more. Once the team is established, the first task is to make sure there is clarity in the company regarding the goals and measurable objectives of the DG/MDM implementation. What are the current data and business intelligence “pains” that need to be addressed? What are the pros and cons of the existing data management policies and practices across the organization? How can improved DG/MDM enhance the company’s ability to understand its customers, improve its marketing campaigns, manage risk, lower operational costs, and so on? At the end of this stage, there should be a well-documented statement of purpose and objectives that reflects the needs and goals of all the major stakeholders.

Detailed Data Governance Planning

Now it’s time to roll up your sleeves and come up with a detailed DG/MDM plan, including:
  • Rigorous classification of the company’s data assets: Each data type has its own role within the organization. This will determine the level of quality it must attain, who can have access to it, how long it has to be kept easily accessible, and what security measures must be put in place to keep it safe.
  • Define data-related enterprise roles and responsibilities: The same data set may be used by different departments in the business for different purposes. For example, sales data is “owned” by the sales department where it is used intensively for a variety of purposes such as assessing personal performance and setting quotas. The marketing department, on the other hand, also needs access to sales data in order to assess the impact of its campaigns. The levels of access to the sales data need to reflect these different business roles.
  • Develop standardized data definitions: The entire company should have the same understanding of what constitutes a customer, a lead, a vendor, an employee, and so on.
  • Map out the infrastructure architecture and tools: This is necessary to collect, clean, analyze, store, and protect the company’s data assets. The goal should be high-performing, self-service access with nuanced permission controls.
  • Develop the operational model, including data-quality-assessment procedures: How often will a data set be audited? By whom? What are the quality measures that will be applied? How will problems and issues be recorded and remedied?
Get as many people as possible involved to improve the quality of the detailed plan, and to ensure buy-in from management and staff across the organization.

Jump Right In – Let’s Start Implementing Data Governance!

Now comes the moment of truth: It’s time to start implementing the plan. Don’t let the vast scope of the undertaking overwhelm you. You and the team should start with one or two well-defined business cases and use them as a pilot. You’ll learn from the process and hopefully get some relatively quick successes that will demonstrate the ROI and create an appetite for more of the same.

A Final Note on Data Governance Best Practices

DG/MDM is a marathon and not a sprint. It is very important for data stewards to take the long view as you continue to implement the Data Governance plan; oversee and audit processes and policies, and respond to the changes that will inevitably take place as the company’s business needs evolve. With the countdown to GDPR already in place, Enterprises may be feeling pressure to ensure compliance and implement data governance best practices before the onset of the new law. It is important to take care of your immediate holes in security and data compliance and then plan out how things can be improved on a longer-term basis. The real success will be when data governance best practices have become part of the enterprise’s and a data stewards’ DNA: Everyone in the organization should feel like a data champion and take responsibility for discovering and correcting data quality problems. It is at that stage that the enterprise will truly start to reap the benefits of high-quality, accessible, and secure data assets.]]>

Next step

The easier way to recover cloud workloads

Allowed us to save over $1 million in the management of AWS EBS snapshots...

Every 11 seconds, a company is hit by ransomware...

Learn an uncommon strategy for protecting your AWS cloud in this expert-led webinar

immutable backups webinar on demand

N2WS vs AWS Backup

Why chose N2WS over AWS Backup? Find out the critical differences here.

N2WS in comparison to AWS Backup, offers a single console to manage backups across accounts or clouds. Here is a stylized screenshot of the N2WS dashboard.