Telling stories with data is hard to do. It relies on a diverse set of skills - data processing, graphic design, storytelling, and more. This activity helps you build those skills by taking apart work that others have done (the good and the bad) to build your critical eye. You'll help participants break down and discuss a four things about a visualization - (1) the data it uses, (2) the ways it shows that data, (3) the narrative it is trying to tell, and (4) evaluating whether it combines those to tell the data story well.
Inicie la actividad
Begin by handing out printouts of the graphic you've selected and giving a little backstory about its context. For example, the USAID graphic was commissioned as part of a series for their 50th anniversary celebration, focused on highlighting success but also the challenges ahead. We've been told it was published online but also displayed in their entrance as a large banner. It was created for the USAID by an independent design firm named Lemonly.
Give participants just a minute or two to review the handout together. Don't give them too long - you want their first reactions to come out.
Lead a Conversation
After participants have looked over the visualization, ask them a series of questions. Try to keep the discussion focused on these exploratory questions rather than whether the visualization is "good" or "bad" (evaluation comes after exploration). First ask them to identify some of the datasets used. Collect four or five answers from participant. For the USAID graphic, these often include answers like "population data over time", "crop yield predictions", and "animal ownership in Ecuador". Then talk about how telling these stories requires you to pull from multiple datasets; you can seldom put together a strong story with just one spreadsheet.
Next, ask participants to identify how this data is represented. Collect a few answers. For example, in the USAID graphic population size is represented by a globe increasing in size and percentages are represented as donut charts. Briefly share how this sets up a consistent set of charts and symbols and ways to use them. We call this the "visual vocabulary" of the story.
Thirdly, ask participants to identify the short story they think this graphic is trying to tell. What are the data and visual representation trying to say? Ask folks to summarize it in just one sentence, like you would in a tweet. In the USAID example most people think the story is something like "food needs are rising, and if we can help female farmers we'd be better prepared to produce enough food." Try to keep participants focused on the story, rather than what they think about it (that comes next).
Pull it All Together
To finish, ask folks if they think the story is well told. What elements best support the story? Are there extraneous pieces that don't help the story along? Are there pieces that actively distract from the main point or contradict it? In the USAID example focus on the takeaway message - what is it? Is it emphasized enough? Does it solve the problem? Emphasize that telling these stories has to focus on a main point, and everything needs to support it. Even if there is some cool data that you want to include, you need to make sure it supports the main story, otherwise it will just distract. Are there examples of data that could be removed from the USAID story to make it more effective?