While this is good in the sense that 99% of dashboards are worthless drek and anything that helps that is good, the examples given here are surprisingly poor. Even a cursory reading of the book they themselves recommend (Stephen Few's "Information Dashboard Design") would know this.
In fact, it appears the author may not have even read Few's book because they fail to mention some fundamental points about dashboard design that need to be understood if the design isn't going to just be a form of simple data analysis tool.
Overall, if you're interested in dashboard design, I'd give this course a miss and just read Stephen Few's book on the subject.
"being able to slice-and-dice is quite important for a dashboard. There's so many angles from which the data can be looked at"
You make the fundamental mistake of confusing a dashboard with an analytics tool. The former must function without interaction because it must deliver its value without the user working for it. The minute they have to "slice and dice" to get an answer then it's not a dashboard. Dashboards exist (as their name implies) to be glanced at in order to establish whether any action should be taken.
4 comments
[ 0.36 ms ] story [ 18.0 ms ] threadIn fact, it appears the author may not have even read Few's book because they fail to mention some fundamental points about dashboard design that need to be understood if the design isn't going to just be a form of simple data analysis tool.
Overall, if you're interested in dashboard design, I'd give this course a miss and just read Stephen Few's book on the subject.
You make the fundamental mistake of confusing a dashboard with an analytics tool. The former must function without interaction because it must deliver its value without the user working for it. The minute they have to "slice and dice" to get an answer then it's not a dashboard. Dashboards exist (as their name implies) to be glanced at in order to establish whether any action should be taken.
https://www.data-to-viz.com/