Overview
In this episode of The Dashboard Effect, Brick Thompson and Caleb Oaks address one of the most practical challenges in data work: making the internal case for a BI investment in terms that resonate with the people who control the budget. The conversation provides a clear and actionable framework for connecting data initiatives to business outcomes, distinguishing between metrics that are easy to quantify and those that require more work to justify, and avoiding the most common mistakes that cause BI proposals to stall before they start.
For any data professional or business leader trying to gain organizational support for a BI initiative, this episode offers the ROI framework that makes that conversation more productive. See how Blue Margin’s Managed Analytics & Insights helps organizations identify and deliver the high-ROI data initiatives that build momentum and demonstrate measurable business value quickly.
What This Episode Covers
Start Narrow (2:00 – 2:37)
The instinct to unify all data sources and solve every reporting problem simultaneously is understandable but counterproductive for building organizational support. A proposal that requires significant budget and time before delivering anything visible tends to lose momentum before it produces results. The more effective approach is to identify a single area where improved data visibility leads to better decisions and better decisions lead to measurable profit impact, and to build the business case around that specific connection rather than a comprehensive data strategy.
Quantify the Value (3:41 – 4:27)
Even a rough ROI calculation is more persuasive than a qualitative argument for better data. If a one percent improvement in machine utilization translates to a specific dollar amount, showing that math makes the investment case concrete rather than conceptual. The precision does not need to be exact. The exercise of doing the math, even with acknowledged assumptions, demonstrates that the team has thought seriously about the return and gives executive leadership a number to evaluate rather than a principle to believe in.
Easy Metrics vs. Hard Metrics (4:27 – 7:03)
Not all metrics are equally easy to connect to business outcomes. Accounts receivable and machine or workforce utilization have direct, traceable impacts on cash flow and profit that make them strong candidates for an initial ROI case. On-time delivery is vital to customer retention and revenue but requires more steps to connect to a specific dollar impact, which makes it harder to justify as a starting point unless there is a known and urgent business problem driving it. Leading with the metrics that have the clearest financial connection builds credibility for the harder-to-quantify ones that follow.
Prioritize Over a Shopping List (7:05 – 7:31)
A proposal that lists every possible report a data platform could deliver tends to dilute rather than strengthen the case. Decision-makers faced with a long list of potential outputs have no clear basis for evaluating which ones matter most, and the lack of prioritization signals that the team has not done the work of distinguishing high-value from low-value initiatives. Focusing on the two or three initiatives most likely to produce visible results quickly builds momentum that makes subsequent investments easier to justify.
Build a Business Case Explicitly (7:33 – 7:56)
BI initiatives that begin without an explicit statement of the expected outcome tend to drift toward becoming a general data improvement project with no clear measure of success. Defining the expected outcome before the work begins gives the initiative a goal to be evaluated against and prevents it from being characterized as a wasted expense when the scope expands or the timeline extends without a clear story of what was delivered.
Do Not Overthink the Precision (7:59 – 8:34)
A rough estimate based on reasonable assumptions is often sufficient to gain approval for an initiative whose value is clear. Spending significant time refining a ROI model to account for every variable before the project has started can delay the conversation and signal a lack of confidence in the core value argument. If the project is clearly worthwhile, a defensible estimate with acknowledged assumptions is a better use of preparation time than an exhaustive financial model.
Who It’s For
This episode is worth your time if you are a data analyst or BI developer trying to gain organizational support for an initiative and struggling to frame the value in terms that resonate with financial decision-makers, a data team lead or director preparing a budget proposal for BI investment and wanting a structured approach to building the ROI case, a business leader who has intuited that better data would improve performance in a specific area but has not yet done the work of quantifying what that improvement would be worth, or any organization where data initiatives have been proposed and rejected because the business case was not concrete enough to compete for budget against other priorities.
Why It’s Worth a Listen
The ROI conversation around data investments is one that data teams consistently find difficult, largely because the value of better decision-making is real but diffuse in ways that make it hard to pin to a specific dollar amount. This episode provides a framework for doing that pinning with enough rigor to be credible and enough pragmatism to be achievable without turning the business case into a research project.
The easy versus hard metrics distinction is the most practically useful part of the episode for teams trying to decide where to start. Choosing the first initiative based on where the ROI connection is most direct rather than where the data problem is most interesting or most comprehensive is a discipline that most data professionals do not apply naturally, and this episode makes the case for it clearly.
And the do not overthink the precision point is a useful permission for teams that have delayed making the case because the analysis was not complete enough. A rough but honest estimate that moves the conversation forward is more valuable than a precise model that arrives after the budget decision has already been made without data team input.
