Overview
In this episode of The Dashboard Effect, Brick Thompson and Caleb Oaks push back on one of the most common reasons organizations delay data initiatives: the belief that data needs to be clean before it can be reported on. The argument they make is both practical and well-grounded in how data quality problems actually get resolved in real organizations. Waiting for clean data is not a prerequisite for good reporting. It is a reason to never start.
The episode reframes bad data from a blocker into a signal, and reporting from a destination into a diagnostic tool that accelerates the path to data quality rather than depending on it. See how Blue Margin’s Managed Analytics & Insights helps organizations start reporting on the data they have today while building the foundation for the trusted, accurate insights they need tomorrow.
What This Episode Covers
Data Quality Is Subjective (1:24 – 2:45)
What counts as bad data depends entirely on the business context and what the data is being used to answer. An ERP system might store accurate revenue figures alongside incorrect cost data, producing reliable top-line reporting and unreliable item profitability at the same time. The implication is that data quality is not a binary state of the dataset as a whole. It is a relationship between the data and the specific questions being asked of it, and understanding that distinction changes how organizations approach the problem.
The Garbage In Garbage Out Fallacy (3:45 – 4:15)
The principle that bad data produces bad outputs is true but frequently misapplied as an argument for waiting. In practice, waiting to fix all data quality issues within source systems before pulling data out for reporting is both impractical and counterproductive. Extracting data and reporting on it is often the fastest way to understand the scope of the quality problem and identify precisely where processes are failing. The garbage in garbage out concern is a reason to label outputs clearly, not a reason to defer the work indefinitely.
Power BI as an Exploration and Compliance Tool (6:32 – 8:05)
Power BI is not only a tool for polished board-level reporting. It is an effective environment for data exploration that surfaces patterns, anomalies, and quality issues that are invisible inside source systems. The hosts also highlight its value as a compliance mechanism: by centralizing data and building monitoring into the reporting layer, teams can receive near real-time alerts when data entry deviates from expected formats or when process breakdowns introduce inconsistencies. That feedback loop is faster and more systematic than manual review.
Proactive Correction Through Centralization (5:50 – 6:30)
Once data is centralized in a data lake or warehouse, cleaning it becomes a programmable and scalable process rather than a manual, record-by-record effort. Centralization makes it possible to identify patterns in the errors, build automated processes to address them, and monitor for future occurrences. The same consolidation that enables better reporting also enables better data governance, and the two reinforce each other in ways that are only accessible after the data has been moved.
Shining a Light on Data Issues (9:05 – 11:03)
The hosts conclude with a framing that ties the episode together: data platforms are not just tools for reporting on clean data. They are tools for illuminating where data is broken and why. Organizations that use reporting to surface their data quality problems rather than hiding from them move faster toward accurate, reliable, and actionable insights than those that wait for a quality standard they cannot achieve without the visibility that reporting provides.
Who It’s For
This episode is worth your time if you are a data or BI team that has been told to wait for cleaner data before building reports and wants a framework for challenging that assumption constructively, a business leader who has used data quality concerns as a reason to defer a reporting initiative and wants to understand what is actually being deferred along with it, a data engineer or analyst responsible for data quality improvement who wants to understand how reporting can accelerate that work rather than compete with it, or any organization that has been stuck in a data quality improvement cycle that never quite reaches the threshold required to start building.
Why It’s Worth a Listen
The bad data paralysis pattern is closely related to the BI paralysis the hosts have discussed elsewhere, and this episode provides the specific arguments needed to break it. The reframe from reporting as a destination to reporting as a diagnostic is genuinely useful, and the hosts support it with enough concrete reasoning to make it credible in an internal conversation where the instinct to wait for perfect data is deeply ingrained.
The Power BI compliance monitoring point is one of the most underutilized capabilities the hosts describe. Most organizations think of their reporting layer as something that consumes data quality and reflect it back. The idea that it can also monitor for deviations and alert teams to process breakdowns in near real time changes what the reporting investment is capable of returning beyond its primary analytics purpose.
And the proactive correction argument is the clearest articulation of why centralization and data quality improvement are not sequential activities. They are parallel ones, and the organizations that treat them as such make progress on both faster than those that insist on completing one before starting the other.
