Data visualization presentation provided during the University of Cincinnati Data and Analytics conference. Discusses how to build out a data visualization group from scratch.

4. •
•
•
•
•
•

5. •
•
•
•
•
•
•

7. •
•
•
•
•
•
•
•

8. •
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

10. •
•
•
•
•
•
•
•
•
•
•

13. •
•
•
•
•
•
•
•
Tip: Gather reporting requirements to streamline your data efforts

14. •
•
•
•
•
•
•
•
•
•
•
•

15. •
•
•
•
•
•
Tip: If you have never used a database
before, I recommend taking an entry level
SQL course and also trying out Microsoft
SQL Server Express (free)
https://www.microsoft.com/en-us/sql-
server/sql-server-editions-express

16. Computing machines (desktops & servers)
Microsoft SQL Server, MySQL, and Aurora
databases)

17. • Geographic regions
• Localization of reporting servers
• Multi availability zones deployment for
high availability
•
•
•
•
•

18. •
•
•
•
•
•
•
•
•
•
•
•
•

19. •
•
•
•
•
•
•
•
•

21. •
•
•
•
•
•
•
•

22. •
•
•
•
•
•
•
•

23. Use business specific questions to test the “quality” of your report
• Which Product has the high revenue for the year?
• What is the top product for each month?
• What is the difference performing products compared to the lower performing
products?
• Which product month combination has the lowest revenue for the year?

24. Ask yourself the same questions with
new visuals
If its quicker and easier to understand
then you probably created a better visual
If not, maybe consider your design
choices and rethink your visuals

25. •
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

26. Leverage the strong points
•Self service analytics & discovery
•Eliminate dependency on developers
•Development speed
•Web reporting platform
•Interactive reports
•Self schedule delivery
•Live data connections
•Modern visuals
Target current problems
•Missing KPIs
•KPIs that are difficult to create
•Reports that people don’t like
•Reports that are known to be incorrect or delivered inconsistently
Tip: What works for one person/company might not work for you
Tip #2: Don’t purchase a new product and rebuild the exact same reports

27. Ask the end-user(s) questions to determine the focus
• What are the most important pieces of data?
• What do you hope this report will achieve or answer?
• What is the goal of this visualization?
• Who is the attended audience for the visualization?
• How granular should the data be?
• How often does the data need to be updated?
• What “story” do we want to tell?
Tip: Ask for current examples of any reports/dashboards, this helps show before
& after improvements but avoid recreating the current report

30. •
•
•
•
•

32. Leverage data visualization strengths
• Keep it Simple: basic chart types (lines & bars) with a high level of execution
• Design: Make it look great (at least better than Excel)
• Color: Use a modern but simple color palette
• Create Interactivity: Use dashboard actions
• Make it Meaningful: Focus on the end user and goals
• Build Trust: Double check your data & numbers
The 30* second test (Time to Insight)
• Dashboards should be clear and easy to understand (if you don’t know what you are
looking at within 30 seconds, the design could be too complicated)
*Exact timing target varies
Tip: Listen and watch for feedback indicators when individuals view your report
Tip #2: Use clear and concise labeling and titles with consistent verbiage

36. 36

37. BAR CHART DESIGN
37

38. BAR CHART DESIGN
38

39. BAR CHART DESIGN
39

40. CHAT EXAMPLES
40

41. LINE CHART DESIGN
41

42. DIFFERENT VIEWS
42

43. •
•
•
•
•
•
•
•
Tip: Reach the “AHA” moment when people realize current reports might not be the best
(make people into data visualization believers)

44. •
•
•
•
•
•
•
•
•
•
•
•
•
•
Tip: Build a template to set standard colors, fonts, and designs for common charts

46. •
•
•
•
•
•
•
•
•
•
Embrace data visualization champions / supporters within your company

47. Attitude and personality is important. Skills can be trained!

48. •
•
•
•

49. •
•
•
•
•
•
•
•
•
•
•

53. Resources
https://aws.amazon.com/redshift/

54. Resources