Why does data quality belong to the business, not the data team?
You hired analysts and engineers, yet bad data still reaches your dashboards. The missing owner is not technical at all.
Quality means fitness for a purpose
Wikipedia's data quality entry defines quality by factors like accuracy, completeness, consistency, reliability, and fitness for intended purpose. Data is high quality if it is fit for its intended uses in operations, decision making and planning. Notice what that definition hinges on: intended use. An engineer can test a column for nulls, but only the business knows whether the data serves the decision at hand.
People disagree about the same data
People's views on data quality can often be in disagreement, even when discussing the same set of data used for the same purpose. The same entry notes that people's views on data quality can often disagree, even for the same data used for the same purpose. When that happens, businesses may adopt recognized international standards to settle the argument. So quality disputes are not bugs in a pipeline. They are conflicts about meaning, and only the people who use the data can resolve them.
Governance and MDM already say so
Master data management is a discipline in which business and information technology collaborate to keep corporate data uniform and accurate. Wikipedia describes data governance as the capability that enables an organization to ensure high data quality. It also describes master data management as a discipline in which business and information technology collaborate to keep corporate data uniform and accurate. Neither is framed as an engineering chore. Both are organizational capabilities that pair business context with technical execution.
What this does not solve
Handing ownership to the business does not fix tooling, pipelines, or measurement. It also does not end disagreements, since the sources note those persist even with shared purpose. And if nobody in the business accepts the role, ownership falls back to whoever complains loudest. Ownership without a named owner is just blame with extra steps.
For your most important dashboard, who could say today what decision it exists to support?
When two teams disagree about whether a dataset is good, who in your business arbitrates?
Pick one critical report and write down, in one sentence, the decision it exists to support.
Sources
Recommended for you
- Data
Why does GDPR see personal data where you see none?
Your AI product's logs and inputs probably count as personal data under GDPR, because the law's definition is far broader than the everyday idea of PII.
- Data
Why do your dashboards lie while your pipelines tell the truth?
When a metric becomes a target, people optimize the number, not the reality. Your raw pipeline has no incentive to flatter you.
- Data
When should you store raw data instead of cleaning it first?
Your data choice locks in who can use it. Here is what the definitions alone tell you about warehouse versus lake.
- Data
Why does hiring one AI engineer still leave your data broken?
You hired for AI and still got outputs that contradict your dashboards. The problem is the role boundary nobody drew between data work and AI work.
Enjoyed this article?
Subscribe for new articles. No spam. Unsubscribe anytime.