Are dashboards dead?

Guess what every HR professional is building with AI right now?

Based on what I’ve seen over the past couple of months, there’s a clear pattern emerging. Almost everyone is creating one of two things. The first is a productivity agent — something that helps them stay on top of their schedule, summarize information, or manage the day more effectively. I understand the appeal. I built one too.

The second is an attempt to finally build the “ultimate” HR dashboard.

The dream isn’t new. In fact, it’s the most consistent wish I’ve heard throughout my career. Regardless of company, geography, or level of seniority, the aspiration has always been the same: a single pane of glass – one place where all people metrics come together, neatly visualized, enabling us to spend less time extracting, cleaning, and stitching together information and more time generating insight.

Now, with access to AI agents, this aspiration feels more achievable than ever. As a result, the first things HR professionals are doing exactly what you would expect. We are all building dashboards that promise to finally solve this problem.

I’m here to tell you to stop.

Dashboards are dead.

Because while we are busy recreating the same interface with better technology, the way we consume and interact with data is fundamentally changing. Agents do not behave like humans, and more importantly, they do not need dashboards to create a unified view of information. They don’t need visual layers to interpret trends, nor do they rely on manual navigation to connect data points across systems.

So before investing more time in building yet another dashboard, it’s worth stepping back and asking a more fundamental question: why do dashboards exist?

The simplest way to unpack that is through the classic “five whys” approach.

Why #1: Why do dashboards exist?

Because our data lives in 15 places and none of them talk to each other.

Data is scattered across systems — compensation, headcount, attrition, hiring pipelines, performance ratings, engagement surveys, financials, code commits – the list is endless. No single system gives you the full picture. Dashboards exist because we needed something to stitch the fragments together into a single view.

Why #2: Why did we need a single view?

Because we needed to see data to draw insights from it.

Humans are visual interpreters. To spot patterns, correlations, and anomalies — to go from “data” to “insight” — we needed information rendered in a way our brains could process. Charts, trends, comparisons. If we couldn’t see it, we couldn’t think about it.

Why #3: Why did we need to generate insights from data?

Because generating insights was a human-dependent task. And I say ‘was’ with purpose.

Root cause analysis, pattern recognition, connecting dots across domains — these were things only humans could do. The entire pipeline from “raw data” to “so what does this mean?” required a human in the loop, interpreting, reasoning, and deciding. Dashboards were built to serve that human.

Why #4: Why was insight generation human-dependent?

Because we didn’t have alternative systems that could do it for us.

There was no technology that could query across fragmented systems, reason over the results, identify what matters, and deliver a tailored insight — all without a human having to look at a chart first. The visual layer wasn’t a preference. It was a necessity.

Until now.

Why #5: AI tells me I don’t need a 5^th so let’s move on.

Bottom line – dashboards are not the solution. They are a workaround.

Dashboards act as a human interface layer — something designed to bridge the gap between messy, disconnected systems and the decisions we need to make. They pull data together, structure it, and present it in a way that is easier for us to consume. They aggregate, they visualize, and they simplify.

But they all rely on one critical step.

A human still has to interpret what they are seeing.

And that assumption, that interpretation sits with the human, is exactly the part that is now being challenged.

Because increasingly, data is no longer something we need to go looking for. It is available at the click of a button, surfaced in context, or pushed to us when it matters. Alerts are triggered the moment predefined thresholds are crossed. Root causes can be explored conversationally, without navigating through layers of filters or drilling into multiple views.

The experience shifts from searching and interpreting to simply asking and understanding.

That transition can feel uncomfortable. Dashboards have been our primary interface with data for decades. They give us a sense of control; a feeling that we are on top of what’s happening. But in reality, they are passive tools. They wait for us to check them, interpret them, and act on them.

Agents flip that model.

Instead of waiting, systems can now nudge, recommend, and increasingly take action. Instead of showing us what is happening, they tell us what matters. Instead of requiring interpretation, they deliver conclusions.

They collapse what used to be multiple steps into a single interaction: “What should I be worried about in my organization right now?” Or even better: “Message me when I need to worry about something and tell me why.”

The model fundamentally changes.

Old model: Data → Dashboard → Human interprets → Decision
New model: Human asks → Agent queries → Agent interprets → Insight + recommendation → Decision

Dashboards start to look less like a necessity and more like a legacy interface.

They are the fax machine of data. Still around, still functional, but clearly on the wrong side of history. I guarantee that a few years from now, we’ll look back and ask: “Remember when we used dashboards to understand what was happening, instead of just asking?”

The organizations that recognize this early won’t invest in better dashboards. They’ll invest in better data foundations — structured, connected, and accessible — so that agents can do what dashboards never could.