Recently I noticed that internet (thanks to big data waves and to easy to use Data Visualization tools) is polluted with a lot of useless Dashboards and I spoke with Marc about this topic. Turned out he has a a very good explanation for it and he was kind enough to share his opinion on this blog as a guest blogger. Marc's post reminded me the old story:
"An admirer asked Michelangelo how he sculpted the famous statue of David that now sits in the Academia Gallery in Florence. How did he craft this masterpiece of form and beauty? Michelangelo’s offered this strikingly simple description: He first fixed his attention on the slab of raw marble. He studied it and then “chipped away all that wasn’t David.”
Dashboards – why are so many useless?
Marc Gedansky, http://marc1717.blogspot.com/
“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.” - Antoine de Saint-Exupery
Most dashboards are designed with no clue as to the meaning and/or importance of this quote.
(BTW, even though this is a blog about data visualization, I (M.G.) won’t show any poorly designed dashboard examples, as they are ubiquitous. Trying to find them is about as difficult as trying to find leaves
on the ground in New England during the Fall).
I view dashboards every day; on software company sites, news sites, financial sites, and blogs. Since dashboards can distill so much information and display it in such a small space, they hold the potential of quickly delivering valuable insights; of cutting through the “data clutter” to immediately reveal important trends or truths.
So why then, are most dashboards crammed with so many charts, dials, and graphs that they overwhelm you? Just because you can fit a half-dozen on a screen, why is there a need to do it? (This approach reminds me of my friend Geoff, who, upon hearing that Hellmann’s was coming out with mayonnaise that had half the calories remarked, “great, now I can eat twice as much”.)
I think there can only be two reasons.
1. The designer/developer wants to show off their expertise with Qlikview, or Spotfire, or Tableau, or X product.
2. The designer/developer does not care about the average person, and wants to build smart software for brilliant users.
That attitude reminds me of a meeting I attended at a software company a few years ago. The head of development was upset because he was being asked to make his software “easy to use”. He called it “dumbing down”, and complained that it would be less challenging for his development team to build “software for idiots”. At this point, the President of the company interjected, “if our customers are smart enough to write us a check, then they are smart enough to use our software. And the onus for them to be able to use our software is on us, not on them.”
For Continuation of this post please see it on this blog's page: http://apandre.wordpress.com/dataviews/dashboard/proliferation-of-useless-dashboards/