<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/">
<channel>
<title>Techdirt. Stories filed under &quot;organization&quot;</title>
<description>Easily digestible tech news...</description>
<link>http://www.techdirt.com/</link>
<language>en-us</language>
<image><title>Techdirt. Stories filed under &quot;organization&quot;</title><url>http://www.techdirt.com/images/td-88x31.gif</url><link>http://www.techdirt.com/</link></image>
<item>
<pubDate>Fri, 20 Jun 2008 11:05:00 PDT</pubDate>
<title>Readers Want Context and Organization, Not Just 'Content'</title>
<dc:creator>Timothy Lee</dc:creator>
<link>http://www.techdirt.com/articles/20080609/1105121347.shtml</link>
<guid>http://www.techdirt.com/articles/20080609/1105121347.shtml</guid>
<description><![CDATA[ <p>I wrote last fall that the <i>New York Times</i> was <a href="http://www.techdirt.com/articles/20071101/220332.shtml">finally starting to get the web</a>, and I think the <i>Washington Post</i> is in the <a href="http://www.techdirt.com/articles/20070726/231430.shtml">same category</a> of taking the web a lot more seriously than it did a few years ago. But although the biggest newspapers are now taking the challenge seriously, they still have work to do. Case in point: the Washington, DC, area had a big storm a while back, and Scott Karp went to the <i>Washington Post</i> website expecting (reasonably enough) to find information about it. Unfortunately, despite being a DC-based publication, the <i>Post</i>'s home page <a href="http://publishing2.com/2008/06/04/what-newspapers-still-dont-understand-about-the-web/">had very little information about the storm</a>. Indeed, the home page wouldn't have mentioned it at all if there didn't happen to be a story on the most-read articles list. Unfortunately it was a <a href="http://www.washingtonpost.com/wp-dyn/content/article/2008/06/04/AR2008060402818.html?nav=hcmodule">formulaic story from the print edition</a> that was great for a non-Washingtonian who doesn't know anything about the storm, but it's not terribly useful to a Washingtonian who can see the storm happening outside his window. What locals need is detailed, real-time information. After seeing nothing relevant on the WaPo's website, he went over to Google, typed in "power outages in northern virginia," and the first hit was a page from Dominion Electric showing power outages around its service region. Karp went back to the <i>Post</i>'s website, and after more searching finally found a <a href="http://blog.washingtonpost.com/capitalweathergang/">blog</a> focusing on DC area weatherâ€&rdquo;precisely the sort of thing that the Post ought to be making more prominently displayed during major weather events.</p>

<p>I think there are a couple of lessons to be learned from this. First, as Mike has said before, <a href="http://www.techdirt.com/articles/20080414/015112835.shtml">good content is often less important than useful services like organizing and filtering information.</a> The <i>Post</i> had the content Karp wanted -- an up-to-date blog and links to useful resources -- but because its website was poorly organized, he wasn't able to find it easily. Some newspapers <a href="http://www.techdirt.com/articles/20060918/020228.shtml">claim</a> that Google lives parasitically off of other content producers, but I think this is a good illustration of why that's not true; there was plenty of content out there, but without Google, Karp might not have been able to find it. The other problem is that for all of the <i>Post</i>'s progress  it still seems to regard itself largely as a newspaper that happens to publish its articles on the web, rather than a general media company that happens to publish a paper edition. Sometimes a traditional newspaper article is the best way to cover a story, but often (as in this case) it's not. The <i>Post</i>, like a lot newspaper outlets, still seems to put too much emphasis on its print content, even in circumstances were a shorter, timelier, and more densely-linked story would be more useful to readers.</p><br /><br /><a href="http://www.techdirt.com/articles/20080609/1105121347.shtml">Permalink</a> | <a href="http://www.techdirt.com/articles/20080609/1105121347.shtml#comments">Comments</a> | <a href="http://www.techdirt.com/articles/20080609/1105121347.shtml?op=sharethis">Email This Story</a><br />
 ]]></description>
<slash:department>web-as-afterthought</slash:department>
<wfw:commentRss>http://www.techdirt.com/comment_rss.php?sid=20080609/1105121347</wfw:commentRss>
</item>
</channel>
</rss>