---
title: "dashboard design | Skills We Assign For | Azendo"
description: "Dashboard design — designing for a decision, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/dashboard-design/"
---

[Skills](https://azendo.co/skills/) Analytics and BI 

# dashboard design.

Dashboard design decides what a dashboard shows, how it is arranged and what it omits, so that the people using it reach a decision faster. It is an editorial discipline as much as a visual one.

## Where dashboard design fits on a long engagement.

The most common failure is a dashboard built from what is available rather than from what someone needs to decide. Forty charts covering every dimension is an inventory, not a dashboard, and the effect is that nobody looks at it after the first week.

Starting from the decision inverts the process usefully. Who looks at this, what are they deciding, what would change their mind — those questions produce a much smaller and more useful set of charts, and they make it possible to say no to additions that do not serve the decision.

## What an assigned team does with dashboard design.

Dashboards accumulate. Every stakeholder request adds a chart, none are ever removed, and within a year the useful signal is buried among additions that served one conversation.

Periodic editing — removing what nobody uses — is part of keeping analytics useful, and it sits within an agreed [committed monthly capacity](https://azendo.co/pricing/) rather than waiting for a rebuild.

## What we use dashboard design for.

* Designed backwards from a decision Charts chosen because they change an action, not because the data exists.
* Usage measured and acted on Views tracked, so unused charts are removed rather than accumulating.
* Context that prevents misreading Comparisons and definitions shown, so a number is not interpreted wrongly.

## How dashboard design capacity is assigned.

Dashboard work sits between analytics and design capacity, and is scoped with [outsource ux design](https://azendo.co/services/ux-ui-design/) where presentation rather than data is the constraint.

## Roles we assign dashboard design for

* [Data Analyst Data science](https://azendo.co/services/data-science/data-analyst/)

## Service lines it sits in

* [Data science](https://azendo.co/services/data-science/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in analytics and bi

* [Looker — skill we assign for](https://azendo.co/skills/looker/)
* [Power BI — skill we assign for](https://azendo.co/skills/power-bi/)
* [Tableau — skill we assign for](https://azendo.co/skills/tableau/)
* [semantic layers — skill we assign for](https://azendo.co/skills/semantic-layers/)
* [A/B testing — skill we assign for](https://azendo.co/skills/a-b-testing/)
* [experimentation design — skill we assign for](https://azendo.co/skills/experimentation-design/)
* [causal inference — skill we assign for](https://azendo.co/skills/causal-inference/)
* [cohort analysis — skill we assign for](https://azendo.co/skills/cohort-analysis/)

## Tell us what your roadmap needs dashboard design for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)