<?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: What is this site for?</title>
	<atom:link href="http://www.goodusability.co.uk/2009/02/what-is-this-site-for/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.goodusability.co.uk/2009/02/what-is-this-site-for/</link>
	<description></description>
	<lastBuildDate>Wed, 28 Jul 2010 11:54:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Monday February 9th Roundup &#124; Webbyn.com</title>
		<link>http://www.goodusability.co.uk/2009/02/what-is-this-site-for/comment-page-1/#comment-169</link>
		<dc:creator>Monday February 9th Roundup &#124; Webbyn.com</dc:creator>
		<pubDate>Wed, 11 Feb 2009 03:38:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=593#comment-169</guid>
		<description>[...] Usability has some good advice for all you webdev&#8217;s out there: tell your visitors what your website does. This should really be a no-brainer. However, I do think its worth noting that telling someone != [...]</description>
		<content:encoded><![CDATA[<p>[...] Usability has some good advice for all you webdev&#8217;s out there: tell your visitors what your website does. This should really be a no-brainer. However, I do think its worth noting that telling someone != [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hamill</title>
		<link>http://www.goodusability.co.uk/2009/02/what-is-this-site-for/comment-page-1/#comment-159</link>
		<dc:creator>David Hamill</dc:creator>
		<pubDate>Thu, 05 Feb 2009 19:58:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=593#comment-159</guid>
		<description>Hi John, consider the user who has clicked one of your Adwords links. They may have run a search on a particular service and landed at your homepage. They will arrive with questions that need to be answered pretty quickly. The first is likely to be &quot;OK, what do these guys do?&quot;. That&#039;s your proposition.

The fact that you&#039;ve listed your services from your homepage explains your proposition.

You could apply a little more visual focus to this list and make them links to more information.

I would also recommend saying &quot;you&quot; more than &quot;we&quot;. Focus on the benefit you can give to the reader. That&#039;s what they&#039;re interested in.</description>
		<content:encoded><![CDATA[<p>Hi John, consider the user who has clicked one of your Adwords links. They may have run a search on a particular service and landed at your homepage. They will arrive with questions that need to be answered pretty quickly. The first is likely to be &#8220;OK, what do these guys do?&#8221;. That&#8217;s your proposition.</p>
<p>The fact that you&#8217;ve listed your services from your homepage explains your proposition.</p>
<p>You could apply a little more visual focus to this list and make them links to more information.</p>
<p>I would also recommend saying &#8220;you&#8221; more than &#8220;we&#8221;. Focus on the benefit you can give to the reader. That&#8217;s what they&#8217;re interested in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Clark</title>
		<link>http://www.goodusability.co.uk/2009/02/what-is-this-site-for/comment-page-1/#comment-155</link>
		<dc:creator>John Clark</dc:creator>
		<pubDate>Thu, 05 Feb 2009 07:20:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=593#comment-155</guid>
		<description>Interesting stuff.  The point I&#039;d like to make here is that the websites you mention are very specific in their intention.  Take iPlayer - it is there for catching up on broadcast TV using your computer.  Very clear objective, from a user&#039;s perspective.  However, many sites may offer multiple services, or even exist for purely informational purposes.  My company&#039;s site is one - www.reynardthomson.com - no tag-line (but maybe this would help - food for thought?) but a more complex proposition which isn&#039;t really intended for the casual browser.  If you&#039;re coming to my company&#039;s site, you&#039;re visiting because you probably have an interest in some of the services, or perhaps you&#039;ve just chanced across it via an AdWords link or somesuch.  

So, tag-line&#039;s aside, it&#039;s our duty as developers to make sites intuitively easy to navigate, exploiting good design, avoiding padding and technological lock-in* and trying to get the message across in the best way possible...

* one trick I like is to see how easy it is to navigate my site using a text-only browser - Lynx springs to mind.  If you&#039;ve avoided &#039;lock-in&#039; AJAX and flash and so on, you ought to be ok, but it&#039;s surprising how many sites just won&#039;t work.  And if they won&#039;t work for Lynx, they likely won&#039;t work for Jaws or other assistive web readers, and may even (heaven forbid) get the Googlebot in a fangle...</description>
		<content:encoded><![CDATA[<p>Interesting stuff.  The point I&#8217;d like to make here is that the websites you mention are very specific in their intention.  Take iPlayer &#8211; it is there for catching up on broadcast TV using your computer.  Very clear objective, from a user&#8217;s perspective.  However, many sites may offer multiple services, or even exist for purely informational purposes.  My company&#8217;s site is one &#8211; <a href="http://www.reynardthomson.com">http://www.reynardthomson.com</a> &#8211; no tag-line (but maybe this would help &#8211; food for thought?) but a more complex proposition which isn&#8217;t really intended for the casual browser.  If you&#8217;re coming to my company&#8217;s site, you&#8217;re visiting because you probably have an interest in some of the services, or perhaps you&#8217;ve just chanced across it via an AdWords link or somesuch.  </p>
<p>So, tag-line&#8217;s aside, it&#8217;s our duty as developers to make sites intuitively easy to navigate, exploiting good design, avoiding padding and technological lock-in* and trying to get the message across in the best way possible&#8230;</p>
<p>* one trick I like is to see how easy it is to navigate my site using a text-only browser &#8211; Lynx springs to mind.  If you&#8217;ve avoided &#8216;lock-in&#8217; AJAX and flash and so on, you ought to be ok, but it&#8217;s surprising how many sites just won&#8217;t work.  And if they won&#8217;t work for Lynx, they likely won&#8217;t work for Jaws or other assistive web readers, and may even (heaven forbid) get the Googlebot in a fangle&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Thompson</title>
		<link>http://www.goodusability.co.uk/2009/02/what-is-this-site-for/comment-page-1/#comment-150</link>
		<dc:creator>Phil Thompson</dc:creator>
		<pubDate>Wed, 04 Feb 2009 10:15:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=593#comment-150</guid>
		<description>It would seem that far too few people are experimental in nature and consequently the first reaction when coming across a new website that they don&#039;t &#039;get&#039; is to leave it straightaway and not to click around thus finding out what it&#039;s all about. 

This is pretty much common sense, as it happens in shops/restaurants and probably elsewhere too.

Take for instance, the restaurant Nando&#039;s; this place has waiting staff but bucks trend by expecting you to order at the bar and grab your own plates/cutlery/drinks. This works out well because they explain it to you when you first come in. However, last week I was there and the waiting staff didn&#039;t explain it to us - no problem for us as I&#039;ve been there before, but the couple next to us sat there looking perplexed for ten minutes and eventually left because they had no idea what to do. They clearly didn&#039;t ask for fear of looking stupid.

The morale to the story: a little explanation goes a long way.</description>
		<content:encoded><![CDATA[<p>It would seem that far too few people are experimental in nature and consequently the first reaction when coming across a new website that they don&#8217;t &#8216;get&#8217; is to leave it straightaway and not to click around thus finding out what it&#8217;s all about. </p>
<p>This is pretty much common sense, as it happens in shops/restaurants and probably elsewhere too.</p>
<p>Take for instance, the restaurant Nando&#8217;s; this place has waiting staff but bucks trend by expecting you to order at the bar and grab your own plates/cutlery/drinks. This works out well because they explain it to you when you first come in. However, last week I was there and the waiting staff didn&#8217;t explain it to us &#8211; no problem for us as I&#8217;ve been there before, but the couple next to us sat there looking perplexed for ten minutes and eventually left because they had no idea what to do. They clearly didn&#8217;t ask for fear of looking stupid.</p>
<p>The morale to the story: a little explanation goes a long way.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
