Tumblelog by Soup.io
Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.

March 28 2012


Best Practices for Collaborative Investigative Reporting

My first professional job out of college was surprisingly relevant to what I've been doing of late. I started as a program analyst at the Department of Health and Human Services' Office of Inspector General in the Office of Evaluation and Inspections. In federal government parlance, that would be the OEI in the OIG at DHHS.

Our mandate was to identify "fraud, waste and abuse" within the department's programs. With unfettered access to vast data sets, we conducted national studies to evaluate various regulations and the ways they were being applied. We were data reporters without my knowing what a data reporter was. It was a lot like investigative journalism, but with bigger budgets and a dress code. It was also a lot like identifying best practices for collaborative investigative reporting.

"Best practices" is a highfalutin' term we used in our proposal to the Knight Foundation just as our office, the Investigative Reporting Program at U.C. Berkeley's Graduate School of Journalism (IRP), was about to launch into "Post Mortem," a collaboration about death investigation in America with PBS Frontline, ProPublica and NPR. In retrospect, "blueprint" would have been a better term to use than "best practices," since we all know that there's rarely one draft of a blueprint.

Documenting Collaboration

When "Post Mortem" launched in the spring of 2010, the combination of partners -- national public television, national public radio and a nonprofit digital publication -- was a first, to the best of my knowledge, and we guessed we'd learn much from this ambitious undertaking. When I've described the project to other editors and reporters over the last year, some have voiced skepticism about how "Post Mortem" reflects other collaborations cropping up around the country. Of course Frontline, NPR and ProPublica can pull off a collaboration like "Post Mortem," the skeptics have said, but how does that experience relate to media organizations collaborating at the state or local level?

The answer is that while investigative collaborations vary, a number of decisions and sticking points remain constant, regardless of the organizations involved.

We learned, for example, that collaboration impacts each phase of the reporting process -- from planning and reporting to publication; sometimes the impact of collaboration is obvious, sometimes not. Our Knight Foundation funding provided for an embedded reporter (me) to cover the collaboration; this was an evaluator's dream, giving us the ability to document the process as it unfolded. After all, if you're a journalist in the midst of a collaboration, your goal is not to understand or refine the process of collaborating -- it's to report and publish or broadcast your story. (Though, based on my experience with "Post Mortem," I'd recommend that those spearheading journalistic collaborations do take the time to document the process to some extent, because the unexpected always happens, and there are good lessons in the unexpected.)

Lessons in the Unexpected

In "Post Mortem" there were plenty of revelations. Everyone involved in the project had a basic understanding of television, radio and the web. But when you report for multiple platforms simultaneously, each medium's differences rise to the surface. It was challenging, for example, to get the project's television correspondent to ask questions of subjects that would evoke answers that translated well for both television and radio.

Other challenges were fairly straightforward, like figuring out how to describe the collaboration within the PBS Frontline documentary. NPR and ProPublica reporters weren't on camera, so how could we introduce them in a visual medium?FL_PM.jpg We also couldn't anticipate the possibility that an event like the Arab Spring would bump an NPR "Post Mortem" story for good.

The best practices (PDF) that we at the IRP have drafted are drawn from our own lessons learned, as well as input from others in the field who've tackled collaborative work. Many of the document's observations come straight from the mouths of the "Post Mortem" collaborators, whom I interviewed during and after the project. It's all good stuff, but the ultimate value of these best practices will be if we view them as a collaborative, open-source document: a starting point for more formalized and smoother collaborating.

The Non-Negotiables

Here are a few of the lessons included in our best practices that I think are especially worthy of emphasis:

  • Plan, plan, plan. You can read my recent post about planning on Collaboration Central. I'll say it again. Plan.
  • Take the time to understand your partner's requirements: What do they need to produce the best possible stories for their media? Where might there be conflicting needs, and how can those conflicts be addressed?
  • Understand your partners' organizational culture and structure. This will help throughout the process and at least offer some insight into burning questions like: Why can't they commit to a publication date? Can we get something in writing? And how much time do we need for the editorial process?
  • Finally, whether you're collaborating with other media outfits or working within your own newsroom, a focus on teamwork and leadership skills is imperative to fostering a culture that can sustain collaborative work; without it, people will burn out and collaboration will falter. Journalism professors Jonathan Groves and Carrie Brown-Smith wrote in a recent Neiman Journalism Lab article: "Changing a culture is not a top-down or bottom-up proposition: It's a dance between leaders and their organizations." I couldn't agree more. Let's dance.

Take a look at the best practices (PDF) we wrote and share your tips, thoughts and ideas about working collectively.

Carrie Lozano is a Bay-Area based journalist and documentary filmmaker. She is currently the project director for "Collective Work" a Knight-funded project about collaborative, multiplatform investigative reporting at the Investigative Reporting Program, UC Berkeley Graduate School of Journalism. She is also directing and producing a documentary film with Charlotte Lagarde about jazz pianist and composer Fred Hersch. You can follow her at @carrielozano or reach her at clozano at berkeley.edu.

"Collective Work" is funded by the John S. and James L. Knight Foundation. Copyright 2012, The University of California at Berkeley.

This is a summary. Visit our site for the full post ».

February 28 2012


What Is Collaboration Anyway?

Journalists, by nature, tend to be fiercely competitive, racing to break the news before their rivals. Given that tendency, anyone who's engaged in a journalism collaboration knows that it's an extraordinary endeavor. That's why it's worth stepping back and identifying what we really mean when we say we're collaborating.

At the Investigative Reporting Program at UC Berkeley's Graduate School of Journalism, we've spent the last 18 months focused on that very question in our project Collective Work, which is developing best practices and other resources to help support and encourage collaborative investigative reporting.

When we began the project, little had been written about the subject (there's been much more attention since), so we began interviewing multiplatform editors, reporters and educators about the fast-emerging trend. To date, we've talked to more than 50 industry professionals who've made clear that collaboration means different things to different organizations and experts. Often, what's dubbed collaboration is actually something else, like crowdsourcing, syndication, aggregation or even sharing.

Collaboration as a category of convenience is notable, even in the realm of media jargon. But it's understandable. Unlike more abstract terms -- synergy, convergence, transmedia -- it conveys something new, positive, concrete and universally understood. As the antithesis of competition, it's a not so subtle way of saying: "We're doing something new!"

But from the perspective of building strong business models and infrastructures that support collaborative endeavors, making a distinction matters.

Towards a standard definition

So what does collaboration really mean?

The definition that my colleagues and I have adopted emerged from Collective Work's primary case study: the Investigative Reporting Program's collaboration with PBS Frontline, ProPublica and NPR for the series "Post Mortem," an ongoing in-depth look at death investigation in America, which I described in an earlier post. Based on that experience and our previous partnerships, we are focusing on projects where reporters, editors and producers from different news organizations work as a team to produce and publish original, in-depth, multiplatform stories.

This definition reflects what we think is truly groundbreaking about collaborative efforts and points to an area of reporting that has both untapped potential and plenty of kinks to work out. While collaboration itself doesn't solve the question of how to pay for the reporting, it does put more resources toward a story, resulting in more (often better) coverage that reaches wider audiences than one organization could manage on its own.

Focus on the fundamentals

The benefits may be obvious, but there's a lot to learn about this new way of working. The reality is that the evolving media landscape, limited resources and fast-breaking nature of news don't always allow for methodical planning, processes, training or staffing. Collaboration, in particular, doesn't operate with the same workflow efficiencies that are the hallmark of getting daily newspapers on the newsstand.

Ulrich Nettesheim.jpg

Not to mention that transitioning from a competition-based, solitary work culture to a more open and team-oriented one doesn't happen with ease, which is why we sought the insight of Ulrich Nettesheim, an organizational psychologist, executive consultant and lecturer on leadership and high-performance teams at UC Berkeley's Haas School of Business.

According to Nettesheim, we journalists are not alone in the march toward collaborative work. Technical disciplines, such as business, science and journalism, are becoming increasingly interdisciplinary, and a premium is placed on teamwork.

"Part of the world of work means that you have to be able to be a member of and lead teams," explained Nettesheim. "That's a skill set that's no longer optional or nice to do. It's a requirement."

Like assumptions about collaboration, understanding the concept of "team" seems a no-brainer. But from an organizational perspective, Nettesheim emphasized that teamwork has a specific meaning: It requires shared goals, high interdependency of tasks, and strong relationships.

Hearing this gave me a framework for understanding the breakdowns in collaboration that I had both witnessed and heard about. It also clarified why collaboration is not an accurate description for many media partnerships.

Nettesheim helped me discern that what journalists often refer to as collaborations are actually transactions. Transactions between media organizations don't require the same relationships or interdependency that collaborations do.

ca-watch.jpgTo understand the distinction, California Watch is a good case study. Associate editor Denise Zapata explained that part of its model is to allow partners to regionalize statewide stories, either by mining data that California Watch provides or reframing a story with a localized angle. While the process may require some back-and-forth, it's largely a systematized transaction. But when California Watch recently pooled money with partners to send a reporter to Spain for a story that they all shared, that was a collaboration.

Given the industry's quest for sustainability, and the desire among forward-thinking journalists to institutionalize collaboration, correctly identifying and naming transactions would be a helpful business strategy. After all, transactions are potential revenue streams, which makes them easy to justify.

Leadership is needed

With an understanding of what it entails, what can we do to ensure that collaboration survives? Nettesheim emphasized the importance of things like team charters, acknowledging strengths and weaknesses (at the individual and organizational level) and making a commitment to give and receive feedback.

It was heartening to hear. It confirmed that if we look beyond our own industry for collaborative modeling, there are promising solutions to what can make the process inefficient, frustrating and an easy target for editors who haven't quite bought in.

But all of this will only happen with strong, vocal leaders who are open to reflection and understanding the dynamics of teamwork. With all the hats that editors and news executives currently wear, it seems like a difficult, if not impossible, task. So when I asked Nettesheim how media organizations could develop and nurture leadership skills, I was relieved that he hedged on a precise formula and instead gave a digestible example.

"The single best definition of leadership I learned from coach Jack Clark," he explained, referring to UC Berkeley's rugby coach whose team has won 22 championships since 1984.

"It's simple and powerful. 'Make those around you better.'"

As journalists try to make journalism better, Collaboration Central wants to hear from you. How do you define collaboration?

Carrie Lozano is a Bay-Area based journalist and documentary filmmaker. She is currently the project director for "Collective Work" a Knight-funded project about collaborative, multiplatform investigative reporting at the Investigative Reporting Program, UC Berkeley Graduate School of Journalism. She is also directing and producing a documentary film with Charlotte Lagarde about jazz pianist and composer Fred Hersch.

Collective Work is funded by the John S. and James L. Knight Foundation. Copyright 2012, The University of California at Berkeley.

This is a summary. Visit our site for the full post ».

Older posts are this way If this message doesn't go away, click anywhere on the page to continue loading posts.
Could not load more posts
Maybe Soup is currently being updated? I'll try again automatically in a few seconds...
Just a second, loading more posts...
You've reached the end.

Don't be the product, buy the product!