Anonymised strategic case study
Making complexity feel effortless
A technology business had developed a powerful data platform used to understand performance, identify risk and support better decision-making. The capability behind the product was sophisticated, but the experience of using it had become increasingly complex. The opportunity was to redesign the platform around the people making decisions with the data, making valuable information clearer, faster to interpret and easier to act upon.
Opportunity
Opportunity
The platform had grown significantly as new datasets, features and reporting requirements were introduced. That growth had increased its capability, but it had also created an experience shaped increasingly by the structure of the technology rather than the needs of the people using it. Dashboards contained large volumes of information, terminology varied between different parts of the product and important insights could become lost amongst less significant data. Experienced users had learnt how to navigate that complexity, but the learning curve for new users was considerable. The brief was initially focused on improving the interface, but redesigning screens alone would have addressed the symptom rather than the underlying problem. The more valuable opportunity was to understand what users were trying to achieve, which information genuinely influenced their decisions and how the product could progressively reveal complexity rather than presenting everything at once. The project therefore became as much about information and product strategy as visual design.
Approach
Approach
The work began by understanding the decisions people needed to make with the product. User journeys, existing workflows and key tasks were mapped alongside the underlying data to identify where complexity was necessary and where it had simply accumulated over time. Particular attention was given to hierarchy: what someone needed to understand immediately, what required further investigation and what should remain available without competing for attention. Those principles informed a new experience architecture and visual language for the platform. Navigation was simplified, related information was brought together and recurring patterns were established for filtering, comparison and exploration. Data visualisation was treated as a communication discipline rather than decoration, choosing the clearest representation for the question being answered instead of filling dashboards with charts simply because the data existed. The aim throughout was not to reduce the sophistication of the product, but to make that sophistication easier to use.
Experience
Experience
A redesigned dashboard established a clearer starting point, surfacing the information most relevant to each user's responsibilities and providing obvious routes into deeper analysis. Complex datasets could be explored progressively, moving from an overall picture into individual segments, trends and records without losing context. Tables, charts, alerts and supporting information followed consistent interaction patterns, reducing the amount users needed to relearn as they moved through the platform. The work also extended beyond individual screens. A design system was created to establish reusable components, interaction behaviours, visualisation principles and accessibility standards across the product. This gave product and engineering teams a shared language for developing new features while reducing the inconsistencies that had accumulated previously. Brand and product were considered together too, ensuring the platform felt like a distinctive expression of the company rather than a functional tool sitting separately from it.
Outcome
Outcome
The project established a clearer product experience around an inherently complex service. Information became easier to navigate and interpret, while the underlying depth remained available to experienced users who needed it. More importantly, the work created a framework for deciding how future functionality should be introduced, helping the product grow without simply adding another layer of complexity each time. The design system provided a stronger foundation for product and engineering teams, while the new experience principles shifted conversations away from individual screens towards the decisions users were trying to make. That change in perspective was fundamental. The value of a data product is not measured by how much information it can display, but by how effectively it helps someone understand what matters and decide what to do next. Complexity can be valuable. Using it shouldn't feel complicated.
Private enquiry