Business teams have never had more data, more dashboards or more ways to query both. Generative AI now lets a regional sales lead type a question in plain English and get a chart back in seconds. Nevertheless, in many companies the same complaints remain. A simple operational question still sits in an analyst’s queue for days. And when the answer arrives, someone in the meeting has a different number.
That gap is the real story across all four types of business analytics, but particularly self-service. As noted in our guide to agentic BI, self-service analytics has ranked as a top organizational priority in TDWI research for more than five consecutive years, yet over 40% of organizations remain dissatisfied or uncertain about their ability to get insights from data. [JP1] The constraint is no longer data or tooling. It’s access and trust. Analytics programs succeed when metrics are defined once, governed centrally and open to anyone who can ask a question in plain language. Programs that take different approaches don’t provide the necessary access and build sufficient trust to be successful.
The data is there, so why the struggle?
The root cause for why analytics programs typically falter is twofold: people can’t get answers fast enough, and they don’t trust the answers they get. More data won’t fix either problem and in fact can usually make both worse because every newed, filtered or joined a little differently. New dashboards also trigger follow-up questions they weren’t built to answer, and those questions go to an already busy analyst team
The result is an operating model that looks mature from the outside, with a modern warehouse, a BI license and a library of dashboards. Yet when returns spike in one region, the analytics team can’t explain why until the moment to do something about it has passed.
The report queue: why teams still wait on analysts
Most analytics programs were built on a request-and-deliver model. A business user files a ticket, an analyst writes the query, builds the view and hands it back. That works for a quarterly board deck. It fails for operational questions that drive daily decisions in supply chain, store operations, marketing or customer service.
The delays are well documented. Our own research estimates that a new dashboard request can take two to three weeks to move through a traditional BI queue. As noted in our blog post aboutleading companies delivering self-service analytics, Virgin Atlantic’s commercial and finance teams used to wait weeks for analysts to assemble reports, and data specialists at the Automobile Association in the UK were overwhelmed with ad hoc requests.
The cost of that wait rarely shows up on a dashboard. It shows up as decisions made on instinct because the data came too late, and as analysts who spend their weeks on routine pulls instead of the hard questions only they can answer. When the queue shrinks, the improvement is stark. As described in the same post, Grupo Casas Bahia cut the time to answer complex logistics and sales questions from five or six hours to about two minutes, while Webmotors reduced BI support tickets by 72%.
Why business users stop trusting the numbers
Everyone loves a fast answer, but at the same time a fast answer nobody trusts is worse than a slow one. For analytics teams, trust usually erodes through metric drift. Revenue means one thing in a marketing dashboard, something slightly different in a finance report and something else again in the executive summary. Each definition is defensible on its own. Together, they turn every meeting into a debate about which number is right instead of what to do about it.
Once that happens, users protect themselves. They export to spreadsheets, rebuild calculations they control and stop opening the shared dashboards. Each workaround creates another version of the metric, which deepens the original problem.
This is where the access problem and the trust problem feed each other. The slower the official path, the more shadow versions people create. The more shadow versions exist, the less anyone believes the official path. That’s why rebuilding trust isn’t about better dashboards. It’s about the definitions underneath your dashboards.
Why AI raises the stakes for business analytics
Natural language might seem like the cure for an overloaded queue. If someone can ask a question directly and get an immediate answer, the ticket is resolved. That part is true. But AI along doesn’t solve the trust problem. It amplifies it.
A conversational interface built on inconsistent definitions will answer confidently, and differently, depending on which table it happens to query. Picture a regional operations director who asks for last month’s same-store sales growth and gets 4.2%, while finance reported 2.9% at the monthly review. Maybe the query counted stores open less than a year. Maybe it treated returns differently than finance does. We can’t tell, but an answer like that sends the director back to the analyst queue, and the self-service investment sits unused. Teams that build production-ready Genie Spaces prevent this by testing answers against questions with known results before users ever see them.
That’s why the order of operations matters. AI-assisted self-service scales whatever sits underneath it. If it’s built on governed, shared definitions, it scales trust. If it’s built on fragmented definitions, it scales confusion faster than any analyst team could.
Three commitments that shape effective business analytics
For data leaders who have already invested in analytics, the goal is no longer more dashboards. It’s building decision-making capabilities that any team can use without waiting or second-guessing the result. That takes three commitments:
1. Define metrics once. Revenue, churn, active customers and margin should each have one certified definition, expressed in standard SQL and reusable by every dashboard, notebook, AI assistant and agent. Drift usually starts when definitions live inside individual business analytics tools, so fixing that needs to happen upstream in the platform. On Databricks, Unity Catalog Business Semantics provides that consistent semantic layer, so a metric means the same thing whether it’s being used by an AI/BI Dashboard, Genie or an AI agent.
2. Govern in the platform, not in each tool. When every BI tool carries its own semantic model and its own permissions, governance fragments along with the definitions. Access controls, lineage and certification belong at the data layer, where they apply to every consumer at once. Databricks AI/BI runs directly on data governed inUnity Catalog, so a dashboard and a natural language question inherit the same rules.
3. Open access to everyone with a question. Per-seat licensing actually works against self-service because it forces leaders to decide which teams deserve answers. License counts are the wrong control point for governance. Strong policy at the data layer is what makes broad access safe. Databricks AI/BI is native to the Databricks Platform with no per-seat license fees. That provides access to every team rather than a select few, and with Genie Spaces everyone can ask questions in natural language and get answers from governed data.
Companies that get these three factors right are able to shift business analytics from “the reports the data team produces” to “the questions people can answer on their own.”
