Or, press release, for that matter. This past week, Adobe announced that it was opening up parts of its Flex platform under an open source license, with the intent to release its entire code sometime by the end of the year. Pretty interesting stuff, right? Somewhat important, no?
But you know how the tech community found out?
Through a video interview by Robert Scoble on PodTech.
If you monitored the blogging / news-osphere thereafter, a number of other posts started to surface, with Adobe’s official release over here.
But, ironically, the most useful post, I found, was neither of these posts (it was Nik Cubrilovic’s over at TechCrunch).
In fact, I found the entire situation frustating because:
- I knew Flex was important
- I’m not geeked up technically savvy enough to know what Flex was
- In general, I need information fast
- I didn’t feel like trawling through different posts to find out what I wanted to know
What would have been really nice would have been a central repository for some nice, quick, facts in an every-day kind of language, with a bunch of *annotated* links to a variety of important resources on the web, such as interviews, videos, opinions, and examples.
Wait — I just described a social media news room! This is an idea that was championed by Todd Defren of SHIFT Communications a little while ago, and I think it might have been useful in Flex’s launch. Really Useful.
Here’s why.
Listen, I think its great that Adobe decided to go “cutting edge” with a video interview on PodTech. Scoble’s got a huge audience, and on the whole, has their attention because of the credibility he’s got.
But did anyone not find it terribly ironic that the news was all about going “open source”, while the content on the interview was “locked” into the video? I’m stretching the metaphor here, but what I mean is that it was simply maddening that the bloody show had no show notes!
Sure, there’s an argument to be made that “if they’re interested they’ll watch all the way through — and that’s good for PodTech and Adobe”. But isn’t that a kind of command-and-control attitude that is the anti-thesis of the “transparency” and “open-source” ethos?
I still haven’t watched the interview, not because its *bad* per se, but I just don’t have the time to sit down and watch something for 25 minute when I could glean the same information (which is all I’m looking for — *information*) in less than two on a single, well constructed site.
And I think this is where Adobe really could have gotten it together.
Rather (or, perhaps, in *addition* to stringing) together a traditional press release over here, which is full of jargony technical speak, forcing people to find *other* resources online, it could create a single page with a few simple lines describing a) what the technology was and b) why its important, and add a whole bunch of annotated links to other important resources on the web.
I think the word “annotated” is important, because rather than just a long list of links, it gives the reader some idea of what each link means, and more importantly, how it contributes to the over all message of the page.
Robert Scoble’s interview, for example is more than just a “PodTech Interview”, but rather “Robert Scoble Interviews David Wadhwani, VP Engineering and Ely Greenfield, Flex Architect” and another sentence or three on why its important, or different, or why it adds to the “conversation”. Other examples?
The best part? It doesn’t need to be static. Like any good “new media” document it could be an evolving “document”, with new links added all the time as more stuff comes on board.
Now, the scary part is exactly what new media pundits will be clamoring over, which is that there’s nothing’s authentic about this kind of bit of communication, where’s the conversation, and for the love of pete, why not just start a blog?!
Hey, I love blogging just as much as the next man / woman / person, but as you can see in Flex’s case, sometimes it just makes no sense. Starting a blog for the purposes of promoting “awareness” about a product seems fairly disingenuous, and furthermore, while there’s an argument to be made for starting a product/service oriented blog at *the beginning*, you can see here that Adobe wanted to keep things under wraps for a little while.
Note — they didn’t want to *lie* … but they wanted to keep things secret.
I think I see the flip side of this. If done the “right” way, social media news rooms (or press releases) allows for the congregation of *many* different kinds of voices, and yes, if it sticks to the transparent and open source ethos, it would even list dissenting opinions as well. Furthermore, its something that stays on a host company’s site, and would not be something “pushed” on to journalists (or bloggers), but rather, something more of a resource.
Having blogs is good. Having video is good. Podcasts are useful as well, in their own way. The announcement of Flex was interesting in the seemingly haphazard way it was done, and I think, might have served as a great example of what social news room could be. Furthermore, given the kind of technology that they were dealing with and the kinds of opinions that were proliferating in and around the blogosphere, I think it would have really been a great opportunity for Adobe. Since they didn’t have a “Flex” blog, it would have been an opportunity to at least *collect* important opinions, so as to acknowledge the conversations that were going on in a way that would have been helpful to everyone.
Resources: