In every dashboard project there comes a moment when one number is presented to leadership and two people in the room say it's wrong. They're both right — because they're counting different things.
Sales counts a deal when a contract is signed. Finance counts it when an invoice is issued. Operations counts it when it's delivered. Each definition makes sense inside its department, and together they turn every meeting into an argument about data instead of conclusions.
The fix isn't technical. It takes one meeting with the role owners that ends with a written definition for each key metric: what counts as an active customer, what counts as a closed deal, and when an enquiry counts as handled. One hour of argument saves months of distrust in the system.
Once the definition is settled, it has to serve every layer — the dashboard, the weekly report, targets and bonuses. If the target is calculated differently from the dashboard, people will stop looking at the dashboard.
One more small rule: every metric needs an owner. Not the person who builds it, but the person accountable for answering when someone asks why it dropped. A metric without an owner stops being maintained after three months.
The bottom line
A dashboard is the product of organizational agreement, not of connecting data. Without that agreement it just presents the argument more nicely.