Data visualisation sits at the intersection of two professional disciplines that rarely talk to one another: data science and user experience design. Despite unprecedented access to enterprise data and modern business intelligence tools, many organizational dashboards remain technically correct yet communicatively inert. They display the right numbers, but they routinely fail to spark a meaningful decision, point toward a clear strategic direction, or change leadership thinking in weekly standups and quarterly reviews.
In modern organizations, performance decks and operational dashboards exist for almost every corporate function, spanning sales, product development, marketing, and operations. Yet, a familiar routine plays out constantly across corporate boardrooms: an analyst shares the metrics, the room nods in passive agreement, and the meeting adjourns without a single definitive choice or actionable direction. When this disconnect happens, the data itself almost always takes the blame. Teams claim the numbers lacked granularity, the underlying dataset was incomplete, or leadership simply requires more information before taking action.
The reality, however, is that the data is rarely the underlying problem. Instead, nobody designed the presentation to deliver actionable insights in the first place. Charts are frequently built from whatever metrics happen to be readily available rather than from the specific business questions that urgently need answering. Audiences are assumed rather than thoroughly understood, and the fundamental question of what should actually change as a result of viewing the data is often never asked at all. Meriem Benhabiles explores what shifts when organizations bring structured UX thinking to dashboards and data presentations, transforming them from passive records into functional decision-making engines.
The Chart Was Never the Whole Story
Data visualisation and user experience principles are ultimately solving the exact same underlying problem: both disciplines attempt to move the right information to the right person in a way that changes behavior or perspective. While their vocabularies differ, the core challenge is identical. The moment organizations begin treating them as complementary disciplines, dashboards stop functioning as passive collections of isolated charts and start driving practical outcomes.
This dynamic was brilliantly illustrated as early as 1973, when statistician Francis Anscombe published a paper that made a quiet yet profound point. Anscombe constructed four distinct datasets that were statistically identical: they shared the exact same mean, variance, correlation coefficient, and regression line. Run the mathematical numbers on any of them, and they yield identical results. However, when plotted on a graph, those four datasets could not possibly be more different.
Anscombe’s lesson to statisticians was fundamentally diagnostic: visual visualisation reveals the operational truth that raw numbers frequently conceal. But visualisation is not merely diagnostic; it is also profoundly communicative. The visual form an analyst chooses dictates whether genuine understanding emerges or gets completely lost in the noise. When audiences walk away from a presentation, do they merely remember raw numbers, or do they absorb a compelling story they will quote and discuss long after the meeting ends?
A striking modern example of communicative data visualisation is Visual Capitalist’s History of Pandemics timeline. Rather than burying the reader inside a massive data table filled with raw casualty counts, the project maps the death tolls of major historical pandemics using a proportional bubble layout across a single timeline. Before the human brain even processes a single numerical label, the visual system instantly grasps the staggering scale of the Black Death relative to every other historical event on the page. The right visualisation does not simply plot data points; it makes the underlying story impossible to miss.
Pioneering information designer Edward Tufte codified a foundational principle for the craft with his famous data-ink ratio, arguing that every single mark on a chart should serve the data rather than decorate it. While Tufte’s framework remains widely used and anchored in the pursuit of visual clarity and hygiene, it applies best to a chart viewed in strict isolation. In the real world, a chart is never read in isolation. It is consumed by a human being operating within a specific context and under distinct professional pressures. Strip a chart down to its absolute simplest form, and a designer might inadvertently strip away the precise layer of contextual nuance a decision-maker desperately requires. Simplicity is not the ultimate goal in itself; appropriate complexity is. Data is fundamentally a message, and the right amount of signal depends entirely on who is receiving it.
The Critical Phase That Happens Before the Chart
The high-leverage work that determines whether a dashboard succeeds almost never happens on a screen. It happens upstream, long before any software tool is opened, before a dataset is pulled, and before a single design choice is finalized. This preparatory work boils down to three fundamental questions: understanding the context, defining the audience, and clarifying the desired insight.
Most data-heavy projects unfortunately start backward. Product and analytics teams pull whatever metrics their internal software tools happen to track automatically and build visualisations around them, while the actual question the data was supposed to answer is merely assumed or ignored entirely. This occurs because teams naturally anchor on the readily available data as the absolute boundary of what is possible.
Defining a goal first sounds obvious, but in practice, it rarely happens with the necessary clarity. Asking a team to show product performance is not a clear goal; identifying which specific features drive retention among users who signed up during a specific quarter is a true goal because it incorporates a metric, a specific population, and an implied operational action. That exact specificity converts an open-ended exploration into a constrained, answerable design problem.
Similarly, designing for an audience comes down to two critical dimensions: accountability and familiarity. Familiarity relates directly to data literacy. Do the intended readers read charts instinctively, or does a complex multi-layered visualisation create cognitive friction? Accountability dictates how that complexity must be presented. A chart illustrating a sudden twelve-percentage-point decline carries vastly different psychological weight for an executive whose personal performance is tied to that metric compared to an analyst who is simply reporting the numbers. Data is never processed neutrally when professional accountability is on the line.
Furthermore, information and insight are entirely different states of understanding. Information represents simply what the data shows, whereas an insight is the specific decision, shift in understanding, or operational course correction someone makes as a result of seeing it. If the intended business change is not explicitly defined before design begins, any dashboard will inevitably default to passive reporting rather than driving active organizational change. Every single visualisation implicitly suggests a next step, even if that step is simply recognizing that no operational changes are required at the moment.
Real-World Application in Enterprise Software
The practical impact of this user-centric data strategy can be seen in complex B2B software environments. During a project for an enterprise talent management platform, a massive footprint of daily user telemetry was captured, leading to an open-ended brief to present this vast archive of user activity back to enterprise team leaders and individual contributors.
Rather than simply charting every piece of available data into a confusing data graveyard, the design approach focused on architecting a practical tool for real people who needed an honest, immediate narrative about their daily workflows. The team recognized that widely tracked metrics like time spent on a product are merely proxies; they indicate presence, but they do not measure actual value gained. By integrating time-spent data alongside more meaningful signals such as competency scores, certification completion rates, and historical performance trajectories, the platform could successfully surface underutilized modules and correlate them with lagging performance.
The project also required recognizing the deep rift between frontline team leads and individual contributors. While a superficial design approach might have used identical charts with minor scale adjustments, true audience analysis revealed that these two groups required entirely distinct narrative structures. Individual contributors needed a self-directed, highly personal mirror to track their pacing, strengths, and slipping metrics. Managers, by contrast, required a macro pulse-check on team vulnerabilities and consistent skill gaps to facilitate early interventions before minor issues evolved into critical project failures.
By shifting the focus from passive reporting to active, insight-driven design, organizations can transform their data visualisations from decorative afterthoughts into vital decision-making engines. Stepping away from BI tools to focus first on the human decisions behind the screen ensures that enterprise dashboards stop serving as passive logs of the past and begin actively shaping the direction of the future.
