Want to build a data journalism team? You'll need these three people

When I started using software to analyze data as a reporter in the late 1980s, "data journalism" ended once my stories were published in the newspaper.

Now the publication of the story is just the beginning. The same data can also be turned into compelling visualizations and into news applications that people can use long after the story is published. So data journalism — which was mostly a one-person job when I started doing it — is now a team sport.

So if you're running a news organization that wants to start doing data journalism, how should you proceed? At the American Society of News Editors conference last week in Washington, I argued that news leaders need to think about three dimensions of data journalism -- and three different types of journalism skills. Here's the graphic I showed them:

venn-3-dimensions-of-data-journalism

The point of the diagram is that to do data journalism well, a news organization needs to employ people with three discrete sets of skills. The numbered areas on the graphic represent people or jobs that blend more than one of these skills, and it's certainly great when a news organization can find someone who can do more than one thing well. But typically, the skills involved in data journalism will be found in at least three different people.

Here's what I think are the three dimensions of data journalism:

  • Computer-assisted reporter: These journalists typically start as news reporters and develop expertise in obtaining, analyzing and finding newsworthy angles in data. (When this discipline emerged in the late 1980s, journalists called it "computer-assisted reporting," a term that is still commonly used.) These journalists have a "data state of mind" for reporting and know how to query (or interview) data to discover the most interesting and relevant findings. They typically use spreadsheets, database and mapping software, but many are now also acquiring programming skills so they can simplify some of their work -- for instance, writing scrapers that pull down data from websites that don't offer API's or data downloads.
  • News applications developer: These are the newest data journalists to arrive in newsrooms, either moving from careers in computer programming or learning programming skills as part of their journalistic work. Their job is to figure out how best to make data available to users online. They have hands-on skills in back-end programming, database configuration and administration, as well as HTML, CSS and JavaScript so they can build the interface to their applications.
  • Data visualization specialist: Historically news organizations had graphic artists whose job was to create static graphics that illustrated data-driven (and other) stories. As graphic artists did when they created static graphics, data visualization specialists understand how to present data in interesting and accessible ways, and they understand the principles of good information design. But since graphics on the Web can be clickable and interactive, these journalists increasingly do front-end programming and make use of open-source Javascript libraries such as D3.


All of these disciplines have historic roots in news organizations. The computer-assisted reporter worked on the city desk, the news applications developer was probably a programmer for the company's business operations, and the data visualization specialist was a graphic artist. As their jobs have evolved, though, they all increasingly need programming skills.

News organizations seeking to fill these roles are finding it difficult. Quite simply, there is more demand for people with these skills -- both inside and outside of journalism -- than there are people qualified to fill them. At the ASNE panel, "Data Journalism: The Myths and the Magic," I argued that news organizations need to take a long-term view and "grow your own talent." This means identifying current staff members with potential to develop these skills and recruiting promising college students who can build their skills as interns or part-time employees.

Among current staff members, potential computer-assisted reporters can be identified by their use of spreadsheet or database software in their work, their comfort with math and data, and the way they use numbers effectively in their stories. Potential news applications developers might be working in a news organization's IT department, but can be identified by their interest in journalism, their participation in "open government" initiatives and their use of contemporary programing languages such as Ruby and Python. And potential data visualization specialists can be identified by their interest in working on data-intensive graphics, their comfort with math and data and possibly some prior experience with mapping applications or JavaScript.

The kind of people who do data journalism are, of course, the core audience for the Knight Lab blog. Do you see yourself in this graphic? Are you a computer-assisted reporter, a news applications developer or a data visualization specialist? Or maybe you fit into one of the numbered areas where these skill sets overlap? Let us know in the comments below — or on Twitter mentioning @knightlab and the hashtag "#datadimensions."

About the author

Rich Gordon

Professor and Director of Digital Innovation

Journalism/tech intersection, my passion for 25 years, data journalism, Miami Herald web director, now hacker journalism.

Latest Posts

  • With the 25th CAR Conference upon us, let’s recall the first oneWhen the Web was young, data journalism pioneers gathered in Raleigh

    For a few days in October 1993, if you were interested in journalism and technology, Raleigh, North Carolina was the place you had to be. The first Computer-Assisted Reporting Conference offered by Investigative Reporters & Editors brought more than 400 journalists to Raleigh for 3½ days of panels, demos and hands-on lessons in how to use computers to find stories in data. That seminal event will be commemorated this week at the 25th CAR Conference, which...

    Continue Reading

  • Prototyping Augmented Reality

    Something that really frustrates me is that, while I’m excited about the potential AR has for storytelling, I don’t feel like I have really great AR experiences that I can point people to. We know that AR is great for taking a selfie with a Pikachu and it’s pretty good at measuring spaces (as long as your room is really well lit and your phone is fully charged) but beyond that, we’re really still figuring...

    Continue Reading

  • Capturing the Soundfield: Recording Ambisonics for VR

    When building experiences in virtual reality we’re confronted with the challenge of mimicking how sounds hit us in the real world from all directions. One useful tool for us to attempt this mimicry is called a soundfield microphone. We tested one of these microphones to explore how audio plays into building immersive experiences for virtual reality. Approaching ambisonics with the soundfield microphone has become popular in development for VR particularly for 360 videos. With it,...

    Continue Reading

  • Prototyping Spatial Audio for Movement Art

    One of Oscillations’ technical goals for this quarter’s Knight Lab Studio class was an exploration of spatial audio. Spatial audio is sound that exists in three dimensions. It is a perfect complement to 360 video, because sound sources can be localized to certain parts of the video. Oscillations is especially interested in using spatial audio to enhance the neuroscientific principles of audiovisual synchrony that they aim to emphasize in their productions. Existing work in spatial......

    Continue Reading

  • Oscillations Audience Engagement Research Findings

    During the Winter 2018 quarter, the Oscillations Knight Lab team was tasked in exploring the question: what constitutes an engaging live movement arts performance for audiences? Oscillations’ Chief Technology Officer, Ilya Fomin, told the team at quarter’s start that the startup aims to create performing arts experiences that are “better than reality.” In response, our team spent the quarter seeking to understand what is reality with qualitative research. Three members of the team interviewed more......

    Continue Reading

  • How to translate live-spoken human words into computer “truth”

    Our Knight Lab team spent three months in Winter 2018 exploring how to combine various technologies to capture, interpret, and fact check live broadcasts from television news stations, using Amazon’s Alexa personal assistant device as a low-friction way to initiate the process. The ultimate goal was to build an Alexa skill that could be its own form of live, automated fact-checking: cross-referencing a statement from a politician or otherwise newsworthy figure against previously fact-checked statements......

    Continue Reading

Storytelling Tools

We build easy-to-use tools that can help you tell better stories.

View More