Yesterday , A couple of days ago, I wrote about <cringe> “taxonomical narratives” </cringe>at the critical center of content strategy, how the velocity and arrangement of microchunks is reshaping the nature of story, and how this change is creating a new firm-based (not just functional) competitive strategy for content innovation down to the level of the bit.
This That morning, in a very smart piece about the demise of newspapers, Razorfish’s Michael Barnwell wryly blogged on Scatter/Gather, the Razorfish CS blog, how “content strategy has long been interested in the relational sphere of stories” and now visionary computer scientist David Gelertner’s idea of “lifestreams” might be one creative solution.
Then Upendra Shardnand, Daylife’s CEO, wrote Storytelling Is Stuck In A Rut—What Publishers Can Do About It, a quick essay about how newspapers seem willing to talk about changing their IT, distribution, and revenue strategies but rarely question “the actual craft of writing and telling stories.” “On one side you have parties that produce what were once finished products, but are now just data for parties on the other side who take that fodder and reconstruct it,” Shardnand writes. ”It’d be much easier for everyone if the authors took matters into their own hands, and wrote stories in a new language, with new tools, for the web.”
Story? What story? Whose story?
We all seem to be pointing to the same stifling lack of new tools out there to help editors and writers integrate, aggregate, reconstruct and re-narrativize story from relatively random microchunks of data in many formats in real time, but each of us wants to assign different job reqs to the folks who would do this.
Gelernter (whose comments are taken from an interview in Edge with NYU/ITP prof Clay Shirky and NY Times uber-tech writer John Markoff), doesn’t really care much who does this job: For him, it’s all about the construction—and definition—of “lifestreams,” a key element in his thinking about computer interfaces that ultimately become mirrors of the mind. Lifestreams as he defines them are ”[sequences] of all kinds of documents — all the electronic documents, digital photos, applications, Web bookmarks, rolodex cards, email messages and every other digital information chunk in your life …appearing on your screen as a receding parade of index cards.” For Gelertner, this is the newsroom of the future:
[Instead] of the managing editor, the city editor, or whatever, being a bigshot, there’s something more like a producer of the stream in real time. So the producer of the stream has lots of feeds. A reporter is posting a new story. Another reporter is posting a new story. AP is doing stuff. Photographs are coming in. Videos are coming in. But each person looks at one thing at one time. Okay, so I as the producer want to say, “Okay, put that on the stream now. And now put this on the stream. And now put two of these on the stream.”
In other words, a curator.
Barnwell says that this is good news for editors—and content strategists. He says that editors’ legacy role as curators—”assisted [of course] by an intelligent software agent to help in sifting the relevance of the news and discovering related stories”— will be one of the “bright prospects” for the continuation of journalistic organizations. As for content strategists, Barnwell says that their job is to ”[maintain] the smooth functioning and insightfulness of the digital lifestream. In fact, content strategy has long been interested in the relational sphere of stories.”
Well, I’m not so sure this is as good for editors as Barnwell—in my experience, editors are good at curating the stories in their own magazines or newspapers, but they are rarely focused on aggregating context, especially from the web. That’s the writer’s job. And as for presenting that context to readers, for a long time—even now—many, many publications won’t link outside themselves. They still think a linking reader is a lost reader! (Way to show confidence in your product, editors!)
Not who but how
So is this what content strategists should be doing?
When I wrote yesterday about “taxonomical narratives” this is part of what I was thinking. Someone has to kick off, organize, strategize, and render author-side metatagging and data hierarchies for readers and match that to readers’ expectations and needs on a continual basis. Relevancy and related-story technologies from Daylife to Inform to Zemanta to Publish2 will all be useful.
But as Upendra says, it’s not enough. We still need someone to understand storytelling at the level of the bit—and please not by turning it into megabyte multimedia, constructing yet another metanarrative, this time built by editors instead of authors. (It also should be additively accesible to users in the form of user-side meta-tagging, ranking and commenting, but let’s leave the ugc side of this alone for a minute, ok?)
It doesn’t finally matter what you call this person. It probably depends on the company and agency. Like Barnwell, I suspect CS is more involved in systemic maintenance and strategy (d’oh) than storytelling itself, especially in journalistic situations. In agencies, it seems to me CS and creative need to be part of a collaborative effort.
The real question though is not who should do this, but what the economic incentives are for it. You can train editors or content strategists to think through these issues, but before any of that happens, you need new tools. As Shardanand says, the problem is “The tools haven’t changed. Whether it’s Microsoft Word or Wordpress, it’s all still word processing. The workflow in newsrooms hasn’t changed. Authors, rarely being software developers themselves, can’t develop the tools they would want. Usually some third-party CMS company makes it for them…Publishers haven’t committed significant R&D to the development of new tools. If they, did they’d have a competitive advantage, much like Apple developing its own chips or Amazon tinkering with its shopping experiences.”
Indeed, while publishers are committing tens of millions of dollars to installation of terrific end to end XML-based, network capable CMS systems such as Eidos’s amazing Methode, they aren’t much willing to innovate at the front end of a story. In other words, as Shardanand says, the story is still just words and pictures, with these bits over here isolated from those bits over there, both in terms of internal story structure and external links. (And yes, the Times is doing a great job with reporting stories with interactive components, but that’s not what we’re talking about here.)
So when will it take to make story change? Much as some CS people believe they have the ability to make it change, I very much doubt it. At agencies, content is typically held in the creatives’ silo; at magazines and newspapers, it’s the province of either editors or producers—over there on the “online side.” (Stage direction: usually followed by someone pointing across the floor to the other side of the newsroom. ”Uh, those guys over there–can you see ‘em?” Oh yes we see.)
So what comes before a new job req and a rockin’ CMS? Probably this: Behavioral innovation at the brand level—the brand promise that these companies, either newspapers or media organizations or agencies (on behalf of brands or on their own) deliver—driven down to the level of customer service.
It’s easy to say aggregate. As Barnwell points out, you can aggregate with machines, rebundle by metatag. Smart aggregation is more though. As Umair Haque suggests in his in-depth, very toughly argued dek on the economics of new media—one of the few things I’d say is truly a must read in digital media analysis—it requires leveraging deep information about content including customers’ information, expectations, and preferences about content, then reflitering, altering, remixing microchunks into something new and different. A story. A new story. That’s brand in customer terms, not brand as grand narrative story, brand marketing. That’s is the difference that makes a difference for Google pagerank.
As Shirky and Markoff’s question to Gelertner implies—and as Haque, Shirky, Jarvis and a growing chorus of others now say—this isn’t a matter of R&D anymore, but a struggle for the future existence of media. No innovation at the level of story is likely, as Haque says, to lead to abrupt hyperdeflation of news products by smart aggregators who don’t care about anything more than the revelation of new ideas and repackaging, remixing, and rebundling reportage to support their piratical ways. I hope we figure it out before that.
Related articles by Zemanta
- Jeff Jarvis and Umair Haque: new business models (accmanpro.com)
- My top takeaways from BarCamp NewsInnovation Philly (wemediaguru.com)
- Four Reasons Your News Org Should Use APIs (poynter.org)

![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=fa8caab3-a661-41b3-8983-ea51112015b2)
7. Credibility: From day 1, Lipman gave readers all the wrong signals. She put all her marbles on long form journalism when everyone was talking about digital journalism, then chose many of the same old prize-winners from Michael Lewis to Tom Wolfe. Her covers showed a complete lack of comprehension about her audience and the economy. Remember the golden skycrapers, the gears, the hairy apes, the spy—one cliché after another—followed by Dov Charney, Sarah Palin, and the fallen bull? What’s that you say? She shouldn’t have been expected to cover the Zombieconomy when she was hired to celebrate it? Rubbish. She could have covered everything from recession economics and its style to derivative disasters to Obama and his style—right from the start. (That fallen bull was apparently stuck on the cover after Lipman feared she’d be seen as a Barry cheerleader, a copycat, or both.) She could have signalled outrage. Instead she signaled that she was personally offended by the fallout and incapable of explaining it. And flying to Davos first class didn’t help. (![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=e80e7205-2742-46d8-b8cb-de344c3bcc9a)