Seek first to understand, then to be understood. We want to drive our team toward discussion, not argumentation. This is why listening to their perspectives first is important, so we can gauge their level of understanding of the data insights. Data insight is not just about collecting and viewing data; it's about interpreting it to uncover patterns, trends, or correlations that can inform decision-making. By knowing our team's level of understanding, we can align their perspectives so that everyone has the same level of comprehension.

Working for a data heavy company, i can tell you for sure that stabilizing " the source of truth " is relevant. Choose well, and stay with your choice unless proven wrong. Finance should be your best friend for anything data.

Rather than relying on subjective views, emphasize decisions based on clear, relevant data. Use agreed-upon metrics and analytics to evaluate solutions. This can neutralize debates and shift the conversation toward factual information.

When debates arise, redirect the conversation back to the primary objective. For instance, if team members are debating technical features, remind them: “At the end of the day, the goal is to solve the customer’s pain points. How does this feature impact the solution’s overall value to the customer?