# How would you design a "Statistics" index page for the backend?

**URL:** <https://meta.discourse.org/t/how-would-you-design-a-statistics-index-page-for-the-backend/47016>\
**Category:** UX\
**Created:** [July 8, 2016, 9:19pm UTC](https://meta.discourse.org/t/how-would-you-design-a-statistics-index-page-for-the-backend/47016 "2016-07-08T21:19:08Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![commonpawn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/commonpawn/32/50792_2.png) [@commonpawn](https://meta.discourse.org/u/commonpawn)\
**Post date:** [July 11, 2016, 4:11pm UTC](https://meta.discourse.org/t/how-would-you-design-a-statistics-index-page-for-the-backend/47016/2 "2016-07-11T16:11:14Z")

</div>

Like you’re saying, it really comes down to what data has to be displayed and what you’re trying to achieve with this dashboard. I think that would be a great place to start

In terms of dashboards in general, there is also room for improvement. A lot of the critique of dashboards as we know them, is based on the fact that they simply display data - not insights. Eg. Fitbit tells you how much you move but does not really tell you how to improve your fitness - you will have to figure that out yourself from reading the data.

What if discourse could have a smarter, dynamic dashboard that not only displays a lot of useful data, but serves you relevant insights on how to improve your community

---

_[View the full topic](https://meta.discourse.org/t/how-would-you-design-a-statistics-index-page-for-the-backend/47016)._