In organizations today, data has never been more available. Dashboards and performance decks exist for almost every function—sales, product, marketing, operations—and the tools to build them have never been more accessible. And yet, in weekly standups and quarterly reviews, the same thing happens constantly: someone shares the numbers, the room nods, and the meeting ends without a decision or clear direction.
When that happens, the data usually takes the blame. The numbers weren’t granular enough, the dataset wasn’t complete, or the team needs more information before they can act. But the data is almost never the problem. The reality is that nobody designed it to deliver insights. The chart was built from what was available, rather than from the question that needed answering. The audience was assumed rather than understood, and what should actually change as a result of seeing this data—that critical question—was never asked at all.
Data visualisation and UX are fundamentally solving the same underlying problem: both are trying to move the right information to the right person in a way that changes something. The vocabulary is different, but the underlying challenge is identical. The moment organizations start treating them as complementary disciplines is the moment dashboards stop being a passive collection of charts and start doing something truly functional. For designers who work with data, analysts who present to non-technical audiences, and marketers who need their numbers to do more than sit in a slide, bridging this gap is no longer optional.
The Chart Was Never The Whole Story
In 1973, statistician Francis Anscombe published a paper that made a quiet but clarifying point. He constructed four datasets that are statistically identical: they share the same mean, the same variance, the same correlation coefficient, and the same regression line. Run the numbers on any of them, and they are identical. Plot them visually, however, and they could not be more different. Anscombe’s lesson to statisticians was about diagnosis: visualisation reveals the operational truth that raw numbers conceal.
Yet visualisation isn’t just diagnostic; it is also communicative. The form you choose is where understanding either emerges or gets lost in the noise. Does your audience walk away with raw numbers, or with a story they will quote and talk about?
One of the most striking examples of this communicative power is Visual Capitalist’s History of Pandemics. Instead of burying the reader in a massive data table of casualty counts, it maps the death toll of major historical pandemics using a proportional bubble layout on a single timeline. Before the human brain reads a single number, the visual system grasps the sheer scale of the Black Death relative to everything else on the page. The right visualisation does not just plot the data; it makes the story impossible to miss.
Edward Tufte codified a foundational principle for the craft with his data-ink ratio, arguing that every mark on a chart should serve the data, not decorate it. It remains a widely used framework in data visualisation, anchored in the assumption that clarity and visual hygiene are the goal. For a chart in isolation, that holds true. But a chart is never read in isolation: it is read by a person, in a specific context, under specific pressure. Strip a chart down to its cleanest form, and you might be removing the exact layer of context a decision-maker needs. Simplicity isn’t the goal in itself; appropriate complexity is.
Data is a message, and the right amount of signal depends entirely on who is receiving it. This leads to the core principle of data UX: roughly 80% of the work that determines whether a dashboard succeeds happens long before you ever draw a chart.
The 80% That Happens Before The Chart
The high-leverage 80% almost never happens on screen. It happens upstream, before a tool is opened, before a dataset is pulled, and before a single design choice is made. It comes down to three fundamental inquiries regarding context, audience, and insight, which can completely shift what developers and analysts notice, ask, and push back on at the outset of every project.
Most data-heavy projects start backward. Teams pull whatever metrics their internal analytics tools already track and build visualisations around them, while the question the data was supposed to answer either gets assumed or never gets asked. This happens simply because we anchor on the data immediately in front of us as the boundary of what is possible.
Defining a goal first sounds obvious, but in practice, it rarely happens with the necessary clarity. Simply asking for a performance overview is not a goal. A true goal includes a specific metric, a defined population, and an implied action, converting open-ended exploration into a constrained, answerable design problem. For instance, a UX team trying to fix a leaky checkout flow might be tempted to pull everything available, from clicks to scroll depth. A context-first approach, however, starts with a targeted constraint: at which step of the checkout do users drop off? Filtering out the noise allows the team to build a simple funnel chart, instantly spot a bottleneck, and understand what to redesign.
Designing for an audience comes down to two things: accountability and familiarity. Familiarity is about data literacy. Do people read charts instinctively, or does a complex visualisation create friction? Accountability dictates how that complexity must be presented. A chart showing a 12% decline carries vastly different weight for the executive responsible for that number versus the analyst simply reporting it.
Furthermore, information and insight are entirely different states. Information is what the data shows, whereas insight is the specific decision, shift in understanding, or course correction someone makes as a result of seeing it. If the intended business change isn’t defined before the design begins, a dashboard will default to passive reporting rather than driving action.
A Project Walk-through: Moving from Questions to Dashboards
These principles play out clearly in real-world implementations, such as a recent project for a client-facing B2B SaaS platform focused on enterprise talent management and competency tracking. The platform captured a massive footprint of daily telemetry, and the initial brief arrived open-ended: the organization had an immense archive of user activity and needed to present it effectively to enterprise teams.
Rather than charting everything captured and creating a data graveyard, the project shifted toward architecting a practical tool for real people who would open the dashboard routinely. The context phase required defining the mechanics of performance. While time spent on the platform is a common metric, it is merely a proxy that indicates presence rather than value. More meaningful signals included competency scores by area, certification completion rates, and historical performance trajectories. Integrating time-spent data alongside these performance metrics helped surface underutilized modules and correlate them with lagging scores.
Audience analysis revealed a deep rift between frontline team leads and individual contributors. While an individual contributor workspace needed to act as a self-directed mirror that was granular and personal, the manager’s interface had to bypass individual milestones initially to provide a macro pulse check on team vulnerabilities. It was designed around a different operational reality, prioritizing the aggregate picture first while retaining an intuitive path to drill down into tactical day-to-day coordination when needed.
For individual contributors, the core value was self-direction, ensuring they could glance at the interface and immediately derive a clear priority list. For managers, the goal was to shift the timing of operational conversations, providing a baseline to intervene before a skill gap evolved into a critical project failure.
To solve the core design problem of helping an individual user answer where their relative strengths and gaps lay across eight distinct competency areas, the team mapped the data using a radar chart. Organizing multiple variables across axes radiating from a central point using polar coordinates connected the data points to form a unified shape. While a traditional linear bar chart would have forced the viewer to scan eight individual bars and calculate variance, a concentric radial layout made progress tracking and skill gaps immediately readable.
Following the deployment of these personalized dashboards and side-by-side team comparison tools, weekly active engagement on the platform’s analytics features rose noticeably. Managers were no longer opening the tool once a month to pull static reports; they were using it proactively to plan their weeks. Churn across the platform fell to one of its lowest points on record, proving that treating visual presentation as an upstream architectural choice rather than a downstream formatting step can turn visualisations into active decision-making engines.
