In almost a decade of teaching online journalism I repeatedly come up against the same two problems:
- people who are so wedded to the idea of the self-contained ‘story’ that they struggle to create journalism outside of that (e.g. the journalism of linking, liveblogging, updating, explaining, or saying what they don’t know);
- and people stuck in the habit of churning out easy-win articles rather than investing a longer-term effort in something of depth.
Until now I’ve addressed these problems largely through teaching and individual feedback. But for the next 3 months I’ll be trying a new way of organising students that hopes to address those two problems. As always, I thought I’d share it here to see what you think.
Roles in a team: moving from churnalism to depth
Here’s what I’m trying (for context: this is on an undergraduate module at Birmingham City University):
Students are allocated one of 5 roles within a group, investigating a particular public interest question. They investigate that for 6 weeks, at which point they are rotated to a different role and a new investigation (I’m weighing up whether to have some sort of job interview at that point).
The group format allows – I hope – for something interesting to happen: students are not under pressure to deliver ‘stories’, but instead blog about their investigation, as explained below. They are still learning newsgathering techniques, and production techniques, but the team structure makes these explicitly different to those that they would learn elsewhere.
The hope is that it will be much more difficult for them to just transfer print-style stories online, or to reach for he-said/she-said sources to fill the space between ads. With only one story to focus on, students should be forced to engage more, to do deeper and deeper into an issue, and to be more creative in how they communicate what they find out.
(It’s interesting to note that at least one news organisation is attempting something similar with a restructuring late last year)
Only one member of the team is primarily concerned with the story, and that is the editor:
The Editor (ED)
It is the editor’s role to identify what exactly the story is that the team is pursuing, and plan how the resources of the team should be best employed in pursuing that. It will help if they form the story as a hypothesis to be tested by the team gathering evidence – following Mark Lee Hunter’s story based inquiry method (PDF).
Qualities needed and developed by the editor include:
- A nose for a story
- Project management skills
- Newswriting – the ability to communicate a story effectively
The Community Manager (CM)
The community manager’s focus is on the communities affected by the story being pursued. They should be engaging regularly with those communities – contributing to forums, having conversations with members on Twitter; following updates on Facebook; attending real world events; commenting on blogs or photo/video sharing sites, and so on.
They are the two-way channel between that community and the news team: feeding leads from the community to the editor, and taking a lead from the editor in finding contacts from the community (experts, case studies, witnesses).
Qualities needed and developed by the community manager include:
- Interpersonal skills – the ability to listen to and communicate with different people
- A nose for a story
- Contacts in the community
- Social network research skills – the ability to find sources and communities online
The Data Journalist (DJ)
While the community manager is focused on people, the data journalist is focused on documentation: datasets, reports, documents, regulations, and anything that frames the story being pursued.
It is their role to find that documentation – and to make sense of it. This is a key role because stories often come from signs being ignored (data) or regulations being ignored (documents).
Qualities needed and developed by the data journalist include:
- Research skills – advanced online search and use of libraries
- Analysis skills – such as using spreadsheets
- Ability to decipher jargon – often by accessing experts (the CM can help)
The Multimedia Journalist (MMJ)
The multimedia journalist is focused on the sights, sounds and people that bring a story to life. In an investigation, these will typically be the ‘victims’ and the ‘targets’.
They will film interviews with case studies; organise podcasts where various parties play the story out; collect galleries of images to illustrate the reality behind the words.
They will work closely with the CM as their roles can overlap, especially when accessing sources. The difference is that the CM is concerned with a larger quantity of interactions and information; the MM is concerned with quality: much fewer interactions and richer detail.
Qualities needed and developed by the MMJ include:
- Ability to find sources: experts, witnesses, case studies
- Technical skills: composition; filming or recording; editing
- Planning: pre-interviewing, research, booking kit
The Curation Journalist (CJ)
(This was called Network Aggregator in an earlier version of this post) The CJ is the person who keeps the site ticking over while the rest of the team is working on the bigger story.
They publish regular links to related stories around the country. They are also the person who provides the wider context of that story: what else is happening in that field or around that issue; are similar issues arising in other places around the country. Typical content includes backgrounders, explainers, and updates from around the world.
This is the least demanding of the roles, so they should also be available to support other members of the team when required, following up minor leads on related stories. They should not be ‘just linking’, but getting original stories too, particularly by ‘joining the dots’ on information coming in.
Qualities needed and developed by the CJ include:
- Information management – following as many feeds, newsletters and other relevant soures of information
- Wide range of contacts – speaking to the usual suspects regularly to get a feel for the pulse of the issue/sector
- Ability to turn around copy quickly
And here’s a post on ‘How to be a curation editor‘.
Examples of network aggregation in action:
- Blogs like Created In Birmingham regularly round up the latest links to events and other reports in their field. See also The Guardian’s PDA Newsbucket.
- John Grayson’s post on G4S uses a topical issue as the angle into a detailed backgrounder on the company with copious links to charity reports, politicians’ statements, articles in the media, research projects, and more.
- This post by Diary of a Benefit Scrounger is the most creative and powerful example I’ve yet seen. It combines dozens of links to stories of treatment of benefit claimants and protestors, and to detail on various welfare schemes, to compile a first-person ‘story’.
Publish regular pieces that come together in a larger story
If this works, I’m hoping students will produce different types of content on their way to that ‘big story’, as follows:
- Linkblogging – simple posts that link to related articles elsewhere with a key quote (rather than wasting resources rewriting them)
- Profiles of key community members
- Backgrounders and explainers on key issues
- Interviews with experts, case studies and witnesses, published individually first, then edited together later
- Aggregation and curation – pulling together a gallery of images, for example; or key tweets on an issue; or key facts on a particular area (who, what, where, when, how); or rounding up an event or discussion
- Datablogging – finding and publishing key datasets and documents and translating them/pulling out key points for a wider audience.
- The story so far – taking users on a journey of what facts have been discovered, and what remains to be done.
You can read more on the expectations of each role in this document. And there’s a diagram indicating how group members might interact at the top of this article.
What will make the difference is how disciplined the editor is in ensuring that their team keeps moving towards the ultimate aim, and that they can combine the different parts into a significant whole.
UPDATE: A commenter has asked about the end result. Here’s how it’s explained to students:
“At an identified point, the Editor will need to organise his or her team to bring those ingredients into that bigger story – and it may be told in different ways, for example:
- A longform text narrative with links to the source material and embedded multimedia
- An edited multimedia package with links to source material in the accompanying description
- A map made with Google Maps, Fusion Tables or another tool, where pins include images or video, and links to each story”
If you’ve any suggestions or experiences on how this might work better, I’d very much welcome them.