Business Intelligence Blog from arcplan
17Aug/112

Business Intelligence Dashboard Best Practices

by


arcplan DashboardDashboards are like snowflakes: I don’t think I’ve ever seen two enterprises with identical dashboard designs. Which isn’t a bad thing. Dashboards should be tailored to your organization’s identity and the way your employees work. We have a client in the auto industry whose dashboards look like the, well, dashboard of a car – full of speedometers and gauges. We have other clients who like to deploy their BI dashboards in SharePoint because that’s where they house all of their corporate information. But the business intelligence dashboards our clients create have a few things in common that I consider best practices:

1) They incorporate data from more than 1 source.

I’m betting that not all of your data sits in the same location. You’ll only get a holistic view of your organization’s performance if you’re integrating data from various sources. Whether it’s ERP + sales data, or marketing data + finance data, or Essbase data + SQL Server data, your dashboards need to support fast, easy integration of your various data sources.

Best practice BI dashboards pull data from internal and external sources (when necessary) to create entirely new views of performance. We have clients integrating data from Standard & Poor’s with their accounts receivable information to match up delinquent clients with their S&P credit rating. We have insurance companies putting claims data on top of Google Maps. And we work with several enterprises that are integrating product revenues from their financial system with Salesforce.com customer data. These are examples of mashups – web applications that make existing data more useful – and they’re extremely helpful on performance dashboards, even if only for quarter-long tactical analysis.

2) They provide at-a-glance views of performance.

Dashboards are for busy people who can’t dig deep every day to spot issues. Your dashboard might benefit from incorporating stoplight indicators that tell users if data is entering into dangerous territory without having to drill down. In arcplan, thresholds can be set separately for each KPI – meaning you set when the light shows up green, yellow, and red, giving users a quick visual cue that focuses them on the areas that need attention.

Continue reading this post >>