There is a particular silence in a meeting when a number on the screen is wrong and everyone in the room knows it. After that moment the dashboard is finished, not because it is broken, but because nobody believes it anymore. Rebuilding that trust is far slower than building the report was.
Trust fails for boring reasons
It is rarely the maths. It is a definition nobody agreed, where complete means one thing to the contractor and another to finance. It is a refresh that silently failed on Friday. It is a filter that drops rows the audience expected to see. The numbers are not lying; they are answering a different question than the one being asked.
Agree the definitions in public
The single highest-return habit is writing definitions down where the audience can see them. What counts as an open repair? When does the clock start? Which status codes are included? When the definition is visible on the report, a disagreement becomes a conversation about the rule, not about whether the data can be trusted at all.
A dashboard does not earn trust by being clever. It earns it by being legible: the same number, defined the same way, every single time someone looks.
Make failure visible
Trustworthy reports show their own health: a last-refreshed timestamp, a row count against the source, a flag when a feed is stale. Hiding a failed refresh to avoid an awkward conversation is how you trade one bad meeting for a permanent loss of credibility.
Trust is not a feature you ship. It is a reputation the reporting earns, one honest number at a time.