Overview
In this episode of The Dashboard Effect, Brick Thompson and Landon Oaks make the case that meaningful business intelligence does not require a large budget, a dedicated data team, or an enterprise-scale technology investment. The episode is aimed at small professional services firms that know data could help them run better but are not sure where to start or whether the investment is realistic for their size.
The answer Brick and Landon offer is practical and deliberately unglamorous: start with one problem, prove the value manually before automating anything, and build from there. See how Blue Margin’s Managed Data Service gives smaller teams access to the expertise and infrastructure they need to do exactly that, without having to build it themselves.
What This Episode Covers
Start Simple (1:00 – 2:30)
Rather than attempting to build a comprehensive, enterprise-wide reporting system, the hosts recommend identifying a single meaningful problem whose solution would materially improve the business. One well-chosen metric that drives a real decision is worth more than a dashboard full of data that no one acts on.
Test with a Proof of Concept (3:40 – 4:40)
Before investing in automation or tooling, build a manual version first. A spreadsheet that gets numbers in front of decision-makers is enough to validate whether the data actually changes how people think and act. The goal at this stage is not polish. It is proof that the insight is useful.
A Real-World Example (4:15)
The hosts share a story about a firm struggling with field technician utilization. By identifying and consistently tracking a small number of key metrics, managers were able to adjust their processes and drive a one percent improvement in utilization that translated into millions of dollars in additional profit. The insight itself was simple. The impact was not.
Automate and Iterate (4:45 – 7:15)
Once a manual process has demonstrated its value, the next step is to automate it for consistency and reliability. From there, BI becomes an ongoing practice rather than a one-time project, evolving based on user feedback and changing business conditions. The firms that get the most from data treat it as a discipline, not a deliverable.
Avoid the Boil the Ocean Mentality (8:05 – 8:41)
One of the most common ways BI initiatives stall is by trying to pull in every available data point before delivering anything useful. The hosts are direct about this: success comes from focusing on the metrics that drive actionable change, not from building the most comprehensive system possible.
Who It’s For
This episode is worth your time if you are a founder or operator at a small professional services firm who suspects data could improve your margins but does not know where to begin, a manager who has tried to implement reporting before and watched it go unused, a team that has been told BI requires more resources than you have, or anyone who wants a realistic and low-overhead framework for getting started with business intelligence without overcomplicating it.
Why It’s Worth a Listen
Most data content is written for organizations that already have infrastructure, tooling, and dedicated teams in place. This episode is not. It is written for the firm where the owner is also the analyst, where Excel is still the primary reporting tool, and where the question is not which platform to choose but whether any of this is worth pursuing at all.
The proof of concept framing is particularly useful. It removes the pressure to get everything right before starting and replaces it with a more honest question: does this data change how we make decisions? If the answer is yes, you automate. If the answer is no, you have learned something valuable without spending much to find out.
For small firms that have been waiting until they are bigger or better resourced to take data seriously, this episode makes a compelling argument for why waiting is the wrong strategy.
