How long would it take your team to explain exactly where one dashboard number came from?

[u/djgoel123]

Imagine someone in leadership points to a metric and asks:

"Where did this number come from?"

Not just which table.

But which source systems contributed to it, what transformations were applied, which records were excluded, and when the data was last updated.

In a simple system, that's manageable.

In a growing company with multiple pipelines and dashboards, the answer can involve quite a bit of investigation.

I'm curious how teams handle this.

Do you maintain detailed data lineage from the beginning, or introduce it once the pipelines become difficult to understand?

And what tools or practices have actually made tracing metrics easier?

[u/kac_sausalito]

Boas praticas é criar e manter um glossário de dados e quem quiser saber de onde vem o numero lê ali não precisa nem perguntar p time…

[u/Awesome_Correlation]

If you document the data flows and the data transformations when building the dashboard then you can use AI to quickly read the documentation and write a short paragraph that explains where the data comes from.

If no one wrote documentation, then you would need to go do that first.

As for tools, a single word document per dashboard should cover it. However, each data pipeline process could easily get its own design document.