Teams often ask for a dashboard before they agree on what a number means. Then Monday’s meeting spends twenty minutes arguing whether “active customers” includes trials, paused accounts, or last-month churn.
The BI tool didn’t fail. The KPI was never defined.
Start with the decision
Ask: what will someone do differently if this number moves? If the answer is vague — “we’ll monitor it” — it’s not a KPI yet. Good KPIs tie to a decision: reallocate budget, escalate a team, pause a campaign, fix a process.
Write the formula in plain English
Before any SQL or pivot table, document: numerator, denominator, filters, time window, and exclusions. “Revenue” might mean invoiced, collected, or recognized — and finance, sales, and ops often mean different things.
Assign one owner per KPI
Someone must defend the definition and sign off when it changes. Shared ownership usually means no ownership. The KPI owner also owns the exception list when numbers look wrong.
Pick one source of truth
ERP says one thing. CRM says another. The dashboard should declare which system wins for each metric — and when reconciliation happens if they disagree.
Ship a one-page KPI dictionary first
Name, definition, formula, owner, source, refresh cadence, and who consumes it. Build the dashboard after leadership agrees on that page. You’ll rebuild less and trust more.