The truth hierarchy, the burden of the proof on the new model.

We also enforced a dashboard “truth hierarchy”, that is, if in the process of exploring data in Looker, a stakeholder developed a metric that “disagreed” with a metric already established in the canonical dashboards, the burden of proof was on them to understand the misalignment. The data team was available to help with quick investigations through a company Slack channel, but the goal was to teach stakeholders how to fish and to avoid having to spend all of their time chasing down numbers that didn’t quite agree

Meeting engineering in the middle:

To balance the data team’s bottom-up approach in developing data models in Looker, my focus while wearing a Data Product Manager hat became creating a top-down vision that could drive development from the point of view of the business needs, with the goal of meeting engineering somewhere in the middle.