<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Trimming the long tail &#8211; the danger of stripping back our websites</title>
	<atom:link href="http://www.prettysimple.co.uk/blog/index.php/2011/09/trimming-the-long-tail/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.prettysimple.co.uk/blog/index.php/2011/09/trimming-the-long-tail/</link>
	<description>about web, social media, accessibility and usability</description>
	<lastBuildDate>Fri, 01 Mar 2013 16:20:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: James</title>
		<link>http://www.prettysimple.co.uk/blog/index.php/2011/09/trimming-the-long-tail/comment-page-1/#comment-9191</link>
		<dc:creator>James</dc:creator>
		<pubDate>Mon, 24 Oct 2011 19:36:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.prettysimple.co.uk/blog/?p=1562#comment-9191</guid>
		<description><![CDATA[Really interesting Nick, thanks. Search is without a doubt one of the most crucial elements to this kind of site.]]></description>
		<content:encoded><![CDATA[<p>Really interesting Nick, thanks. Search is without a doubt one of the most crucial elements to this kind of site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Charney</title>
		<link>http://www.prettysimple.co.uk/blog/index.php/2011/09/trimming-the-long-tail/comment-page-1/#comment-9185</link>
		<dc:creator>Nick Charney</dc:creator>
		<pubDate>Mon, 24 Oct 2011 16:33:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.prettysimple.co.uk/blog/?p=1562#comment-9185</guid>
		<description><![CDATA[In Canada the City of Calgary chose to make search the central feature of the website rather than by pruning pages themselves.  They worked directly with Google to help organize their stack and make it more citizen centred through search.  You can see the site here:

http://www.calgary.ca/

The move garnered positive response from the country&#039;s national newspaper:

http://www.theglobeandmail.com/news/technology/digital-culture/ivor-tossell/more-complexity-demands-greater-simplicity/article2147167/

Cheers.

Nick]]></description>
		<content:encoded><![CDATA[<p>In Canada the City of Calgary chose to make search the central feature of the website rather than by pruning pages themselves.  They worked directly with Google to help organize their stack and make it more citizen centred through search.  You can see the site here:</p>
<p><a href="http://www.calgary.ca/" rel="nofollow">http://www.calgary.ca/</a></p>
<p>The move garnered positive response from the country&#8217;s national newspaper:</p>
<p><a href="http://www.theglobeandmail.com/news/technology/digital-culture/ivor-tossell/more-complexity-demands-greater-simplicity/article2147167/" rel="nofollow">http://www.theglobeandmail.com/news/technology/digital-culture/ivor-tossell/more-complexity-demands-greater-simplicity/article2147167/</a></p>
<p>Cheers.</p>
<p>Nick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: simon gray</title>
		<link>http://www.prettysimple.co.uk/blog/index.php/2011/09/trimming-the-long-tail/comment-page-1/#comment-8411</link>
		<dc:creator>simon gray</dc:creator>
		<pubDate>Thu, 15 Sep 2011 16:13:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.prettysimple.co.uk/blog/?p=1562#comment-8411</guid>
		<description><![CDATA[@paul - actually, like the bbc site is exactly what i was thinking. the bbc does not have one site, it has many sites - eg the radio site, which itself is split into different sites for the stations, or the news site, which then splits into different sites for sport, and weather, etc. and there are sites for individual programmes.

my point is, all these are contained under one overarching banner of &#039;bbc.co.uk&#039;, but the way they are held under that banner the content the user wishes to find is (for the most part) easy to find, with other content not interfering with it.

so, yes, we indeed *should* be creating top-tasks-focussed sites, so that the 20% of content 80% of users want is easy to find, without the remaining 80% of the content interfering with that. my suggestion is that the best way of also making the other 80% of important content easy to find for the remaining 20% of important users is not to try to keep the entire site&#039;s content constrained within a single one-size-fits-all site with a single global navigation and single global site design, but to break it off into properly segmented microsites. of course there needs to be a way for web users to find all these microsites - that&#039;s what the home page is for!]]></description>
		<content:encoded><![CDATA[<p>@paul &#8211; actually, like the bbc site is exactly what i was thinking. the bbc does not have one site, it has many sites &#8211; eg the radio site, which itself is split into different sites for the stations, or the news site, which then splits into different sites for sport, and weather, etc. and there are sites for individual programmes.</p>
<p>my point is, all these are contained under one overarching banner of &#8216;bbc.co.uk&#8217;, but the way they are held under that banner the content the user wishes to find is (for the most part) easy to find, with other content not interfering with it.</p>
<p>so, yes, we indeed *should* be creating top-tasks-focussed sites, so that the 20% of content 80% of users want is easy to find, without the remaining 80% of the content interfering with that. my suggestion is that the best way of also making the other 80% of important content easy to find for the remaining 20% of important users is not to try to keep the entire site&#8217;s content constrained within a single one-size-fits-all site with a single global navigation and single global site design, but to break it off into properly segmented microsites. of course there needs to be a way for web users to find all these microsites &#8211; that&#8217;s what the home page is for!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlastairC</title>
		<link>http://www.prettysimple.co.uk/blog/index.php/2011/09/trimming-the-long-tail/comment-page-1/#comment-8386</link>
		<dc:creator>AlastairC</dc:creator>
		<pubDate>Wed, 14 Sep 2011 12:20:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.prettysimple.co.uk/blog/?p=1562#comment-8386</guid>
		<description><![CDATA[The point on cost is also interesting, in my experience the level of cost (or at least effort) goes up in this order:

1. Throw a website together, it&#039;s got on it whatever you already had.
2. Make a large website (2000+ pages) which is difficult to use, but comprehensive.
3. Make a somewhat usable, large and comprehensive website.
4. Make a very usable, smaller site (&lt;1000 pages) that still covers the vast majority of things.

The first is what LAs had in the 90&#039;s and early 2000s, and the rest is a natural progression, but it takes more effort to create a smaller site that is still comprehensive.

The last is the most effective, but it takes a lot of effort to concisely cover everything you should.

I get the impression that LAs would be going back to square 1, without the effort needed to make it useful and usable.]]></description>
		<content:encoded><![CDATA[<p>The point on cost is also interesting, in my experience the level of cost (or at least effort) goes up in this order:</p>
<p>1. Throw a website together, it&#8217;s got on it whatever you already had.<br />
2. Make a large website (2000+ pages) which is difficult to use, but comprehensive.<br />
3. Make a somewhat usable, large and comprehensive website.<br />
4. Make a very usable, smaller site (&lt;1000 pages) that still covers the vast majority of things.</p>
<p>The first is what LAs had in the 90&#039;s and early 2000s, and the rest is a natural progression, but it takes more effort to create a smaller site that is still comprehensive.</p>
<p>The last is the most effective, but it takes a lot of effort to concisely cover everything you should.</p>
<p>I get the impression that LAs would be going back to square 1, without the effort needed to make it useful and usable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.prettysimple.co.uk/blog/index.php/2011/09/trimming-the-long-tail/comment-page-1/#comment-8383</link>
		<dc:creator>James</dc:creator>
		<pubDate>Wed, 14 Sep 2011 11:35:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.prettysimple.co.uk/blog/?p=1562#comment-8383</guid>
		<description><![CDATA[Thanks for the comments so far, everyone. Clearly a subject of interest to many.

SOCITM are holding &lt;a href=&quot;http://www.socitm.net/events/event/245/&quot; rel=&quot;nofollow&quot;&gt;an event in London tomorrow to discuss Top Tasks&lt;/a&gt; so I&#039;ll be following that with interest.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the comments so far, everyone. Clearly a subject of interest to many.</p>
<p>SOCITM are holding <a href="http://www.socitm.net/events/event/245/" rel="nofollow">an event in London tomorrow to discuss Top Tasks</a> so I&#8217;ll be following that with interest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Forrest</title>
		<link>http://www.prettysimple.co.uk/blog/index.php/2011/09/trimming-the-long-tail/comment-page-1/#comment-8380</link>
		<dc:creator>Ryan Forrest</dc:creator>
		<pubDate>Wed, 14 Sep 2011 10:20:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.prettysimple.co.uk/blog/?p=1562#comment-8380</guid>
		<description><![CDATA[I agree wholeheartedly with Paul that more intelligent use of metadata and taxonomies is the way forward. I&#039;m thinking dynamic menus (ie menus dictated by metadata rather than being conceived in separation from actual content) and intelligent, suggestive search being promoted as key navigation.

I am in favour of a model which gives &#039;top tasks&#039;/transactional stuff homepage priority but also provides a well-signposted, navigable repository (I like the Wikipedia model for &#039;static&#039; pages and think it could work) - built around LGNL but with expanded and enhanced metadata taxonomies - to assist councils in categorizing information - the &#039;long tail&#039;.






I am currently plotting a mock up to this end using Drupal.]]></description>
		<content:encoded><![CDATA[<p>I agree wholeheartedly with Paul that more intelligent use of metadata and taxonomies is the way forward. I&#8217;m thinking dynamic menus (ie menus dictated by metadata rather than being conceived in separation from actual content) and intelligent, suggestive search being promoted as key navigation.</p>
<p>I am in favour of a model which gives &#8216;top tasks&#8217;/transactional stuff homepage priority but also provides a well-signposted, navigable repository (I like the Wikipedia model for &#8216;static&#8217; pages and think it could work) &#8211; built around LGNL but with expanded and enhanced metadata taxonomies &#8211; to assist councils in categorizing information &#8211; the &#8216;long tail&#8217;.</p>
<p>I am currently plotting a mock up to this end using Drupal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger White</title>
		<link>http://www.prettysimple.co.uk/blog/index.php/2011/09/trimming-the-long-tail/comment-page-1/#comment-8379</link>
		<dc:creator>Roger White</dc:creator>
		<pubDate>Wed, 14 Sep 2011 08:54:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.prettysimple.co.uk/blog/?p=1562#comment-8379</guid>
		<description><![CDATA[Gary says:

Regarding your example of not finding the word ‘deaf’ on a site: Do you think this could be classed as discrimination?

Knowing bureaucracies, perhaps a search on &quot;hearing impairment&quot; might have returned a hit ;)]]></description>
		<content:encoded><![CDATA[<p>Gary says:</p>
<p>Regarding your example of not finding the word ‘deaf’ on a site: Do you think this could be classed as discrimination?</p>
<p>Knowing bureaucracies, perhaps a search on &#8220;hearing impairment&#8221; might have returned a hit ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PaulGeraghty</title>
		<link>http://www.prettysimple.co.uk/blog/index.php/2011/09/trimming-the-long-tail/comment-page-1/#comment-8378</link>
		<dc:creator>PaulGeraghty</dc:creator>
		<pubDate>Wed, 14 Sep 2011 08:44:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.prettysimple.co.uk/blog/?p=1562#comment-8378</guid>
		<description><![CDATA[@simongray - what? like the BBC you mean?

The BBC managed to work out how to create sites within sites and make it work - floating content off into different sites is just a giant leap backwards.

That the (majority of) CMS vendors cannot work out how to make poly-hierarchical menus in the LGNL fashion does not mean that body of work should be dissed out of hand.

Making a &quot;Top tasks&quot; site is wrong thinking .. being clever enough to associate top tasks with each ones inevitable &quot;long tail&quot; infrastructure is the challenge. 

And the key to that challenge is metadata - that is what can magically glue all of this stuff together and automate the linking, automate the searching and automate menu associations.

If the driver for removing content is that it is too costly to maintain the links to it, then let me tell you - you are doing it wrong.

If the driver for removing content is that it gets out of date, then again - you are doing it wrong - if you have static documents containing variables like prices, times, people, telephone numbers - then I repeat, you have been doing it wrong.

Isolate what changes from what stays the same.

That is the challenge that LG CMS vendors are largely unable to rise to, sadly this is mostly the fault of those that are responsible for drawing up the specs - so instead of looking for proper fit for purpose Local Government solutions - we peek about looking for saviours.

Now, let those who want to follow the Socitm pied piper do so - it will all end it tears - do you remember having to make a text only version of your site? Remember the bonus points that Socitm used to dole out for doing so? Then the mysterious volte-face the following year?

This &#039;focus only on top tasks&#039; has the same childish smell about it in my book, lets all run over and look through the ... round window.]]></description>
		<content:encoded><![CDATA[<p>@simongray &#8211; what? like the BBC you mean?</p>
<p>The BBC managed to work out how to create sites within sites and make it work &#8211; floating content off into different sites is just a giant leap backwards.</p>
<p>That the (majority of) CMS vendors cannot work out how to make poly-hierarchical menus in the LGNL fashion does not mean that body of work should be dissed out of hand.</p>
<p>Making a &#8220;Top tasks&#8221; site is wrong thinking .. being clever enough to associate top tasks with each ones inevitable &#8220;long tail&#8221; infrastructure is the challenge. </p>
<p>And the key to that challenge is metadata &#8211; that is what can magically glue all of this stuff together and automate the linking, automate the searching and automate menu associations.</p>
<p>If the driver for removing content is that it is too costly to maintain the links to it, then let me tell you &#8211; you are doing it wrong.</p>
<p>If the driver for removing content is that it gets out of date, then again &#8211; you are doing it wrong &#8211; if you have static documents containing variables like prices, times, people, telephone numbers &#8211; then I repeat, you have been doing it wrong.</p>
<p>Isolate what changes from what stays the same.</p>
<p>That is the challenge that LG CMS vendors are largely unable to rise to, sadly this is mostly the fault of those that are responsible for drawing up the specs &#8211; so instead of looking for proper fit for purpose Local Government solutions &#8211; we peek about looking for saviours.</p>
<p>Now, let those who want to follow the Socitm pied piper do so &#8211; it will all end it tears &#8211; do you remember having to make a text only version of your site? Remember the bonus points that Socitm used to dole out for doing so? Then the mysterious volte-face the following year?</p>
<p>This &#8216;focus only on top tasks&#8217; has the same childish smell about it in my book, lets all run over and look through the &#8230; round window.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: simon gray</title>
		<link>http://www.prettysimple.co.uk/blog/index.php/2011/09/trimming-the-long-tail/comment-page-1/#comment-8377</link>
		<dc:creator>simon gray</dc:creator>
		<pubDate>Wed, 14 Sep 2011 07:48:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.prettysimple.co.uk/blog/?p=1562#comment-8377</guid>
		<description><![CDATA[My favourite case study in this regard is the highways services landing page, proudly declaring how many miles of roads and how many street lights it looks after. &quot;who&#039;s interested in that?&quot;, the customer services obsessive asks. I can tell you who&#039;s interested - the hundreds of kids throughout the year, all doing their school geography projects, who without that info on the website will be making hundreds of phone calls costing ten quid a pop to find out the information.

I think where council websites have gone wrong is they&#039;ve basically followed a steady expansion path since they were first set up 10+ plus years ago, all diligently following the lgnl at least in spirit if not in fact and become so cumbersome that they&#039;re not much use to anybody, whether pothole reporter *or* obscure policy seeker. What&#039;s needed is a complete abandonment of the one-size-one-site-fits-all mentality, and the sites being broken up. By all means, have a site dedicated to the so-called top tasks - but also have a site dedicated to the needs of business and partners, a site dedicated to the needs of families and children, a site focussed on getting around, on leisure, and of course a site dedicated to the needs of those who wish to democratically hold the council to account. And be realistic about content - what, in the modern era, would be better maintained - still by council staff - on Wikipedia rather than the council website?

Trying to tie together 9000+ pages, all with radically different content aimed at radically different audiences, is where we&#039;ve gone wrong. It&#039;s time to be more radical in our approaches to content strategy. Actually having a content strategy would be a god start for many.]]></description>
		<content:encoded><![CDATA[<p>My favourite case study in this regard is the highways services landing page, proudly declaring how many miles of roads and how many street lights it looks after. &#8220;who&#8217;s interested in that?&#8221;, the customer services obsessive asks. I can tell you who&#8217;s interested &#8211; the hundreds of kids throughout the year, all doing their school geography projects, who without that info on the website will be making hundreds of phone calls costing ten quid a pop to find out the information.</p>
<p>I think where council websites have gone wrong is they&#8217;ve basically followed a steady expansion path since they were first set up 10+ plus years ago, all diligently following the lgnl at least in spirit if not in fact and become so cumbersome that they&#8217;re not much use to anybody, whether pothole reporter *or* obscure policy seeker. What&#8217;s needed is a complete abandonment of the one-size-one-site-fits-all mentality, and the sites being broken up. By all means, have a site dedicated to the so-called top tasks &#8211; but also have a site dedicated to the needs of business and partners, a site dedicated to the needs of families and children, a site focussed on getting around, on leisure, and of course a site dedicated to the needs of those who wish to democratically hold the council to account. And be realistic about content &#8211; what, in the modern era, would be better maintained &#8211; still by council staff &#8211; on Wikipedia rather than the council website?</p>
<p>Trying to tie together 9000+ pages, all with radically different content aimed at radically different audiences, is where we&#8217;ve gone wrong. It&#8217;s time to be more radical in our approaches to content strategy. Actually having a content strategy would be a god start for many.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.prettysimple.co.uk/blog/index.php/2011/09/trimming-the-long-tail/comment-page-1/#comment-8382</link>
		<dc:creator>James</dc:creator>
		<pubDate>Wed, 14 Sep 2011 06:33:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.prettysimple.co.uk/blog/?p=1562#comment-8382</guid>
		<description><![CDATA[Thanks Gary. Yes I think it could easily be regarded as discrimination by omission (aversive disablism).]]></description>
		<content:encoded><![CDATA[<p>Thanks Gary. Yes I think it could easily be regarded as discrimination by omission (aversive disablism).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
