<?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: 4 product comparison best practices</title>
	<atom:link href="http://webusability-blog.com/4-product-comparison-best-practices/feed/" rel="self" type="application/rss+xml" />
	<link>http://webusability-blog.com/4-product-comparison-best-practices/</link>
	<description>Tips, insights and meandering thoughts about usability and information architecture</description>
	<lastBuildDate>Wed, 01 Sep 2010 19:25:26 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Product overview: do’s and don’ts &#124; Uxable</title>
		<link>http://webusability-blog.com/4-product-comparison-best-practices/comment-page-1/#comment-5523</link>
		<dc:creator>Product overview: do’s and don’ts &#124; Uxable</dc:creator>
		<pubDate>Fri, 25 Jun 2010 21:33:28 +0000</pubDate>
		<guid isPermaLink="false">http://webusability-blog.com/?p=723#comment-5523</guid>
		<description>[...] Product comparison: a must-have If you’re offering 2 or more similar products or services, people should be able to compare them easily. It’s the vendor’s job to help people pick the product that suits their needs best. That’s what people expect, offline as well as online. We’ve written about this before in ‘4 product comparison best practices’. [...]</description>
		<content:encoded><![CDATA[<p>[...] Product comparison: a must-have If you’re offering 2 or more similar products or services, people should be able to compare them easily. It’s the vendor’s job to help people pick the product that suits their needs best. That’s what people expect, offline as well as online. We’ve written about this before in ‘4 product comparison best practices’. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
