Miscellany: SAI, Crooked Timber, MediaBugs and “Inception”

Part Three of “In Defense of Links” coming later this week! Some little stuff in between:

  • I have begun an experiment in crossposting some of my stuff over at Silicon Alley Insider/Business Insider. Same writing, grabbier headlines! As it is, my posts appear here, and then also at Open Salon (where Salon sometimes picks them up). And I pipe them into Facebook for my friends who hang out there. The folks at SAI have picked up some of my pieces before, and I’m curious about how my point of view goes over with this somewhat different crowd.
  • Henry Farrell was kind enough to post a bit about In Defense of Links over at the Crooked Timber blog, and the discussion in comments there is just humblingly good — as well as entertaining. Would every single person who has ever issued a blanket putdown of the worthlessness of blog comments please pay this estimable community of online scholars a visit, and then pipe down? Thank you.
  • Just in time for the release of his new novel, Zero History, William Gibson has a great op-ed in the Times:

    Jeremy Bentham’s Panopticon prison design is a perennial metaphor in discussions of digital surveillance and data mining, but it doesn’t really suit an entity like Google. Bentham’s all-seeing eye looks down from a central viewpoint, the gaze of a Victorian warder. In Google, we are at once the surveilled and the individual retinal cells of the surveillant, however many millions of us, constantly if unconsciously participatory.

    In the ’90s I had the pleasure of interviewing Gibson a couple of times — here’s the 1994 edition, in which we discussed why the technology in his early novels never breaks down, and here’s part of the 1996 one, where he talks about building his first website and predicts the rise of people who “presurf” the Web for you.

    I recently caught up with Inception, and was amazed at how shot-through it is with Gibsonisms. Inception is to Neuromancer as The Matrix was to Philip K. Dick’s worlds: an adapation in everything but formal reality.


 

Bloomberg: a scarlet-letter correction policy?

One of the things we’re trying to accomplish with MediaBugs is to encourage a change in newsroom culture. Journalists are still often reluctant to admit error, or even discuss the possibility of a mistake, for fear that it undermines their authority. But today a growing number of them understand that accuracy is best served, and authority best preserved, by being more open about the correction process.

That is the attitude we’ve encountered at most of the Bay Area news institutions where we’ve demoed MediaBugs. Unfortunately, it’s not what we found at Bloomberg when we tried to obtain a response on behalf of blogger Josh Nelson, who’d filed an error report at MediaBugs about a Bloomberg story.

Nelson raised a specific and credible criticism about the headline and lead on a Bloomberg report based on a national poll. Bloomberg’s coverage, Nelson argued, didn’t accurately reflect the actual question that its pollsters had asked about the Obama administration’s ban on deepwater oil drilling in the Gulf. (The story and headline said that “Most Americans oppose President Barack Obama’s ban” on such drilling, but the poll asked about a general ban on all Gulf drilling, while Obama has placed a temporary hold on deepwater drilling.) Bloomberg, as we described recently, circled the wagons in response.

The news service, of course, has every right to “stand by its story.” But since Nelson has raised a reasonable question, Bloomberg’s public deserves a reasonable response. It would be useful for its readers — and its colleagues at publications like the San Francisco Chronicle, which reprinted the story — to hear from the editors why they disagree with Nelson. Apparently they believe their copy accurately reflects the poll they took, but they have yet to offer a substantive case explaining why.

Institutional behavior of this kind always leaves me scratching my head. A comment posted on our previous post on the Bloomberg bug over at the PBS MediaShift Idea Lab proposed an intriguing theory: A former Bloomberg journalist suggested that the company’s personnel policies came down so hard on employees who made errors that they were reluctant to admit them at all.

These standards, which are meant to make people super-careful before publishing a story, actually serve as a perverse incentive and cause people at all levels of the newsroom to resist correcting stories after they are published if there is any way to justify leaving the story as is.

This was, we thought, worth a follow-up, and so we contacted the commenter. He turned out to be Steven Bodzin, who’d worked as a reporter in San Francisco and Venezuela for Bloomberg for four years before leaving the company in March. My colleague Mark Follman spoke at length with Bodzin last week.

Bodzin said he “rarely saw complaints from the public get ignored.” He told us that Bloomberg’s culture is actually “hypersensitive” to public response but especially focused on issues raised by sources or by customers who subscribe to its terminal service (Bloomberg’s business was built on selling real-time market data to the financial industry over its own network — only later did it begin distributing news and information on public networks).

Bodzin described his own “prolific” first year as a Bloomberg correspondent, during which five of his stories were cited as exemplary in the company’s weekly internal reviews. He also had an unusually high number of corrections that year — which he attributed to the intense pace of the job — and got the message from his superiors that “you really have to bring that down.” He says that made him more careful. But he observed that the stigma that Bloomberg attached to corrections also encouraged a sort of silence in the newsroom in the face of potential problems.

Certainly there were situations where you realize something is wrong but you’re gonna say “I didn’t see that” or just forget about it.
At Bloomberg that’s considered a really serious offense … but at the same time, if you or nobody else mentions it … no harm no foul. I think it happens. One time a colleague of mine, who’d already had one correction that day, saw one and said to me: “I am Olympically burying this error.”

We asked Bodzin about the specific issue Josh Nelson raised about the drilling-ban poll.

They see this case as a question of interpretation, a judgment call — this is their own poll, a lot of reporters and editors are involved, so they [would all] get a correction. So they aren’t going to want to do it.

What we’re looking at here isn’t some revelation of blatantly irresponsible behavior but a subtler insight into the complex interplay of motivation inside a big organization. Bloomberg is hardly the only company where such a dynamic may be at work. What’s important is that the people who lead such institutions understand the need to change the dynamic — to rebalance the incentives inside their newsrooms.

Unfortunately, this incident suggests that Bloomberg’s culture today clings to the wagon-circling habit. As so much of the rest of the journalism field moves toward more open models, it remains an old-fashioned black-hole newsroom, happy to pump stories out to the world but unwilling to engage with that world when outsiders toss concerns back in. Bodzin explained, “Staffers aren’t supposed to talk to press at all — you’re supposed to send reporters to the PR department.”

And that’s exactly what we found when we tried to get comment from Bloomberg about the issues Bodzin raised. When we asked senior editors at Bloomberg to discuss their own policies and newsroom culture, they shunted us over to Ty Trippet, director of public relations for Bloomberg News, who wrote back:

Our policy is simple: If any Bloomberg News journalist is found to be hiding a mistake and is not transparent about it, their employment with Bloomberg is terminated.

So Bloomberg looks at a nuanced psychological question of newsroom behavior and responds with an “Apocalypse-Now”-style “terminate with extreme prejudice.” Doesn’t exactly give you confidence about the company’s ability to foster a culture of openness around the correction process.

Earlier this week Bloomberg announced the hire of Clark Hoyt — the Knight Ridder veteran who for the last three years served as the New York Times’ public editor. In that ombudsman-style role he served as a channel for public concerns about just the sort of issues we are raising here about Bloomberg.

Though Hoyt’s new management job at Bloomberg’s Washington bureau isn’t a public-editor role, it does put him squarely in the chain of command for stories like the oil-drilling poll. So maybe he’ll look into this, and also more generally at how Bloomberg handles public response to questions of accuracy. Right now, the company’s stance is one that hurts its reputation.


 

Change is good, but show your work: Here’s a WordPress revisions plugin

A couple of weeks ago I posted a manifesto. I said Web publishers should let themselves change published articles and posts whenever they need to — and make each superseded version accessible to readers, the way Wikipedians and software developers do.

This one simple addition to the content-management arsenal, known as versioning, would allow us to use the Web as the flexible medium it ought to be, without worrying about confusing or deceiving readers.

Why not adopt [versioning] for every story we publish? Let readers see the older versions of stories. Let them see the diffs. Toss no text down the memory hole, and trigger no Orwell alarms.

Then I asked for help creating a WordPress plugin so I could show people what I was talking about. Now, thanks to some great work by Scott Carpenter, we have it. It’s working on this blog. (You can get it here.) Just go to the single-page form of any post here (the one that’s at its permalink URL, where you can see the comments), and if the post has been revised in any way since I published it, you can click back and see the earlier versions. You can also see the differences — diffs — highlighted, so you don’t have to hunt for them.

The less than two weeks since my post have given us several examples of problems that this “show your work” approach would solve. One of them can be found in the story of this New York Times error report over at MediaBugs.

An anonymous bug filer noticed that the Times seemed to have changed a statistic in the online version of a front-page story about where California’s African Americans stood on pot legalization. As first published, the story said blacks made up “only” or “about 6 percent” of the state population; soon after it was posted, the number changed to “less than 10 percent.” There’s a full explanation of what happened over at MediaBugs; apparently, the reporter got additional information after the story went live, and it was conflicting information, so reporter and editor together decided to alter the story to reflect the new information.

There is nothing wrong with this. In fact, it’s good — the story isn’t etched in stone, and if it can be improved, hooray. The only problem is the poor confused reader, who saw a story that read one way before and now reads another way. The problem isn’t the change; it’s the failure to note it. Showing versions would solve that.

Another Times issue arose yesterday when the paper changed a headline on a published story. The original version of a piece about Tumblr, the blogging service, was headlined “Facebook and Twitter’s new rival.” Some observers felt this headline was hype. (Tumblr is successful but in a very different league from the vastness of Facebook and Twitter.) At some point the headline was rewritten to read “Media Companies Try Getting Social With Tumblr.” Though the article does sport a correction now fixing some other errors, it makes no note of the headline change.

I don’t know what official Times policy is on headline substitution. Certainly, Web publications often modify headlines, and online headlines often differ from print headlines. Still, any time there’s an issue about the substance of a headline, and the headline is changed, a responsible news organization should be forthright about noting the change. Versioning would let editors tinker with headlines all they want.

I do not mean to single out the Times, which is one of the most scrupulous newsrooms around when it comes to corrections. Practices are in a state of flux today. News organizations don’t want to append elaborate correction notices each time they make a small adjustment to a story. And if we expect them to, we rob ourselves of the chance to have them continuously improve their stories.

The versioning solution takes care of all of this. It frees writers and editors to keep making their work better, without seeming to be pulling a fast one on their readers. It’s a simple, concrete way to get beyond the old print-borne notion of news stories as immutable text. It moves us one decent-sized step toward the possibilities the Web opens up for “continuing stories,” iterative news, and open-ended journalism.

How the plugin happened: I got some initial help from Stephen Paul Weber, who responded to my initial request to modify the existing “post revision display” plugin so as to only list revisions made since publication. Weber modified the plugin for me soon thereafter (thank you!). Unfortunately, I failed to realize that that plugin, created by D’Arcy Norman, only provided access to version texts to site administrators, not regular site visitors.

Scott Carpenter, the developer who’d originally pointed out the existing plugin to me, stepped up to the plate, helped me work up a short set of requirements for the plugin I wanted, and set to work to create it. Here’s his full post on the subject, along with the download link for the plugin. We went back and forth a few times. He thought of some issues I hadn’t — and took care of them. I kept adding new little requirements and he knocked them off one by one. I think we both view the end-product as still “experimentally usable” rather than a polished product, but it’s working pretty well for me here.

As the author of a whole book on why making software is hard, I’m always stunned when things go really fast and well, as they did here. Thanks for making this real, Scott!

If you run WordPress and like the idea of showing your work, let us know how it goes.


 

Bloomberg circles the wagons on misleading Gulf spill poll coverage

News organizations’ default response to criticism is to circle the wagons.

“We stand by our story!” is a stirring thing to say, and sometimes it’s even the right thing. But in the web world of 2010, where everyone has a public platform, ignoring critics can also squander a news outlet’s credibility and alienate its audience.

The basic premise of MediaBugs — which I laid out in this video — is that news organizations can begin winning back the public trust they have lost by engaging civilly, in public, with people who criticize them about specific errors. Whoever is right in the end, and whether the newsroom decides to run a correction or not, the editors are better off explaining their thinking than slamming the door on dialogue.

For an example of precisely the wrong way of handling legitimate questions about coverage, consider the controversy over a recent Bloomberg opinion poll.
[Read more...]


 

Politico, Slate, and story versioning — or: the only Web constant is change

Last month, the hardworking gang at Politico got into a dustup with critics after an editor made a change in an already-posted story. The story was about the Rolling Stone/General McChrystal affair; the change removed a phrase that described how beat reporting works; the phrase had drawn considerable attention, and so did its disappearance.

I’m not going to add to the volume of commentary on that affair. I’m interested here in the larger issue of the mutability of online content, and how responsible news organizations deal with it.

A story posted at Slate yesterday sheds considerable light on this issue, in the course of making a few stumbles of its own. (The story includes quotes from a recent post I wrote about best practices in online corrections.) It’s remarkable that, after 15 years of Web publishing experience, we haven’t gotten better at handling changes to news published online. Before this post is done, I will offer a straightforward, concrete proposal for doing so.

[Read more...]


 

You’re the notorious flamingo smuggler!

We created what we hope is a fun little video explaining the basic concept behind MediaBugs. All credit to the awesome talents of Kate and Nate at Beep Show — and their stock company of men in shorts.

The Story of MediaBugs from Beep Show on Vimeo.


 

MediaBugs report on Bay Area corrections flunks most news sites

Because web pages are just computer files, news stories on the web can be altered at will after publication. That makes corrections on the web a little more complex than corrections in print — but it also makes them potentially much more effective. Unlike in print or broadcast, you can fix the original. You can make errors vanish — though not without a trace, if you’re doing it right.

So why do so many news organizations continue to handle their online corrections so poorly? At MediaBugs, where we’re devoted to improving the feedback loop between the public and the press, we’ve just published our first survey of corrections practices at more than two dozen Bay Area news outlets. The report’s top-line conclusion? Mostly, they’re doing it wrong.

Three quarters of the 28 news outlets we reviewed provide no corrections-reporting link of any kind on their home or article pages. Even media organizations that show signs of working to handle corrections carefully fall down in various ways — and lots of others don’t look like they’re even trying.

Many bury information about how to report errors behind confusing trails of links. Some provide multiple, poorly labeled avenues for feedback without telling readers which ones to use for error reports. Others provide no access to recently corrected articles beyond a search on “corrections,” which often turns up multiple stories about prisons.

These findings are disheartening — not simply for how poorly editors are protecting their readers’ trust in them, but also because handling these matters better doesn’t take that much effort.

There’s really just a small number of things any news website needs to do if it wants to handle corrections and error reports responsibly:

  • Append a note to any article that’s been corrected, explaining the change;
  • Keep a list of these changes, linking to the corrected articles, at a fixed location on the site;
  • Post a brief corrections policy, with information about how readers can report errors they find;
  • Make sure that your corrections listing page and your corrections policy (whether they’re on the same or different pages) are part of your site navigation — they should be accessible by one click from any page on your site.

In addition to our survey, we’ve provided a brief summary of best practices for corrections and error reporting that we hope will be helpful to news site editors and their readers alike.

Fifteen years ago, in the early days of web publishing, it might have been understandable for editors to have a hard time figuring out how to handle corrections: This pliable medium was new and strange.

But news on the web is no longer in its infancy, and “We’re new to this” just doesn’t cut it anymore as an explanation for the kind of poor practices our MediaBugs survey documents. The explanations you generally hear are truthful but don’t excuse the problems: “Our content management system makes it too hard to do that” or “we just don’t have the resources to do that” or “we’ve been meaning to fix that for a while but never seem to get around to it.”

The web excels at connecting people. That’s what its technology is for. Yet when it comes to the most basic areas of accuracy and accountability, the professional newsrooms of the Bay Area (and so many other communities) continue to do a poor job of connecting with their own readers.

It’s time for news websites to move this issue to the top of their priority lists and get it taken care of. They can do this, in most cases, with just a few changes to site templates and some small improvements in editing procedures. Of course, we hope, once they’ve done that, that they’ll do more: At MediaBugs, we want to see that every news page on the web includes a “Report an Error” button as a standard feature, just like the ubiquitous “Print” buttons, “Share This” links and RSS icons.

MediaBugs offers one easy way to do this — our error-reporting widget is easy to integrate on any website. You can now see it in action on every story published over at Spot.Us (as it is on every post here at my Wordyard blog). But there are plenty of other ways to achieve this same end.

As long as readers can quickly and easily find their way to report an error with a single click, we’ll be happy. But before we get there, we’ve all got some basic housekeeping to take care of first. End the suffering of orphaned corrections links and pages now!

[Cross-posted from the MediaShift Idea Lab blog]