Telling stories with data is absolutely nothing new for data journalist John Burn-Murdoch. Starting with an initial six week spell with The Guardian, he now works in the interactive news team of the Financial Times. With Journocode, he talked about data journalism and his work.
Journocode: What do you think is the most important task of data journalism?
It's very easy as a data journalist to get hung up on the data and the tools. These are the tangible elements that differentiate data journalism from other forms of journalism, after all. But this mindset risks focusing more on process than product, more on spreadsheets than stories. Ultimately, if my time as a data journalist has taught me anything, it's that the common ingredient in all of the work that I'm most proud of — and, more importantly, that readers have most appreciated — is the quality of using data to help people better understand the issues that matter to them. In this sense, data journalism is no different to any other form of journalism. A good news story makes people aware of something they didn't previously know. A good feature takes something people may already have been superficially aware of, and adds the depth and context that lead to a fuller understanding of the issue. Both of these goals can be achieved with or without data, so for me, the role of data journalism is to discover and communicate the stories and issues that are best found and told with the aid of data.
Journocode: What skills should a data journalist/data journalism team have? What does an ideal team look like?
Specialists in obtaining, analysing and visualising data are all star players in a data journalism team, but I can't stress enough that the single vital ingredient is good ideas. Whether these come from somebody on the data team or elsewhere in the newsroom, the key is that there is one or more person who really gets what a good data story is, and can consistently come up with them. At the FT I'm fortunate to work with a fantastic immediate data team but also some brilliant, data-savvy reporters and correspondents, who understand when data can bring value to a story and — almost as important — when it can't. The time, effort and cost of assembling the most technically and creatively talented team in the world would all be for nothing if they didn't have the stories and features on which to bring their talents to bear.
Journocode: What are the most important tools you use in your work?
Technical skills and tools are a huge advantage, but it is important to understand that they are ultimately force multipliers, expediting or broadening the fundamental process of journalism. To put it another way, a good story told using "only" Google Sheets is better than a weak story told using Node.js, R and d3. To be clear — I'm a fanatical user of R and d3, and wish I was better at writing Node scripts, but the quick hit of self-satisfaction I might get from solving a coding problem or adding a visual flourish is nothing compared to deep sense of fulfilment that comes with using data to leave someone more knowledgeable about the world.
Journocode: Without what can you on no account start working in the morning?
Journocode: How long do you work on average on a project?
Anything from a few hours to a few months!
Journocode: Are you inspired by projects of colleagues from home and abroad? Or do you find your ideas elsewhere?
No idea is created from nothing, and if I really think about it, I probably owe large cheques to dozens of people in journalism and beyond, whose stories, podcasts or casual conversations have sparked — if not delivered wholesale — ideas of my own. I try to read and listen to as much as possible on the topics that I cover, and to bounce ideas off specialists in those fields. Even when it's difficult, obtaining the data is usually the easiest part of data journalism, so I place a huge value on the more qualitative work of developing a deep understanding of the issues that I will then use data to highlight or explain.