Why BI teams get treated as report-monkeys
BI people often complain that business teams see them as “dashboard monkeys”. But if we’re completely honest, BI teams sometimes create this perception themselves.
Expample 1: Stakeholder: “Can you send me campaign performance data?” BI: sends CSV export.
WOW!
Now the stakeholder has: another spreadsheet, another version of the metric, another manually built report.
Two weeks later everybody asks why numbers don’t match across dashboards. Well, because nobody stopped to ask: “What are you actually trying to decide?”
Example 2: Business: “We need to understand why retention dropped.” BI: starts explaining joins, dbt models, refresh logic, attribution definitions, filter behavior.
But nobody answers the real business question.
A lot of BI communication is technically accurate - but its the accuracy that hides analyst from business problem.
Example 3: Stakeholder: “Can we visualize how revenue changed from last quarter?”
BI: “Technically Power BI/Tableau doesn’t support this natively…”
What could actually work:
Option 1: stacked bar with a running total column - builds in 20 minutes, works for most stakeholders, no custom visuals needed
Option 2: custom visual from AppSource - looks exactly like a waterfall, takes a couple of hours, harder to maintain when the data model changes
That's the answer. Two options, tradeoffs stated, stakeholder picks. The "not supported natively" part is irrelevant to them.
Posted May 12, 2026, 11:28 AM UTC