Member-only story
Dashboards are a powerful tool that you probably shouldn’t try to make
How to avoid turning your visualization into a data graveyard
My worst data visualization work has all been dashboards, and I recently realized why.
Part of learning Data Viz is experimenting with different types of visualizations to present information, and dashboards are something I’ve been looking into as I’ve started working with more complex datasets.
It’s a standard visual format that a lot of people have come to expect, but there are several catastrophic mistakes you can fall into when creating one.
To elaborate on this, one needs to look no further than Jared Spool.

Dashboards can easily become a data graveyard
“Dashboards are where data goes to die.” — Michael Solomon, Product Strategy Director

Jared Spool, the founder of User Interface Engineering, tweeted out something last year that sparked a fair amount of discussion about dashboards.