What constitutes a good dashboard?


Dashboards are the 1st screen to welcome users for the 1st time or everytime they use your web app. What are examples of web apps with good dashboard? What do you want in a dashboard? Do you guys have general tips in designing one?

Metrics User Interface Design

asked Jan 16 '10 at 20:52
352 points

6 Answers


Good question.

I've logged into a few new web apps recently, and have experienced that 'what do I do now?' feeling on the first use.

For that reason, I'm putting a lot of effort into merging my sign up workflow and user experience into the first few uses of my app, keeping them on board and walking them through the app, hopefully motivating my users to put the effort into learning the application.

A few concrete I'm ideas I'm using on my home screen.

1) The ability to easily seed the database with sample data and then drop that data when they are ready to start entering their own.
2) Integrated tutorials that walk them through the use of the software within the context of their own user account.
3) Integrated help files accessible right in the app, not hidden away on the public site.
4) Optional detailed tooltips which they can turn off once they become proficient with the app.
5) Subtle marketing messages to keep the user excited and interested.

Dashboards for the proficient user are probably a different question. (Maybe users wouldn't want to be bothered with the above, and would appreciate a traditional management information overview style of dashboard.) I haven't decided how yet, but I want to move from one style of dashboard to the other as the user moves from beginner to advanced, helping move from new user to expert.

answered Jan 16 '10 at 22:12
Benjamin Wootton
1,667 points
  • a few counters to get to the perfect answers. :) 1. Are you talking of something like what Wordpress does? sample data on a new user's dashboard might be intrusive or might disturb the newness 'smell' of his account. 2. tutorials for a dashboard defeats the purpose of designing your dashboard intuitively. if its intuitive enough it shouldnt need an explicit tutorial 3. i agree, the help, faq, and support links should be visible within dashboard 4. agreed we are using this for our web app 5. company blog updates should be subtle enough. just title and no teasers. – Eric 14 years ago
  • My answer was more from the perspective of the 'blank slate' described below, e.g. the first time they log into the application after signing up for my free trial. I want the first screen they see to continue where my public website left off, continuing to make the product clearer and continuing the sales process, rather than leaving the person thinking 'what do I do now?' For brand new users, I want this to be a launch pad into learning more about your app. – Benjamin Wootton 14 years ago


There is also a relevant post by 37 Signals on this topic:

http://gettingreal.37signals.com/ch09_The_Blank_Slate.php For the design of traditional management information BI dashboards, I can't recommend this book highly enough:


answered Jan 16 '10 at 22:14
Benjamin Wootton
1,667 points


Check dashboardspy blog. Author collected impressive number of dashboards from very different software systems.

Browse through dashboards and you'll probably find some that you like.

answered Jan 28 '10 at 13:34
171 points


The most important thing for any dashboard is the ability to select exactly which gadgets and what type of information to be on the dashboard, instead of several preselected graphs and tables, which in most cases are only slightly relevant to the information that I'm really interested in. It would be really nice if there is an option to change the way in which the data is presented, i.e whether some chart is pie chart or bar chart, etc.

Unfortunately, most of the dashboard that I saw do not have such flexibility.

answered Jan 16 '10 at 22:19
Krasimir Evtimov
150 points
  • i agree, we are building a dashboard with a user selectable widget system. hope that would suffice. – Eric 14 years ago


Tips for brand new clients in a very non-technical market One thing that I've been doing very successfully is creating STEP 1, STEP 2, STEP 3, etc. They are the ONLY things that a brand new client can do. If he tries to go to a menu item like "Reports", he gets redirected to "Before you can view reports, you have to set up X".

For example, I have a product for churches that allows church members to set up automatic tithes. Before a church can do anything in the system, they have to create at least one offering, enter in Authorize.net details, enter billing details, etc. Once a step has been completed, it changes colors and instead of "set up now" it says "done". When all steps are complete, the client never sees these again...ever.

After system has been set up completely, they see basic reports, recent tithes, etc.

answered Jan 27 '10 at 11:13
21 points
  • tumblr does this. and the growth they are having could be a good indicator that its effective. – Eric 14 years ago


I've been thinking a lot (and trying to implement) incremental UI. When someone creates an account, give them one big option "Start here" or "Upload your first file here" (and a few others like account, sign out). Then once they've done that, show them the second action, "Great, now share it with friends...". Don't show them again once they've done it.

answered Jan 27 '10 at 02:27
Corey Maass
201 points

Your Answer

  • Bold
  • Italic
  • • Bullets
  • 1. Numbers
  • Quote
Not the answer you're looking for? Ask your own question or browse other questions in these topics:

Metrics User Interface Design