Overview
In this episode of The Dashboard Effect, Brick Thompson and Landon Oaks unpack a paradox that anyone who has built or used business dashboards will recognize: the most effective dashboards look simple, but they are anything but. The cleaner the visual, the more engineering, data modeling, and business logic is typically working behind the scenes to make it possible.
The conversation challenges a common misconception that a dashboard cluttered with charts and controls signals sophistication. Brick and Landon argue the opposite. Complexity on the surface is usually a sign that the work is unfinished. True dashboard maturity is measured by how easy it is for a business user to open it, understand it, and make a decision.
What This Episode Covers
Simplicity Drives ROI (0:47 – 1:27)
Dashboards that are intuitive and easy to interpret allow business users to make quick, informed decisions. When a dashboard is too complex to navigate, it goes unused, and an unused dashboard delivers no value regardless of how much effort went into building it.
Behind the Scenes Complexity (1:27 – 3:57)
Clean visuals require significant work underneath: data modeling, business rule validation, and careful engineering to ensure accuracy and reusability across the organization. The simplicity users experience is the product of that hidden effort, not the absence of it.
Salesperson ROI Reporting (2:06 – 3:57)
Tracking salesperson performance over 36 months sounds straightforward until you account for factors like inherited accounts from previous employees. Accurate reporting requires deep data modeling to ensure credit is assigned correctly and comparisons hold up over time.
Point-in-Time AR Reporting (4:07 – 6:03)
Reconstructing historical accounts receivable data is significantly more difficult than taking a snapshot. To account for corrections, invoices, and payments accurately, the data must be rebuilt over time rather than simply captured at a single moment.
Price-Volume-Mix Analysis (6:45 – 8:38)
Often displayed as a clean waterfall chart, the underlying calculations for price-volume-mix analysis vary considerably by company. Getting it right requires custom coding to ensure the analysis accurately reflects the specific realities of the business rather than a generic formula.
What Complexity on the Surface Actually Signals (9:21 – 9:51)
Brick and Landon close with a useful heuristic: if a dashboard looks cluttered or overwhelming, it is usually a sign that the tool is unfinished or untested. A truly effective dashboard is a reliable, simple instrument for day-to-day decision-making, and it earns that simplicity through the work done before it ever reaches a user.
Who It’s For
This episode is worth your time if you are a business intelligence or data team evaluating why your dashboards are not getting adopted, a leader or operator who has received a dashboard that felt too complicated to use, an analyst or engineer who wants language to help stakeholders understand why good dashboard work takes time, or anyone involved in a data project where simplicity and usability are the stated goals.
Why It’s Worth a Listen
Brick and Landon do something useful here: they give language to a frustration that many data teams feel but struggle to articulate. Building something that looks simple is hard, and this episode makes that case concretely through real examples that practitioners will immediately recognize.
The three examples, salesperson ROI, point-in-time AR, and price-volume-mix, are not edge cases. They are common reporting requirements that surface in nearly every data engagement. Hearing how much modeling and validation sits beneath each one reframes what good dashboard work actually involves and why it takes the time it does.
For anyone trying to set expectations with stakeholders, align on what done looks like, or simply make the case for investing in data infrastructure, this episode offers clear, credible talking points grounded in real project experience.
