Three versions of the truth
Ops has a live list. Finance has the ledger. Sales has the pipeline. The board asks for one number and the meeting becomes archaeology — export, VLOOKUP, which tab did Sarah send. The same pain as when the stack is heavier than the work: more tools did not create trust, they created debate.
When every dashboard tells a different story, the problem is not charts — it is which number is allowed to be true. Fix that before you add another BI login or hire an analyst to reconcile what your systems should have agreed on already.
Pick one report first
Choose the metric that drives cash, capacity, or risk this quarter — not the metric that is easiest to chart. Name the system of record for each input. If revenue is the number, the finance posted view wins unless leadership explicitly overrides it with a documented rule.
Kill duplicate fields in the CRM that re-state finance facts unless someone owns the reconciliation weekly. Pipeline value is motion; invoiced revenue is fact — the CRM and finance disagreement article covers that distinction in detail. Mixing the two in one headline guarantees distrust.
Make it boring on purpose
Fixed definitions written in plain English — booked versus billed versus collected. A fixed refresh time — 07:00 weekdays, not "whenever someone runs it". A named owner who answers when it looks wrong, not a committee. Everything else is secondary until this report survives a bad week, a leave gap, and a vendor outage.
Boring is a feature. Exciting dashboards with twelve drill-downs nobody uses are dashboards nobody opens. One trusted line on one page beats a data warehouse nobody believes.
Ritual beats software
Schedule the same fifteen minutes weekly: the owner presents the report, variances get named causes, and actions get owners. Cancel the ritual only after six months of no material corrections — not after one good month. If the meeting exists because the report is wrong, fix the report. Do not extend the meeting.
When leadership asks for a second opinion
Someone will export their own version — pipeline from the CRM, cash from the bank feed, WIP from a spreadsheet. Do not shame them. Ask which decision their number supports. Either fold a documented rule into the official report, or ban that export from board packs. Two official truths is worse than one boring truth.
Document definitions where new hires will actually find them — not in a wiki nobody opens. Link from the report footer: booked means X, refreshed at Y, owner Z. That reduces the coordination tax every month-end.
For pipeline trust specifically, minimum viable CRM covers the gap. An ROI framework helps if you need the board framing for funding the fix. And a quarterly systems check-in can catch drift before it becomes a rebuild.
At a glance
Book a review — Teesside and the North East. A process audit helps when you cannot agree which number should win.