Designing Dashboard Layouts 15 Tips & Tricks

Here is a helpful guide to go through when designing dashboards (before and after). These tip should help your dashboard design by improving the layout, functionality, and usability.

1) Avoid scrolling and/or multiple pages for a single dashboard. Anything more than 1 page is considered a report. The graphs and numbers should always be together, allowing the user to do quick analysis.

2) Choose the correct visualization. Take advantage of visualizations and graphs that allow the user to quickly associate patterns.

a. Example 1: Avoid most gauges, what might work for a car’s dashboard won’t necessary work in a business. They take up space and say very little.

b. Example 2: Pie charts with more than 4-6 items can make it hard to compare sizes of the slices.

c. Example 3: Using text instead of a line chart; can give a better understanding of where the data is going.


d. Example 4: Using a bar chart to try and draw comparisons when numbers would be more forward.


3) Consider flow and transitions. Incorporate links to details and/or filtering, and try to let the eyes rest on the data and graph without unnecessary jumping around.

a. Example: Placing values in the legend but not on the graph, this would cause the user to switch their views constantly when trying to do comparisons.

4) Avoid textual overload, try to keep it visual. Dashboards are meant to be fast and easy to read.

5) Don’t do complex patterns; simple patterns allow the brain to recognize values more quickly. Sort the data to give direction.



6) Group similar characteristics, making them perceived as a group.



7) Use the correct grouping. Differing grouping options can convey different messages.

a. Example: If the objective is to view how each region is comparing to each other. Try grouping on the region instead of the quarter.



8) Covert complex data into simple logical stories. Arrange items to give a flow of communication with data laid out logically. Are the items in the data distinguishable or can they be removed or combined. Is the macro point being made clearly? Use spacing and subtle borders to create distinctions between groups and add comparative measures, like percentages to communicate differences.

9) Communicate and drive action, don’t try to use every available feature or show off your skills if it is not necessary.

10) Show focus, if the dashboard was designed for a specific reason, then try highlighting that item.


11) Show insight, don’t show metrics by themselves; this will end up leaving the interpretation to the user. Give insight by showing metrics with benchmarks, goals, and prior performance to give context. Give hits & misses, root causes, reference lines, goals, etc.

12) Don’t clutter, always give enough whitespace, and never add background logos, stock photographs, large company logos, or too many links to the dashboard.

13) Make it interactive. Users have their own questions and area of expertise. Allowing the user to filter the view, drill down, and examine underlying data will give them confidence and focus in the area they need most.

14) Stick with the basic everyday graphs, and avoid the cute uncommonly seen graphs. Visualizations like bar graphs, line graphs, heat maps, and scatterplots are popular, because they are easy to read.

15) Keep the write-ups short, sweet and simple avoid dryness. Try to avoid technical jargon, if it makes it less understandable.


By |July 1st, 2014|Categories: Visualizations|Tags: |

12 Avoidances in the initial dashboard design phase

There are many milestones through the lifecycle of a dashboards. The initial stages are the most important, in preventing headaches or failure. This list will hopefully give some guidance to start the ball rolling on a correct path to success.

1)      Avoid waiting for technology waiting for traditional BI projects to begin could take months or even years with delays. Find what technology you have available and start working on some implementations. Once you have started some ground work, the design can easily be applied to other BI technologies with little adjustments needed.

2)      Avoid underestimating time and resources – Though a dashboard is designed to be typically compact, it does not mean it will be quick and easy to create and maintain. Expect it to be an on-going, frequently changing process.

3)      Avoid static/stale data Having data automatically and frequently updateable is very important to the user and designer.  Static or stale data will lead to a false sense of confidence.

4)      Avoid limited access Making dashboards easily accessible is ideal. Making it easy for the user to access the dashboard will allow for more frequent uses and feedback; helping keep the dashboard current and useful. For example, distributing dashboards on the web can help keep data current and still adhere to IT protocols and security standards.

5)      Avoid choosing the wrong metrics Find the metrics that will end up answering the underlying questions.

  1. How does each metric contribute to the objectives?
  2. Is there data that can shed light on the objective?
  3. Is there a meaningful metric that measures those contributions?
  4. Are the metrics, chosen, necessary to contribute to the objective?
  5. Is the metric a continuous organized measurement?

6)      Avoid not knowing the goals and objectives of the dashboard. Some examples of the most common goals found in companies can be generalize as:

  1. Make better-informed business decisions.
  2. Improve customer interaction and satisfaction.
  3. Gain an overall competitive advantage.

The goal(s) usually can be seen having these characteristics at its core:

  1. Objective-focused
  2. Visual
  3. Relevant
  4. Current
  5. Accessible to its audience

7)      Avoid meaningless variety When starting, keep it simple and aim at 3-5 metrics. Never go above 10 metrics. Too many metrics will likely cause added charts and graphs that add no value to the dashboard.

8)      Avoid ignoring the target audience give the audience what they need (e.g. timely summaries, links to supporting details, what actions are applicable, etc..) The usual types of audiences can basically be broken down into 3 categories.

  1. Strategic (Executives) these users want a summary of the overall health, long term progress and goals, historical data.
  2. Operational (Department Heads) these users need a snapshot of the current operation, clear meaning, real time data, interaction and link to information.
  3. Analytic (Engineers, Programmers, Researchers, Lawyers, Paralegals, etc¦) these users need ways to do comparisons, review historical data, evaluate performance, drill into causes, needs feedback, established goals to course-correct.

9)      Avoid using metrics no one understands it is wise to avoid any unnecessary teaching of some new metric. Stick to the common and familiar metrics that the audience will know of and understand.

10)   Avoid using compound metrics Compound metrics are usually developed by using a formula comprised of a variety of measurements to come up with a single value. (Example: FICO, Klout, etc¦) The problem is that compound metrics masks insight and understanding making it hard to compare and contrast the real underlying numbers.

11)   Avoid blindly following easy measurements Easy measurements are great, but can cause users to lose sight of the bigger, more important picture. For example, SAT scores may be a great measurement of what a student’s potential will be at a college, it can also cause a blind spot on the whole life of the student.

12)   Avoid complexity Keep it simple. Focus on trends rather than point-in-time comparisons. Keep focus on the handful of metrics and design principles throughout the dashboard(s). Reduce, minimize, or eliminate non-data elements. Try reducing emphasis by changing the size, color, and borders; meanwhile, removing data that does not add insight. Draw attention and maximize the important data element.

Some helpful resources:


By |January 28th, 2014|Categories: Visualizations|Tags: , , |