Read-Only Dashboards

Read-only dashboards are visual tools that aggregate and display critical metrics and key performance indicators (KPIs) in a single screen, enabling users to monitor and examine business performance at a glance.

When designing read-only dashboards, keep the following factors in mind so that the dashboards are appealing and functional to the intended users:

• Know your audience

  Different dashboards have different audiences and different uses. Managers and Executives use read-only dashboards strategically to monitor essential business KPIs and metrics so they can effectively make decisions. Data Analysts and Interactive Users use read-only dashboards analytically to visualize important high-level summary data with the ability to drill through to detailed data.

  Note:

  Another type of dashboard user are Data Input and Impact Analyzers. They are data entry users who use dashboards as a data input interface, but also have the ability to immediately view the newly input data impact on a chart in real-time. These types of dashboards are unique to Oracle Enterprise Performance Management Cloud and are called write-enabled dashboards. For information about designing write-enabled dashboards, see Write-Enabled Dashboards.

• Keep it simple

  The fundamental challenge of dashboard design is to squeeze as much information as possible into a small amount of space. Nobody wants to leave out critical information, but there's a tradeoff between complexity and usefulness. Be clear in your objective for a dashboard, and narrow the information to that which directly applies to meeting that objective. If there is deeper information under the initial data presented, provide an option to drill down and seek ever more focused and useful information.

• Prioritize elements

  Prioritize elements top left to bottom right. Place high-level, easy-to-read, actionable components near the top left, and place components with supporting information lower. If your audience has limited time or attention, place important elements where they will be noticed.

• Aesthetics matter

  The aesthetics of a dashboard (or lack therof) can impact its adoption. Use only one typeface, and don't overuse colors. Each color in a data visualization should serve a purpose. Use different dashboard colors only when you're communicating different things. Be consistent. If your dashboard includes multiple charts, ensure to match colors between charts when they refer to the same group or entity. If colors change their meaning between charts, this can make it harder for users to understand the chart.