Dashboards Driving Decision Making - ui and me


Published on

Defining dashboard fundamentals.

Published in: Business, Technology
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Dashboards Driving Decision Making - ui and me

  1. 1. Dashboards: Driving Decision Making Mary Chant, Certified Usability Analyst http:// www.uiandme.com
  2. 2. Dashboards: : Driving Decision Making
  3. 3. <ul><li>“ Dashboards are much more than pretty data presentations. They are powerful, flexible business tools which allow for true information democracy – actively empowering business users at all levels to make better decisions every single day.” Hyperion White Paper </li></ul><ul><li>“ It is a well-established management principle that you cannot manage what you cannot measure. It is equally true, however, that you cannot manage well what you cannot monitor. That is where enterprise dashboards come in.” Business Case for Enterprise Dashboards, Dashboard Execution </li></ul>
  4. 4. Dashboard: Business Activity Monitoring Business Activity Monitoring – BAM – a right-time system enabling organizations to monitor and manage business processes that span multiple systems, departments, and organizations. BAM is basically another label for an operational dashboard. BAM characteristics: 1. Event-driven processing model that captures events in real time from multiple systems that comprise an end-to-end business process. 2. Robust business rules that let users define alerts, targets, and thresholds for individual performance metrics. 3. A business-user-friendly dashboard that updates metrics as events flow through the system and puts metrics into context by relating them to business objectives. 4. A collaborative workflow system that lets one set up formal and informal processes by which users can collaborate and discuss results. * p. 117, definition of an Operational Dashboard, Performance Dashboards, Eckerson
  5. 5. Dashboard: Real Time & Right Time Real Time Technologists use the term real time to mean data that are updated instantaneously after an event occurs. Here, the latency between an event and when workers view it on a dashboard is zero. . . In actuality, it is difficult, expensive, and often unnecessary to deliver data in real time with zero latency. Conversely, business people use the term real time to mean something that happens quickly. However, how fast is real time to them? Is it a second? A minute? An hour? In the end, the definition of real time varies from business person to business person. Right Time Right Time. Perhaps, a better term to describe the timely delivery of information to decision makers is right time. Ultimately, business executives do not care about the degree of latency in a performance dashboard. They simply want the system to deliver the right information to the right people at the right time so they can make optimal business decisions. Right time puts the emphasis on the business value of information, not its latency. *p. 114, real time vs. right time, Performance Dashboards, Eckerson
  6. 6. Dashboard: Components
  7. 8. Dashboards: Return on Investment *Enterprise Dashboards, Malik See also: “Reduced Costs Through Business Intelligence Standardization”, Business Objects Case Study
  8. 9. Dashboard: Sample Milestones/Effort Chart
  9. 10. Dashboard: Criteria <ul><ul><li>Criteria for Evaluating Performance Dashboards </li></ul></ul><ul><ul><li>Design </li></ul></ul><ul><ul><li>Analysis </li></ul></ul><ul><ul><li>Delivery </li></ul></ul><ul><ul><li>Administration </li></ul></ul><ul><ul><li>Infrastructure </li></ul></ul><ul><ul><li>Vendors </li></ul></ul>
  10. 11. Dashboard: Features <ul><ul><li>Features for Evaluating Dashboard Software </li></ul></ul><ul><ul><li>End-user experience </li></ul></ul><ul><ul><li>User management </li></ul></ul><ul><ul><li>Drill-down </li></ul></ul><ul><ul><li>Reporting </li></ul></ul><ul><ul><li>Data connectivity </li></ul></ul><ul><ul><li>Alerts </li></ul></ul><ul><ul><li>Visualization </li></ul></ul><ul><ul><li>Collaboration </li></ul></ul><ul><ul><li>System requirements </li></ul></ul><ul><ul><li>Image capturing and printout </li></ul></ul>
  11. 12. Dashboard: Sample Evaluation
  12. 13. Dashboard: User Requirements “ By treating BI (Business Intelligence) as a set of technologies, most organizations veer off track, building ever-more-complex systems that fail to meet user needs – while what’s really needed is a better understanding of the underlying data and business requirements.” . . . “You need to be business-driven, not IT driven. Otherwise, you get a tool that no one uses.” *Rethinking Business Intelligence, Galen Gruman, Infoworld, 04/02/07 “ With contextual, personalized information at their fingertips, users can rapidly pinpoint problems, detect emerging trends and respond to shifting business conditions.” *Choice with Context: Enterprise Dashboards from Hyperion “The most common customer complaint about analysis applications today is that they are too hard to use.” *Visual Analysis for Everyone, Tableau Software “ You should evaluate the different tools against the specific needs of your end users. Because there is no such thing as a “typical user,” you should first group or segment your users into different profiles. Examples of appropriate profiles may include executives, analysts, general business users, and external users such as customers and partners.” *Choosing a Business Intelligence Standard, Business Objects
  13. 14. Dashboard: Vendors Major Dashboard Vendors “For the most part, the vendors who have developed the potential of enterprise dashboards most effectively are the reporting and Business Intelligence (BI) vendors such as: Business Objects, Cognos, Hyperion, Micro-Strategy. Also there are niche vendors such as iViz Group, iDashboards, Noetix, QPR Software, and Theoris, who have developed dashboard software with certain characteristics that have been left out by the major BI vendors.” *Enterprise Dashboards, Malik Vendor Resources http://www.cognos.com/products/now/application-workbench.html http://www.tableausoftware.com/products.htm http:// www.dundas.com/Dashboards/index.aspx?Campaign = ASPAlliancePS http://www.businessobjects.com/products/dashboardvisualization/dashboardbuilder.asp http:// www.iviz.com/portfolio/portfolio.htm http://www.2020software.com/software/display.asp?tMethodID=9&tMethod= category&tse = Google&tst = business+intelligence+dashboards&CMP =KNC-Google Comparison of Top 8 Business Intelligence Software Solutions Vendor Evaluation Industry analysts such as Gartner, Meta Group, and IDC regularly evaluate the different vendors in the market and can help advise on the choice of a particular vendor or product based on your projects. *Choosing a Business Intelligence Standard, Business Objects
  14. 15. Dashboard & Alerts “ Although it does so much more, the central purpose of a dashboard is to warn the user when any relevant metrics are out of acceptable boundaries. In the dashboard terminology, these alerts consisting of rules and actions add critical value to an enterprise dashboard deployment complemented with strong visual indicators of warnings. *Business Case for Dashboard Execution, Dashboard Execution “The system should also let developers and end-users define rules about when and how users should be notified if parameters are exceeded for a a given metric (i.e., alerts ) as well as when and how to initiate automated actions based on those alerts (i.e. agents). Visual alerts should be accompanied by text that explains the problem, a report that users can click to see actual data and a URL to initiate additional action, such as to refresh a report or display contact information for someone to call. The rules engine should accept events from third-party systems as well.” *p. 215, Performance Dashboards, Eckerson
  15. 16. Alerts: Definition Notifications sent by users or administrators that let users know when a metric exceeds predefined thresholds.
  16. 17. Alerts: Key Performance Indicators <ul><li>Key Performance Indicators - KPI </li></ul><ul><li>KPI are determined through requirements analysis in order to build customized and effective dashboards </li></ul><ul><li>Key Performance Indicator Elements: </li></ul><ul><li>Data source(s) (including data validation and data redundancy) </li></ul><ul><li>Granularity </li></ul><ul><ul><li>Time – hourly, daily, weekly, etc. </li></ul></ul><ul><ul><li>Geography – zip code, city, state, etc. </li></ul></ul><ul><ul><li>Product – UPC, item, item group, brand, category, etc. </li></ul></ul><ul><li>Calculation (sum, average, percentage, and other calculations) </li></ul><ul><li>Variance (basis for change, change calculation) may include periodic calculations and forecasts </li></ul><ul><li>Assessment of the attributes of the key performance indicators helps determine navigation and the user experience (i.e. meaningful drilldown paths). </li></ul>
  17. 18. Alerts: Description <ul><li>Alerts and key performance indicators are related </li></ul><ul><li>Being out-of-variance triggers an alert </li></ul><ul><li>Alerts provide a method for exception management </li></ul><ul><li>Distribute information to the right person at the right time </li></ul><ul><li>Can also trigger actions/events within the system </li></ul>
  18. 19. Alerts: Elements <ul><li>Rules </li></ul><ul><li>Actions </li></ul><ul><li>Recipients </li></ul>
  19. 20. Alerts: Requirements <ul><li>Alerts Requirements (Basic) </li></ul><ul><li>User is allowed to archive alerts </li></ul><ul><li>User is allowed to delete alerts </li></ul><ul><li>User is allowed to organize alerts </li></ul><ul><ul><li>Into folders </li></ul></ul><ul><ul><li>Into categories </li></ul></ul><ul><li>User is allowed to forward alerts </li></ul><ul><li>Alerts Requirements (Advanced) </li></ul><ul><li>Collaboration </li></ul>
  20. 21. <ul><li>Alert ID – for managing/referring to alerts/archiving </li></ul><ul><li>Date/Time stamp for alert </li></ul><ul><li>Date/Time the message information takes effect (if applicable) </li></ul><ul><li>Date/Time – expiration </li></ul><ul><li>Distribution status: Public (General), Restricted, Private </li></ul><ul><li>Distribute by: User Group, Job Profile, Individual </li></ul><ul><li>Headline </li></ul><ul><li>Event Type </li></ul><ul><li>Event Category </li></ul><ul><li>Urgency (time sensitive) </li></ul><ul><li>Severity (importance or priority) - commonly ranked as: extreme, severe, moderate, minor or unknown/undetermined </li></ul><ul><li>Risk commonly ranked as: high, moderate, low, minimal, unknown </li></ul>Alerts: Common Attributes <ul><li>Name of distribution group </li></ul><ul><li>Body text – event description </li></ul><ul><li>Link to additional information </li></ul><ul><li>Recommended actions </li></ul><ul><li>Link to graphic file </li></ul><ul><li>Link to audio file </li></ul><ul><li>Link to URL </li></ul><ul><li>Contact/follow-up or confirmation </li></ul><ul><li>Rule/threshold or parameter that caused the alert to be launched </li></ul><ul><li>Scheduled/recurring – send this alert every Monday morning </li></ul><ul><li>Scheduled/triggered </li></ul><ul><li>Reminder </li></ul><ul><li>Real Time/Right Time </li></ul><ul><li>Create alerts for shared lists and documents </li></ul><ul><li>Ability to Disable Alerts </li></ul><ul><li>Project level alerts </li></ul>
  21. 22. Resources <ul><li>Books </li></ul><ul><li>Enterprise Dashboards, Shadan Malik </li></ul><ul><li>Performance Dashboards, Wayne W. Eckerson </li></ul><ul><li>Information Dashboard Design: The Effective Visual Communication of Data </li></ul><ul><li>Articles </li></ul><ul><li>Analytic Applications versus Business Intelligence Tools </li></ul><ul><li>Dashboard Execution, Business Case for Enterprise Dashboards </li></ul><ul><li>Guidelines for Effective Alerts, Paige K. Parsons </li></ul><ul><li>Common Alerting Protocols, Common Alerting Protocol Technical Working Group </li></ul><ul><li>White Papers </li></ul><ul><li>Choice with Context: Enterprise Dashboards from Hyperion </li></ul><ul><li>Visual Analysis for Everyone, Understanding Data Exploration and Visualization, Tableau Software </li></ul><ul><li>Choosing a Business Intelligence Standard, Business Objects </li></ul><ul><li>Other Recommended Books </li></ul><ul><li>Super Crunchers: Data Mining and Statistical Analysis, Ian Ayres </li></ul><ul><li>Readings in Information Visualization: Using Vision to Think </li></ul>
  22. 23. <ul><li>Mary Chant , Certified Usability Analyst </li></ul><ul><li>website: http://www.uiandme.com </li></ul><ul><li>email: [email_address] </li></ul><ul><li>http://twitter.com/uiandme </li></ul><ul><li>Delicious </li></ul>Contact