Data governance
This page will outline some best practices around data governance
Last updated
Was this helpful?
This page will outline some best practices around data governance
Last updated
Was this helpful?
Data governance is a hot topic in the data space as it covers the ways to ensure that your company's data is secure, accurate, reliable, and accessible. There are many features and capabilities within Secoda that can help you achieve your data governance goals.
Here are some best practices to consider to enable data governance across your organization:
When rolling out a tool like Secoda, it is important to define roles within your organization and who will be taking on which responsibilities. This will ensure that every user knows what needs to be done so that the metadata within the product is accurate and up to date. It will also ensure that only the relevant people are able to edit and view certain resources that may be private. Consider these questions:
Who is a part of the initial group to enrich and implement Secoda? How are we delegating these tasks?
Who will be the data champions who will own the data resources? How do we define ownership?
Which users and stakeholders will we onboard? Which Teams do we need to create, and which resources will they need access to?
Once you have a grasp on the makeup of your Teams and users, can be assigned using our RBAC approach, owners can be set, and can be created. so that only the right users have access to editing the metadata in that Team. Enforce of critical data so that it is kept up to date.
It's important to start this initiative by identifying the data that most impacts your business. Consider these questions:
What data is most critical to your business?
Which reports and dashboards are relevant and up to date?
What are questions that pop up all of the time?
Start here since they are more likely to have a larger impact on more users.
Your users should feel confident using and accessing the right data, but we often see questions and concerns like:
What does this data mean?
Where can I find data on this subject?
Who's responsible or the subject matter expert?
Is this the right data?
Is it up to date?
Is this sensitive data?
This is why enrichment is so important to Secoda, and if done well, should answer all of the questions above. Add descriptions, ownership, and tagging to make your important resources easier to locate when searching within Secoda. Define standards for your editors to follow so they know which types of metadata needs to be included in their documentation. Some of this can be addressed by creating Templates for documentation!
In summary, the team uses the following strategies to work towards their data governance goals:
Another way to identify critical data elements once you've integrated your data into Secoda is by using our . Users can look at the overall lineage and see which are some key nodes that touch a lot of parts of a pipeline. They can also make note of important data resources and make a note of anything upstream of that asset, as it shouldn't also be marked as critical since it's dependent on it.
metadata could be another important field to look at since usage data can help us understand what's most important to the business. Read more about these ideas here: .
Consider using our on resources that have checked the box on each of those questions, indicating that it is ready for use by your Members. Using this system will provide your users confidence and reliability in using the data. Check out some tips on implementing a Defining resources workflow at your organization!
To enable security measures, use our to tag sensitive resources to alert Members in your workspace. An Automations can be created that automatically tags new resources with certain qualities, as PII.
They organized the workspace so that each team has their own which acts as a single source of truth for all of their documentation
They map every table to a Collection , and ensured that every table has a defined
Tip: Try out to push new tables into the right Collection, and set the owners automatically
They rely heavily on for understanding downstream impacts of their schema changes
They use as well as to notify relevant stakeholders about changes
They have a very defined workflow using our where documentation criteria is required by the developer in order to create new tables and push them to Secoda
