Upload
others
View
2
Download
0
Embed Size (px)
Citation preview
2012 Redwood Analytics® User Conference
Analysis. Insight. Action.
Dashboards and Adoption Strategies Lessons Learned
Derek Schutz Director of Programs
2012 Redwood Analytics® User Conference
Analysis. Insight. Action.
Panelists
Michael Porter – DLA Piper LLP Director of Business Intelligence
Purvi Sanghvi – Patterson Belknap Webb & Tyler LLP Manager, Financial Business Analysis
Milan Babic – Shepherd Mullen Richter & Hampton LLP Financial Analyst, Business Intelligence and Analytics
2
BI 5
Dashboard
Analytics
Reporting
Alerting
Security
Share-
point
Compa
tible
Mobile
Web
Based
Bursting
Enhanc
ed
Ware-
house
• Integrated Analytic, Reporting, Distribution Mechanisms
• Bursting and Subscription Options
• Alerting Capabilities
• Dashboard Customization
• Data Level Security
• Enhanced Warehouse
• Mobile Strategy
Overview of BI5
3
Concepts of a Successful Dashboard
• Simple (not overly crowded/complex)
• Data is meaningful and actionable
• Timing of data is relevant
• Data is framed Overview First, Zoom and Filter, Details on Demand
• Supported
• Flexible/Updatable
4
Sample Dashboards
5
Sample Dashboards
6
Sample Dashboards
7
Sample Dashboards
8
Sample Dashboards
9
10
11
12
13
14
15
16
Sample Dashboards
17
18
19
20
21
22
Lessons Learned
23
Lessons Learned
• ‘Cool Looking’ is NOT the deciding factor
24
Cool is NOT the Deciding Factor
25
Lessons Learned
• ‘Cool Looking’ is NOT the deciding factor
• Provide finite options, don’t leave it open-ended
26
Too Many Options leads to Confusion
27
Lessons Learned
• ‘Cool Looking’ is NOT the deciding factor
• Provide finite options, don’t leave it open-ended
• Have a ‘Decider’ and make sure THEY Decide
28
Large Committee’s Lead to Strange Products
29
Lessons Learned
• ‘Cool Looking’ is NOT the deciding factor
• Provide finite options, don’t leave it open-ended
• Have a ‘Decider’ and make sure THEY Decide
• It’s a Dashboard, not the entire car manual
30
Dashboards are Heads-Up Displays
31
They are NOT Going to Answer Every Question
32
Lessons Learned
• ‘Cool Looking’ is NOT the deciding factor
• Provide finite options, don’t leave it open-ended
• Have a ‘Decider’ and make sure THEY Decide
• It’s a Dashboard, not the entire car manual
• Your Dashboard will not impress everyone
33
100% Approval is NOT Achievable
34
Panel Discussion
Michael Porter – DLA Piper LLP
Director of Business Intelligence
Purvi Sanghvi – Patterson Belknap Webb & Tyler LLP
Manager, Financial Business Analysis
Milan Babic – Shepherd Mullen Richter & Hampton LLP
Financial Analyst, Business Intelligence and Analytics
35
Overview of Dashboard Process
1. Pre - Planning phase Gather requirements
Focus on DATA NEEDED
Determine Pilot Group(s)
Determine Rollout Plan
2. Planning Phase Whiteboard out ideas
Take Notes
Determine Timeline – Add 2 months
Rethink Rollout Plan
3. Building Phase Build our initial DB
Gather feedback EARLY and often
Be Iterative
Amend Rollout Plan
4. Rollout Phase FOLLOW Rollout Plan
Educate First
Provide Documentation
Start Small
Gather Feedback
5. Phase 2 Start Again
2012 Redwood Analytics® User Conference
Analysis. Insight. Action.
Dashboards & Adoption Strategies Lessons Learned
Derek Schutz Director of Programs