Anuj Sharma, Sr. Customer Success Architect at Amplitude, says there are 3 important areas to a Data Governance function: “One would be Education. Second would be Instrumentation and third would be Maintenance.”
So you need to “Make sure you have enough documentation to educate your users, be it in terms of what your events mean, be it in terms of what your taxonomy naming conventions are.
There is instrumentation, which is making sure your devs understand those conventions and are ready to instrument that and follow the same standard across the entire instrumentation.
And finally maintenance, which is making sure that once you've instrumented your data, you're maintaining that taxonomy. You do need a regular cadence where you meet, you look at your entire taxonomy, make sure the events that you have are usable. If there are duplicates, you're cleaning those up. If there are events that no longer are used, you're hiding those from your taxonomy to reduce end user confusion.
Maintenance is an ongoing state. You've instrumented your taxonomy and maybe you followed all the best practices, but it's not necessarily that over time those best practices stayed intact.”
This is a snippet from Tracking Plan Tips: Event and Property Recommendations an Office Hours session with Ampliteer Anuj Sharma and Avo’s Thora Gudfinnsdottir who discuss data design, data governance, and tracking plans.
Related Tips:
