Stop building dashboards. Start asking questions.
Every data team I've talked to has the same problem: they spend more time building dashboards than answering questions. A stakeholder asks: "Which accounts are most at risk of churning?" The data t...

Source: DEV Community
Every data team I've talked to has the same problem: they spend more time building dashboards than answering questions. A stakeholder asks: "Which accounts are most at risk of churning?" The data team says: "We can build a dashboard for that. It'll be ready in two weeks." Two weeks later, the dashboard is live. It answers the original question. And then the stakeholder asks a slightly different question, and the cycle starts again. Why dashboards are the wrong abstraction Dashboards are answers to questions you predicted in advance. They're good for monitoring known metrics. They're terrible for exploration, ad-hoc analysis, or any question that wasn't anticipated when the dashboard was built. The world doesn't ask predictable questions. Business moves faster than dashboard backlogs. The alternative: queryable data What if instead of building a dashboard, you made your database directly queryable in natural language? Not "give everyone raw SQL access" — that's a different kind of probl