The relentless pursuit of something to satisfy everyone ends up in satisfying no one
A health check not an encyclopedia
The most common reason a dashboard fails to work is simple. Too much information. It would be an impossible task to create a dashboard that answered everyone’s questions, and for that matter that shouldn’t be the goal. A dashboard's intended purpose is to give you a glimpse into the health of whatever application you are monitoring. It is a health check intended to be used to then ask deeper questions for which another layer of analytics reporting would provideLess is more
Huge dashboards with endless details that users only really focus on once, and then ignore because it contains too much detailed information are often the norm. However, dashboards should contain roll up figures focused on specific KPIs not detailed data. The figures shared should inform you quickly of high level results from which you may desire to dig deeper to understand why - for example - your session lengths are declining.




