<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Michael Beasley &#187; Website Usability</title>
	<atom:link href="http://www.michael-beasley.net/blog/category/website-usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.michael-beasley.net/blog</link>
	<description>Usability and user experience thoughts and tips and intepretation of the world.</description>
	<lastBuildDate>Tue, 02 Mar 2010 00:43:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Websites are Still Hard to Use</title>
		<link>http://www.michael-beasley.net/blog/2010/02/websites-are-still-hard-to-use/</link>
		<comments>http://www.michael-beasley.net/blog/2010/02/websites-are-still-hard-to-use/#comments</comments>
		<pubDate>Tue, 09 Feb 2010 00:03:07 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[Website Usability]]></category>

		<guid isPermaLink="false">http://www.michael-beasley.net/blog/?p=21</guid>
		<description><![CDATA[It&#8217;s hard to believe, but even today there are still a lot of sites out there that are hard to use.
I find myself falling into the trap of thinking that designing a standard, informational website is a &#8220;solved&#8221; problem. You put a main navigation on the site, fill it with labels that capture the things [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s hard to believe, but even today there are still a lot of sites out there that are hard to use.</p>
<p>I find myself falling into the trap of thinking that designing a standard, informational website is a &#8220;solved&#8221; problem. You put a main navigation on the site, fill it with labels that capture the things that you can offer people, add in an &#8220;About Us&#8221; and a &#8220;Contact Us&#8221; section, and you&#8217;re good. Don&#8217;t use hard-to-read color combinations. Don&#8217;t bury important information. Get to the point. Or, to put it in a really boring and worn-out way, usability professionals aren&#8217;t going to find this &#8220;low-hanging fruit&#8221; anymore.</p>
<p>That just isn&#8217;t the case, from small mom-and-pop businesses to huge national brands.</p>
<p>Although I spend a lot of my time thinking about incremental improvements to sites, there are unfortunately still plenty of chances to make bold leaps in site performance. These are the situations that often allow usability professionals to put on the business analyst &#8220;hat&#8221; (which is pretty much the same as the &#8220;business therapist hat&#8221;). Sites that are confusing down to their core are probably the product of people that aren&#8217;t sure of the purpose of their site&#8230; at least, putting those goals into specific and explicit terms.</p>
<p>A down side of these situations is that you may end up coming back with recommendations for improving the site that amount to &#8220;scrap this site and make a new one.&#8221; How do you make tactical improvements to a site that&#8217;s got foundational problems?</p>
<p>I don&#8217;t have a good answer for that, because I think every situation is different. It comes down to managing expectations and negotiation, though. Redesign may be out of scope for a project, but it doesn&#8217;t me<a href="http://www.michael-beasley.net/blog/wp-admin/post-new.php#edit_timestamp">OK</a>an that you can&#8217;t raise the issue. And what can you focus on in the meantime to improve the site that is currently there?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.michael-beasley.net/blog/2010/02/websites-are-still-hard-to-use/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
