The laws of shitty dashboards
attackwithnumbers.com
The laws of shitty dashboards
1–10 of 126 posts
Re: The laws of shitty dashboards
#2>"Most KPIs (traffic, revenue) are too volatile on a daily basis to be useful. Yet “last 30 days daily” is more or less the default option."
YES! If you're building a dashboard, don't answer the question "what data do I have?" or "what does the brass say this should be?" But instead, get out and talk to users, find out what data is most important to them, think outside the box, throw some different ideas out there and see what sticks with users.
Re: The laws of shitty dashboards
#3>"Most KPIs (traffic, revenue) are too volatile on a daily basis to be useful. Yet “last 30 days daily” is more or less the default option." YES! If you're building a dashboard, don't answer the question "what data do I have?" or "what does the brass say this should be?" But instead, get out and talk to users, find out what data is most important to them, think outside the box, throw some different ideas out there an…
I can only agree. Especially real-time data. There are only a few cases where real-time might be usefull
Re: The laws of shitty dashboards
#4Most articles are shitty, this is an example of one.
Most technical articles are written by someone blinkered by their specific experience which they feel is so wonderful that they should share with the world.
Save the internet from such dross and write it on a piece of paper, roll it up and shove it up the ares your talking out of.
Re: The laws of shitty dashboards
#5I was hoping for an article that would explain how to design a good dashboard. This isn't it.
Re: The laws of shitty dashboards
#6>"Most KPIs (traffic, revenue) are too volatile on a daily basis to be useful. Yet “last 30 days daily” is more or less the default option." YES! If you're building a dashboard, don't answer the question "what data do I have?" or "what does the brass say this should be?" But instead, get out and talk to users, find out what data is most important to them, think outside the box, throw some different ideas out there an…
I can only agree. Especially real-time data. There are only a few cases where real-time might be usefull
If you have a site delivering real time content, such as news, its pretty important.
Re: The laws of shitty dashboards
#7>"Corollary: No one needs real-time"
If you've ever run service where you're anticipating a large traffic spike and you need to monitor server stats, real-time statistics are invaluable.
Re: The laws of shitty dashboards
#8> Yes, back-end applications need ways to show their users that they’re working
This is probably the only reason many dashboards exist. They're not there to be useful, but to provide proof that the gears are turning behind the system.
Re: The laws of shitty dashboards
#9>"Corollary: No one needs real-time" If you've ever run service where you're anticipating a large traffic spike and you need to monitor server stats, real-time statistics are invaluable.
precisely. try running a network of any appreciable throughput (10G+) with 5-minute averages.
Re: The laws of shitty dashboards
#10>"Corollary: No one needs real-time" If you've ever run service where you're anticipating a large traffic spike and you need to monitor server stats, real-time statistics are invaluable.
Or you release a new version of a game and you notice your arpdau tanks. ;)