Begin with the person making the decision
Ask which decisions a team makes each week and what information is missing. Design around those questions. A small number of well-defined measures often serves people better than a large page of charts.
Agree on the meaning of a number
Define each metric with its owner, source, refresh schedule, and exclusions. Reconcile sample results with the source system before publishing. When two teams use different definitions, resolve that difference explicitly.
Treat adoption as ongoing work
Review whether the dashboard is helping people take action. Remove unused views, make stale data visible, and provide a way to report discrepancies. The reporting product should evolve with the decisions it supports.