How often do our managers ask questions that are not already answered by an existing dashboard?

Dashboards answer the questions you anticipated. NLQ answers the questions you did not. If managers regularly ask questions their dashboards do not cover, you have a follow-up question problem that NLQ solves.

When a dashboard shows an anomaly, how does someone currently investigate the root cause?

The investigation step — drilling from 'revenue is down' to 'why' — is where dashboards end and NLQ begins. Without NLQ, investigation means asking an analyst to build another report and waiting for it.

Would our teams benefit more from better static dashboards or from the ability to ask ad-hoc questions of live data?

Most organizations need both: dashboards for metrics you monitor daily, and NLQ for the follow-up questions those metrics provoke. They are complementary, not competing.

Data & Analytics Intelligence

Dashboard vs NLQ distinction

By Mark Ziler · Last updated 2026-04-05

The difference between a dashboard and NLQ: a dashboard answers the questions someone anticipated. NLQ answers the question you just thought of. A dashboard shows you last month revenue by location because someone designed that view. NLQ lets you ask "show me revenue by location but only for new customers acquired after the acquisition" — a question nobody predicted but the data can answer. Dashboards are the starting point. NLQ is what makes the data truly accessible, because real operational questions are never the ones someone pre-built a chart for.

Go deeper

Your COO opens the dashboard every Monday and sees the same eight charts: revenue by location, utilization by provider, no-show rate, denial rate, overtime hours, open positions, days to fill, and patient satisfaction. These are the vital signs — they tell you if something needs attention. But the moment she notices overtime spiking at two locations, the dashboard cannot tell her why. Was it a staffing gap? A seasonal surge? A scheduling error? That is where she switches to NLQ and asks the follow-up question the dashboard was never designed to answer.

The trap most companies fall into is thinking they need to choose between dashboards and NLQ, or that NLQ will replace dashboards. They serve different cognitive modes. Dashboards are for pattern recognition — scanning familiar metrics for anomalies. NLQ is for investigation — digging into the anomaly once you spot it. Building only dashboards means your team spots problems but cannot investigate them without analyst help. Building only NLQ means nobody has a consistent view of operational health. You need both, and the handoff between them should be seamless.

Questions to ask

When someone spots an anomaly on our dashboard today, what is their process for investigating it?
How many of our current dashboard views were built to answer a one-time question and never updated?
If we added NLQ alongside our dashboards, which three operational questions would get asked most?