Hugo Chappe
Work About Contact
Work & Case Studies
Case Study · Europcar Mobility Group · Data Visualisation

Internal dashboards for business teams

Internal dashboards packed with numbers nobody used. I redesigned them around the questions teams actually needed to answer — and turned them into daily operational tools.

Faster
Decision-making across business teams
Daily
Active use — from gathering dust
Fewer
Meetings needed to "read the numbers"
Role
Senior Product Designer
Context
Internal Data Tools · B2B
Deliverables
UX Research · Data Design · Iteration

Dashboards That Serve No Purpose

We've all seen those internal dashboards packed with numbers, blinking charts, colors everywhere — and ultimately, nobody really uses them. That was exactly the situation here.

  • Business teams had access to tons of data
  • But they couldn't read it or interpret it easily
  • Let alone use it to make decisions
  • Result: dashboards gathering dust, decisions made on gut feel
These dashboards were designed by people who love data, for people who want answers. That's a fundamental mismatch — and it's a UX problem.

Data UX Mode

Step 01
Understand the real needs

I started by talking to business teams. Not to ask "what do you want?" — but to understand what questions they ask themselves daily, what decisions they need to make, and how they actually use (or don't use) current dashboards. Spoiler: they didn't want more data. They wanted clear answers.

Step 02
Clarify and prioritise

I sorted through the data landscape: what are the truly key indicators? What needs to be visible first? What can live at a second level? The goal was to avoid information overload — because an overloaded dashboard is a useless dashboard. Less data, more insight.

Step 03
Design for action

I designed dashboards that don't just show numbers — they enable quick understanding (5 seconds to grasp the essential), guide toward action (if this number is red, here's what to do), and adapt to different business profiles. Data as decision support, not data for its own sake.

Step 04
Collaborate tightly with tech

Beautiful mockups are great, but if they're not technically feasible, they're worthless. I worked hand-in-hand with product and tech teams to verify visualization feasibility, understand data constraints, and find smart compromises that served users without creating impossible engineering challenges.

Step 05
Iterate with users

I didn't just ship and move on. Multiple iteration cycles with business teams, adjustments based on real feedback, and continuous improvement of relevance. Each iteration made the dashboards a little more useful — and a little more used.

One Visual Language for Data

A colour system built for data visualisation, and a kit of chart components that uses it. Every dashboard draws from the same palettes and the same building blocks.

Chart components from the design system: KPI cards, bar, line, donut and bubble charts, shown with sample data
Chart components from the design system, shown with sample data
The full colour system documentation for data visualisation: categorical, sequential, diverging and alert palettes
Colour system documentation

The One That Actually Works

The Dashboards
  • Readable at a glance
  • Adopted by business teams
  • Used daily to drive operations
  • Adapted to each profile
The Impact
  • Faster decision-making
  • Fewer meetings to "understand the numbers"
  • More team autonomy
The Recognition
  • Teams finally have tools they use
  • Requests for more dashboards using the same approach
  • Design approach replicated in other tools

Data Is Worthless If Nobody Understands It

A good dashboard answers questions, not just displays numbers
Start with the question. Then find the data that answers it. Never the other way around.
Data design is primarily about information hierarchy
What's first? What's secondary? What can you find if you look? These choices matter more than chart style.
Less is often better — especially in data viz
Every additional metric competes for attention. Be ruthless about what earns its place on screen.
The best design gets out of the way to enable action
If the user is thinking about the interface, you've already lost. They should be thinking about the insight.