Your quote “Taking that extra time to making sure you’re doing the right work instead of doing the work right is often some of time best spent” is great. People in any domain should ask themselves whether they're working on the right stuff all the time.
That's awesome. I really like how the GitLab team has made it all public. I actually had a chat with Rob Parker who runs their data team a while back and they've really thought their stuff through
I don't know if you've seen this before, but GitLab's Data Team (and the company in general) maintains a public handbook (https://about.gitlab.com/handbook/business-technology/data-team/). Based on my reading of that resource, it seems like GitLab applies some of the principles you mention. For instance, "Every data asset should have an owner" and "Close the loop to data producers with shared ownership so issues are caught as far upstream as possible" seem to be in line with their platform page that lists out their data sources (https://about.gitlab.com/handbook/business-technology/data-team/platform/#data-sources) as well as their definition of "tiers" (https://about.gitlab.com/handbook/business-technology/data-team/platform/#tier-definition).
Your quote “Taking that extra time to making sure you’re doing the right work instead of doing the work right is often some of time best spent” is great. People in any domain should ask themselves whether they're working on the right stuff all the time.
That's awesome. I really like how the GitLab team has made it all public. I actually had a chat with Rob Parker who runs their data team a while back and they've really thought their stuff through
The handbooks are quite impressive. I've taken quite a bit of inspiration from them and started our own version at the company where I work.
Another great post Mikkel. What makes you lose time on getting access to data?