Context: One thing that liveblogs can’t do at the moment

Liveblogging is still a nascent writing style. There have been several discussions about its value. You can debate for days about whether or not it’s appropriate for everything, or whether covering something through process journalism is always the right decision, but liveblogging is a form of storytelling that’s here to stay.

To me the humdinger that almost every single liveblog that I’ve come across has failed to address is the issue of context.

When talking to people about Ocqur, one of the most common pieces of feedback was not being able to properly understand what had been going on in a liveblog if joining the story or event part of the way through.

This is a problem for two reasons.

First, viewers are likely to spend several minutes trying to work out what happened and when before getting back to the latest updates, which is a poor reading experience.

The second reason is a byproduct of the first, in that as long as this problem keeps occuring and readers still view it as an issue, it’s going to put people off the liveblog experience.

There’s a reason why things like Longform and Readability have done so well – because they enshrine and bring out the simplicity that long form reading used to be before we were assailed by a horde of feeds, links and social networks. Right now it doesn’t seem like the frontend of many liveblogs seem to treat their readers in the same way.

So how can it be done better?

News organisations like the Guardian, the Times and the New York Times have it easier than most in this respect, simply because they have access to thousands of articles, hundreds of tags and topic pages, video content, photo archives, commentary and analysis. This alone should make the task of contextualising liveblogs a lot simpler for them than a standalone service like Cover It Live or Scribble Live.

In fact, the New York Times already seem to be halfway there. Take a look at this screenshot of their Facebook IPO liveblog.

The right column displays a graph tracking the stock price, with major shareholders listed below and a pane offering videos, interactives and documents. The NYT come closer than any other organisation to offering a full contextual experience alongside their liveblog.

So for us at Ocqur, this is potentially the toughest nut to crack. Feature requests are small fry – we can build multiple authors, we can give you more options for embedding, and we can add permalinks for individual entries.

But when it comes to context, how do we interpret that? It’s potentially a very abstract and subjective concept. One man’s article is another man’s YouTube video, and it’s very difficult to tell how everyone reads stories when they’re being played out live.

I think the solution lies in, ironically, looking at how ‘old’ media cover things like elections. Take the BBC’s 2010 general election coverage. The main coverage consisted of rolling news in the vein that we’re used to seeing from the BBC news channel and Sky News, with reporters from various counting halls around the country occasionally doing a piece to camera and reporting the local result. This is the broadcast equivalent of the liveblog, with the liveblog author taking the place of the program producer.

Between these results, the BBC would come back to the studio, which featured Jeremy Paxman, David Dimbleby, Emily Maitlis et al filling in viewers on the bigger picture. “Here’s the result” said the journalist in the counting hall, “and this is what it means” said the presenter in the studio.

The problem with this analogy is that we don’t seem to have found our presenters yet in liveblogging. There isn’t much contextualisation of the river of information that’s flowing through a liveblog, and it’s one of our main challenges in the ongoing development of Ocqur. @socialtechno has pointed out some excellent processes on how to address this in the comments.

As mentioned in my last post, we’ll be working with our testers in the next couple of months in order to really draw out and establish what it means to have a liveblog that truly allows the reader to stay up to date as well as understand the key issues quickly.

Post comment as twitter logo facebook logo
Sort: Newest | Oldest
socialtechno 7 pts

That's a very succinct summary of the challenge. I think there are three distinct things missing. First, any live blog needs a 'new readers start here'  summary, the sort of thing Twitter does badly when it tries to explain a hashtag, and  Wikipedia does well with the first paragraph of its articles. You did a good live blog on the Breivik shootings, but I was very confused by the question of how a bomb going off in Oslo turned into a lone sniper shooing people on an island. It took me a long time to work it out.

 

The second thing, which i think is a bit easier, is to provide support for returning readers to catch up. I've said before, I want a view that lets me put the oldest at the top, newest at the bottom, and I also want a cookie to remember where I stopped reading on my last visit.

 

A third element of context is what's important - what are the key developments? This partly overlaps with the first point, and I think it works well with crowdsourcing and tagging.   Let people tag a line in the flow as significant (the Milly Dowler hack, the Robben penalty save) and let people vote them up and down, not as 'likes' (sentiment) but 'key' (significance).  Then give me a view that allows me to filter the whole live blog based on other readers' significance ranking.

 

If you have that function in place, you can (optionally) have your 'presenter in the studio' curating their own ranking of significant events. The default 'new readers start here' context could be the list of 'events ranked significant by our editor'. And if you wanted to be really clever, you could be partisan (show me only things rated significant by Labour supporters, by Chelsea fans, etc)

 

So the data manipulation functions that help the reader establish context are:

 

a) Sequence (oldest-first OR newest-first)

b) Zoom to (start, newest, where I logged off, to significant event)

c) Filter (everything, things rated significant by curator, things rated by readers)

 

 

 

 

JosephStash 15 pts moderator

 socialtechno This is spot on, I think I'll point to this comment in the post now. I'll be blogging about this issue again soon when we start building on what we've already got for Ocqur and start addressing some of these issues.