Tips & tricks
Below is a collection of dashboard and widget tips and tricks you can use to make the most out of the ESO Insights module.
As a dashboard designer, put yourself in the shoes of someone who has only viewer-level access. Ask yourself:
-
Where could they get confused or have questions?
-
Where can you add clarity to the information that you are presenting?
Tip: When you create a dashboard, use a descriptive name to indicate the purpose of the data on the dashboard.
Information on creating a dashboard is available in Add a new, blank dashboard.
Tip: If you duplicate a dashboard, rename the duplicated dashboard right away, to prevent confusion between the two in the future.
Information on duplicating a dashboard is available in Duplicate an existing dashboard. Information on renaming a dashboard is available in Rename a dashboard.
Tip: Add titles and text blocks to the dashboard to indicate the purpose of the data or to provide a detailed explanation for the dashboard, or to explain the content of a neighboring widget on the dashboard.
Information on adding text to a dashboard is available in Add a text block to a dashboard.
Tip: Put the most-important data at the top of the dashboard, so viewers can see it as soon as they open the dashboard, and do not have to go scrolling to find it.
Information on placing widgets at or near the top of the dashboard is available in Arrange and resize widgets on a dashboard.
Tip: Do not add more than one pivot table widget to a dashboard. Pivot tables can present large amounts of data, and can visually overwhelm a viewer.
Information on adding a widget to a dashboard is available in Add a widget to a dashboard. Information on configuring a pivot table is available in Configure a pivot table.
Tip: Do not add more than one pie chart widget to a dashboard. Pie charts portray a stagnate time frame, so trending data is off the table with this visualization method. When you use one, make sure your audience understands the timeframe portrayed.
Information on adding a widget to a dashboard is available in Add a widget to a dashboard. Information on configuring pie charts is available in Configure a pie chart.
Trick: Instead of using multiple pies chart in one dashboard, combine the data in a different type of chart, such as a stacked bar chart.
Information on bar and column charts is available in Configure a column or bar chart.
Tip: Limit the number of number charts on a dashboard, to prevent your narrative from becoming diluted or make your dashboard a bit superficial. If you want more in-depth information, leave room for other types of data visualization that drill down a little deeper.
Tip: When you add it to a dashboard, use a descriptive name for a widget, to indicate the purpose of the data in the widget.
Information on adding a widget to a dashboard is available in Add a widget to a dashboard.
Tip: If you duplicate a widget, rename the duplicated widget right away, to prevent confusion between the two in the future.
Information renaming a widget is available in Rename a widget.
Tip: When filtering at the widget level, remember that from the dashboard view, there is no indication that the ESO Insights module is filtering data at the widget level. This can confuse your dashboard viewers, and you may want to reconsider filtering at this level.
Trick: If you decide to filter at the widget level anyway, include a reference to this in the widget's name or information menu, to let to viewers know that the widget's data is already filtered.
Information on filtering at the widget level is available in Configure a widget filter. Information on renaming a widget or adding a description to the widgets information menu is available in Rename a widget and Add a description to a widget, respectively.
Tip: Too many lines or bars (variables) in a chart widget can make a chart complicated and hard to decipher. If you have too many variables, consider a second (or even third) chart to tell this story.
Tip: When it comes to layout in a chart widget, keep your numbers relevant. When you set up your axis scale, keep it close to the highest data point.