Designing newsrooms for digital: No more silos, try pods

NOTE: This post was written by Knight Lab student fellow Katie Zhu for the AP-Google Journalism and Technology Scholars blog series, and originally appeared on Online News Association's AP Google blog.

As a programmer-journalist studying journalism/computer science, I’ve found myself at the “intersection of journalism and technology” or in the emerging field of computational journalism.

I used to think the technical stuff was the hard part. I spent my time trying to grasp scope in JavaScript, scraping webpages or learning the MVC framework of the week. But here’s the thing — programming? That’s actually the easy part. (N.B.: That’s not to say it’s trivial.)

The real issue: How do we use these tools (see: robots) to tell better stories and present information in a correct yet impactful way? How do we leverage machines to do better journalism?

I’ve learned not to get so caught up in the technical flashy stuff that I lose sight of this overarching goal. And that’s why I say programming is the easy part. What good does it do to code a flashy display of charts/figures/data/tables/insert buzzword here if it’s not doing the story justice?

And that’s why I’d like to talk a bit about silos and pods.

Not the grain container or storage solution, but the metaphorical structures they represent — silos as separate, rather isolated groups and pods containing a mix of these groups.

Silos: Why they don’t work

Consider the genesis of a story. Starts with a pitch. Maybe a crime beat reporter wants to do a particularly compelling story on the prevalence of teen violence, prompted by a few individual anecdotes. This has data potential, too. Anecdotes are great on a micro-level, but more broadly, is this part of some nationwide trend? The numbers can tell us the answer to that question. But data and thinking statistically, numerically, needs to happen at the beginning. If it becomes an afterthought, then it’s too late.

Moreover, let’s pretend that reporter didn’t come up with this story. Let’s say we had a script that scraped crime data and pumped it into a spreadsheet, and a data journalist drew up a quick chart to see if there was a story in the numbers. Maybe the stats tell us that the mean age of homicides in the last month has decreased by 50 percent, and we decide to run with that story.

A newsroom typically contains reporters, editors, data journalists, developers, designers … the list goes on. But traditionally they work in separate departments, unable to seamlessly collaborate together. That’s why silos don’t work. Instead, there should be a horizontal of these newsroom archetypes to truly integrate the journalism with the tech.

In my LedeHub work (as part of my AP-Google scholarship), I’ve been playing with the idea of version control for journalism. One question I’ve been struggling with is this: How do you support a process that allows cross-disciplinary teams to combine contributions and work in parallel?

Journalists can learn a lot from programmers. Namely, how to make machines do the grunt work and automate tasks. But there should be a feedback loop here, because programmers must also learn from reporters. Deep beat knowledge, how to find and talk to the right people to suss out a great story, these are critical to being able to do good journalism.

So we need to bridge the gap, because we’re all on the same J-team. It’s about information. It’s about the story.

Pods: Why they work

So instead of silos, I’m proposing newsroom pods.

Think of a pod as a horizontal slice of the varying newsroom archetypes. Ideally, a pod would consist of a reporter, data whiz, developer, designer and editor, resources permitting.

But there’s no need to be overly prescriptive here. What I’m really trying to get at is the integration across disciplines that this model affords. I’m not saying we should throw beats and desks out the window, but introduce some pods to make it easy for the story and the technology to meet.

The benefit of having a beat reporter’s intimate knowledge and expertise in a given topic area is invaluable. A developer helping journalists clean up messy government data sets is also pretty useful. There should be cross-pollination between the reporters and the news developers. I firmly believe that this is a pivotal step to producing great journalism.

So, how do we do it?

Newsroom geography is a good place to start. The news applications teams at the Chicago Tribune and ProPublica sit in the center of the newsroom. Plus-one for visibility. ProPublica’s news applications developers are highly embedded in the reporting process and work closely with editors and reporters throughout the entire story process.

The task of designing digital newsrooms is not a new concept. Various factors — audience, platform, brand, goals — play into building a newsroom and ecosystem that works for a specific publication, and I recognize that there is no “one size fits all” solution. But pods do exist.

The BBC’s redesigned newsroom layout also exemplifies that organization’s recognition of the need for integrated spaces. Integration helps ease information sharing and, in turn, collaboration. Steve Herrmann, editor for BBC News Online, emphasized that in the new floor plan, global and UK journalists all sit in the same space. I think the same must be done for news applications teams.

In today’s online news world, people have talked about unicorns. You could try your luck at breeding them, but in the meantime, we should work with what we have. People are awesome at what they do. Reporters cover beats like nobody’s business. Programming is often cited as an aggregate skill, but within that, developers have different specialties, too (at the most basic level, front end vs. back end). Throwing all these roles into a pod results in breadth and depth, and just might just help us do some better journalism.

This is one in a series of blog posts from the first ONA class of AP-Google Journalism and Technology Scholars describing their experiences, projects and sharing their knowledge with the ONA community.

Katie Zhu is a junior at Northwestern University, working on LedeHub, a project for collaborative, open journalism.

End repost from Online News Association’s AP Google blog series

About the author

Katie Zhu

Undergraduate Fellow

Latest Posts

  • Building a Community for VR and AR Storytelling

    In 2016 we founded the Device Lab to provide a hub for the exploration of AR/VR storytelling on campus. In addition to providing access to these technologies for Medill and the wider Northwestern community, we’ve also pursued a wide variety of research and experimental content development projects. We’ve built WebVR timelines of feminist history and looked into the inner workings of ambisonic audio. We’ve built virtual coral reefs and prototyped an AR experience setting interviews...

    Continue Reading

  • A Brief Introduction to NewsgamesCan video games be used to tell the news?

    When the Financial Times released The Uber Game in 2017, the game immediately gained widespread popularity with more than 360,000 visits, rising up the ranks as the paper’s most popular interactive piece of the year. David Blood, the game’s lead developer, said that the average time spent on the page was about 20 minutes, which was substantially longer than what most Financial Times interactives tend to receive, according to Blood. The Uber Game was so successful that the Financial...

    Continue Reading

  • 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

  • Audience Engagement and Onboarding with Hearken Auditing the News Resurrecting History for VR Civic Engagement with City Bureau Automated Fact Checking Conversational Interface for News Creative Co-Author Crowdsourcing for Journalism Environmental Reporting with Sensors Augmented Reality Visualizations Exploring Data Visualization in VR Fact Flow Storytelling with GIFs Historical Census Data Information Spaces in AR/VR Contrasting Forms Of Interactive 3D Storytelling Interactive Audio Juxtapose Legislator Tracker Storytelling with Augmented Reality Music Magazine Navigating Virtual Reality Open Data Reporter Oscillations Personalize My Story Photo Bingo Photojournalism in 3D for VR and Beyond Podcast Discoverability Privacy Mirror Projection Mapping ProPublica Illinois Rethinking Election Coverage SensorGrid API and Dashboard Sidebar Smarter News Exploring Software Defined Radio Story for You Storyline: Charts that tell stories. Storytelling Layers on 360 Video Talking to Data Visual Recipes Watch Me Work Writing and Designing for Chatbots
  • 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

Storytelling Tools

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

View More