Visual Best Practices

Visual best practices are key to developing informative visualizations that drive your audience to act. A dashboard is successful when people can easily use it to derive answers. Even a beautiful dashboard with an interesting data source could be rendered useless if your audience can’t use it to discover insights.

Think not just as an analyst but also as a designer and consumer. Dashboards should have interactive elements that are discoverable and predictable, follow a sensible, logical layout, and have a simplified design that makes complex decisions easier. It is important not to assume that people automatically know what it takes to clearly and effectively communicate with data. Here are a few whitepaper links to share on your enablement intranet:

You can find a list of books by renowned data visualization experts in the appendix. Adding these whitepapers and books to the resources of your analytics community can lead to a deeper understanding and internalization of visual best practices.


The best visualizations have a clear purpose and work for their intended audience. It’s important to know what you are trying to say and who you are saying it to. Does your audience know this subject matter extremely well or will it be new to them? What kind of cues will they need? Thinking about these questions before you begin designing will help you create a successful dashboard. For example, you would present aggregated, summary-level data and KPIs to an executive audience rather than row-level transactions.


Make sure your views include context. Titles, captions, units, and commentary all help your audience to better understand your data view. Always strive to tell stories with your data and your visuals. Understand that good stories involve more than just data, and consider the following:

  • Mind your aesthetics and know that what is effective is often affective. In other words, an effective view can create an emotional response and a genuine communication to your audience.
  • Style is also important. Make sure that your views are consistent and pleasing to the eye. Your views are representative of who you are and what you care about.
  • Dashboards that people can interact with are very engaging. Interactive elements allow your audience to manipulate the data, ask and answer questions, and arrive at findings on their own. This helps to foster trust in your data.
  • Make your views vivid and memorable. Pay attention to structure and context.

Chart Choice

Chart choice should depend on the question you are trying to answer or a specific insight you are trying to communicate. There is almost always a trade-off involved, with different chart types each having their own advantages and downsides. You should always ask yourself if your chosen chart type best conveys the message you are trying to share and if it can be easily understood by your audience. The table below explains the chart types in Tableau’s Show Me panel and when to use each. This should be published to your enablement intranet to educate new users.




Line — Viewing trends in data over time.

Examples: Stock price change over a five-year period, website page views during a month, revenue growth by quarter.

Bar — Comparing data across categories.

Examples: Volume of shirts in different sizes, website traffic by origination site, percent of spending by department.

Heat Map — Showing the relationship between two factors.

Examples: Segmentation analysis of target market, product adoption across regions, sales leads by individual rep.

Highlight Table — Providing detailed information on heat maps.

Examples: The percent of a market for different segments, sales numbers in a particular region, population of cities in different years.

Treemap — Showing hierarchical data as a proportion of a whole.

Examples: Storage usage across computer machines, managing the number and priority of technical support cases, comparing fiscal budgets between years.

Gantt — Showing duration over time.

Examples: Project timeline, duration of a machine’s use, availability of players on a team.

Bullet — Evaluating performance of a metric against a goal.

Examples: Sales quota assessment, actual spending vs. budget, performance spectrum (great/good/poor).

Scatterplot — Investigating the relationship between different variables.

Examples: Male versus female likelihood of having lung cancer at different ages, technology early adopters’ and laggards’ purchase patterns of smart phones, shipping costs of different product categories to different regions.









Histogram — Understanding the distribution of your data.

Examples: Number of customers by company size, student performance on an exam, frequency of a product defect.

Symbol maps — Use for totals rather than rates. Be careful, as small differences will be hard to see.

Examples: Number of customers in different geographies.

Area maps — Use for rates rather than totals. Use sensible base geography.

Examples: Rates of internet-usage in certain geographies, house prices in different neighborhoods.

Box-and-Whisker — Showing the distribution of a set of a data.

Examples: Understanding your data at a glance, seeing how data is skewed towards one end, identifying outliers in your data.



How your audience “reads” your dashboard is not a trivial consideration. Your dashboard’s purpose is to help guide the reader’s eye through multiple views in coordination and tell the story of each insight. Your dashboard needs a sensible “flow” and a logical layout of different pieces of information. The more you employ better dashboard design, your users will discover what’s happening, why, and what’s most important. Consider how you’re guiding their eyes across the dashboard. Are you showing the user where to look next?

Design theory gives us plenty of advice on how best to succeed. Layout is a key component of any successful dashboard design, here are a few concepts you want to think about when building visualizations:

  • Newspaper or Z-layout — The most important content is put either at the top or the left of a visualization, as users move right and down for more specific content.
  • White space — Using negative space (blank spots) and padding to delineate sections of your visualization – don’t use thick “grid lines” as you would see in a table.
  • Size — More important pieces of content (KPIs, summary visualizations, etc.) should be larger than other items.
  • Device type — With device-specific dashboards you can create the optimum viewing experience on desktop, laptop, tablet, and phone.



Color is one of the most powerful aesthetic features because it’s an attention-grabber. It’s the first thing we notice, and it can immediately highlight specific insights or identify outliers, but it is not an unlimited design resource.

Using color effectively is critical for producing quality data visualizations – color types (alerting vs highlighting), creating custom color palettes, and consistency—are key aspects to build into your standards.

The correct use of color is critical for producing coherent and impactful data stories. The key factors that should be taken in to consideration for any successful dashboard are:

  • Managing color choices — The primary color(s) that make up most of your design should be a neutral color. Using techniques like grayscale, you maximize the possibility for contrast and visibility of your data driven points. Your extended colors—accents, emphasis, and alerts—should reflect the brand. Any extended color should be used sparingly to draw attention to key messages within the data.
  • Color types — Understand when to use sequential, diverging, categorical, highlighting, or alerting color motifs.
  • Custom color palettes — Build your own company palettes to bring a sense of uniformity and provide guiderails for new users.
  • Consistency — Double-check your visualizations to make sure a color (e.g. red) does not mean three different things. Similar and repeated colors can imply a relation where one doesn’t exist.
  • Accessibility — Remember to account for color blindness in the design process.

Titles & Subtitles

Titles are an easy way to make your dashboard more digestible for your audience. You add more context with subtitles that describe how to interact with the worksheet or dashboard. This is a powerful and simple way to make dashboards easier to navigate. In the example below, the question pulls the audience in and then tells the audience how to answer the question using the dashboard.

Effective Title and Subtitle


Similarly, by changing your filter title to something more intuitive, you guide viewers through how to interact with a dashboard.

Example of a Filter


Tooltips guide the audience by highlighting important information. In the example below, the County and State are highlighted through a bold effect and color change, and we don’t have to partition our scatter plot further. We add important and related dimensions and measures in the tooltip. This helps save space and declutter the dashboard so our viewers can focus on gleaning insights instead of interpreting the visualization.

Effective Tooltip


If the viewer notices something interesting in the tooltip, they can interact directly with the tooltip and watch the rest of the visualization come to life, highlighting related marks and outliers.

Formatting a Tooltip


Typography is important. It can be tempting to use many font types and sizes in a dashboard. Don’t do that; instead, define a clear hierarchy for your typography. In the example below, there is a top, mid, and low-level font. The mid-level is blue to focus viewer attention. Color draws the eye to the most important level (which needn’t necessarily be the top-level font).

Top, Mid, and Low-Level Fonts (Courtesy of The Big Book of Dashboards)


Make sure that font selection is done to reinforce a visual hierarchy within your visualization through size, boldness, color and type.

  • Size — Larger elements convey importance as they catch the eye.  Save your largest fonts for KPIs, titles, etc.
  • Boldness — Bolder elements convey importance as they catch the eye. You can vary boldness throughout your visualization in conjunction with size. For example, your title and KPIs could both be 24pt font, but making your KPIs bold will “pop” them, allowing your audience to focus there first.
  • Color — Generally it’s good to stick with gray and black hues in your titles, text, and KPIs. You can “pop” your KPIs by giving them a color treatment, but you have to balance this with the other colors used in your visualization. Darker colors will draw the eye, so it’s wise to lighten your titles so they don’t compete for visual attention.

Dashboard Size

By default, Tableau dashboards are set to use a fixed size. If you keep this setting, be sure to construct your visualization at the size which it will be viewed. You can also set Size to Automatic, so Tableau automatically adapts the overall dimensions of a visualization based on screen size. This means that if you design a dashboard at 1300 x 700 pixels, Tableau will resize it for smaller displays—and sometimes this results in scrunched views or scrollbars. The Range sizing feature is helpful for avoiding this.

Dashboard Size Range

If you're using Tableau Desktop to create dashboards, you can also design for specific device layouts, so that on tablets, for example, your dashboard contains one set of views and objects, and on phones it displays another. See Create Dashboard Layouts for Different Device Types for steps.

Dashboard Interactivity

When designing a dashboard, you need to consider your audience, and how you can communicate to them that they can interact with the dashboard. Skilled users know to click and experiment, but new users may not have the knowledge or confidence. Your job is to help them make these decisions consciously, not by accident.

It’s important to make any interactivity obvious to your audience—even by creating subtitles to instruct them to click or hover for more information. Add interactivity to your data using filters, tooltips, and actions. Filters are the most obvious way to interact with a dashboard. Users can also interact with your visualizations by selecting marks and hovering to see tooltips. The actions you set up can respond with navigation and changes in the view. The table below enumerates the ways to create interactivity in your dashboards.



Highlighting & Highlight Actions

  • Easily find data of interest while remaining within context.
  • See other marks with shared attributes.
  • Find related data across sheets.

Filtering & Filter Actions

  • Focus on data you want to analyze.
  • Control context of data.
  • Show relevant data and remove unnecessary data.


  • Explore what-if scenarios.
  • Customize your views.
  • Enhance dashboard flexibility.

Sets & Set Actions

  • Dynamically update the members of a set.
  • Compare parts to whole.
  • Seamlessly drill down through hierarchies.
  • Update a calculation by interacting with data.


  • Provide details on demand.
  • Keep your dashboard minimalistic.
  • Insert a viz in a tooltip.

URL Actions

  • Incorporate external content in a dashboard.
  • Provide more in-depth information on demand.
  • Link users to websites.

Dashboard Navigation

  • Guide users through your workbook.
  • Direct users to additional content.


When designing dashboards, consider how and why you incorporate interactivity into the dashboard. The following questions are helpful:

  • Why does a viewer need to interact with the dashboard?
  • What extras insight will be gained through the interactivity?

Designing for Performance

When we talk about performance, we mean the speed with which you can work in Tableau. That might mean the speed of data analysis—for example, if you work in Tableau Desktop on a large corporate database that takes forever in real time when you access it remotely. Or it might mean simply the speed of loading views or dashboards that you access on your desktop or from Tableau Server or Tableau Online.

Performance and efficiency should be treated as part of the design process—not as an afterthought. Responsiveness is an important success factor for end users when viewing reports and dashboards, so making your workbooks run as quickly as possible makes for happier users.

There are several factors that make a workbook “efficient”. Some of these factors are technical and some more user-focused but in general an efficient workbook is:

  • Simple — Is it easy to create the workbook and will it be easy to maintain in the future? Does it take advantage of the principles of visual analysis to clearly communicate the message of the author and the data?
  • Flexible — Can the workbook answer multiple questions the users want to ask, or just one? Does it engage the user in an interactive experience or is it simply a static report?
  • Fast — Does the workbook respond quickly enough for the users? This may mean time to open, time to refresh, or time to respond to interaction. This is a subjective measure, but in general we want workbooks to provide an initial display of information and to respond to user interactions within seconds.

The performance of a dashboard is impacted by the following:

  • The visual design at both the dashboard and worksheet levels, e.g. how many elements, how many data points, use of filters and actions, etc.
  • The calculations, e.g. what kind of calculation, where the calculation is performed, etc.
  • The queries, e.g. how much data is returned, impact of custom SQL, etc.
  • The data connections and underlying data sources.
  • Some differences between Tableau Desktop and Tableau Server or Tableau Online.
  • Other environmental factors, such as hardware configuration and capacity for Tableau Server.

For more information, see Designing Efficient Workbooks.


To make your views accessible to as many people as possible—or if you work in an environment that is subject to US Section 508 requirements or other accessibility-related laws and regulations—you can use Tableau to build data views that conform to the Web Content Accessibility guidelines (WCAG 2.0 AA). This includes building views that are accessible to users who use screen readers, braille keyboards, keyboard-only navigation, and so on. Refer to Build Data Views for Accessibility for details. Additional resources are available on the “FAQ: Accessibility” post in the Tableau Community forums.

Thanks for your feedback!