Skip to content

Latest commit

 

History

History
29 lines (20 loc) · 2.75 KB

README.md

File metadata and controls

29 lines (20 loc) · 2.75 KB

CORE Skills Data Science Springboard - Day 7 - Telling stories with data

The aim of today's session will be to develop an understanding of the intersection between data and communication – where this works well, where this goes wrong and how to improve the communication from their projects. We'll look at how we can use data to tell compelling stories, change the way people view problems and effectively suggest a course of action.

You should aim to:

  • understand avenues for communicating project results beyond the usual dashboard/graphs approach.
  • understand the use of design principles to engage your audience and draw their attention
  • be able to critique data presentations (both good and bad) in a variety of media
  • gain experience at developing your own effective data-driven communication

Pre-session Reading & Resources

Have a poke around online to find examples of excellent online examples of data-driven storytelling. You should also check out:

We'll cover visualisation and perception briefly in the course. For more details on the science behind how we perceive order and make decisions, take a look at Thinking Fast and Slow by Daniel Kahneman: https://www.amazon.com/Thinking-Fast-Slow-Daniel-Kahneman/dp/0374533555

The grand-daddy of visualisation is Edward Tufte, who was writing about this back in the days of moveable type, rather than electrons. His book Visual Explanations: Images and Quantities, Evidence and Narrative is the default text in the field and has arguably influenced more data viz practitioners than anyone else: https://www.edwardtufte.com/tufte/books_visex

Have a look around on the internet for examples of bad visualisation - there are plenty of sites with 'halls of shame'. One good example is How to lie with maps: https://www.ft.com/content/65b5df0e-49ff-11e8-8ee8-cae73aab7ccb

Todo: add pre-session reading and resources (and why you might like to read them - see week two's README as an example)