<?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: When &#8220;Useful&#8221; Features Create an Avalanche of Problems</title>
	<atom:link href="http://www.maderalabs.com/blog/when-useful-features-create-an-avalanche-of-problems/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.maderalabs.com/blog/when-useful-features-create-an-avalanche-of-problems/</link>
	<description>Experiences that rock</description>
	<lastBuildDate>Fri, 25 Jan 2013 01:14:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Tom Logue</title>
		<link>http://www.maderalabs.com/blog/when-useful-features-create-an-avalanche-of-problems/comment-page-1/#comment-704</link>
		<dc:creator>Tom Logue</dc:creator>
		<pubDate>Tue, 24 Apr 2012 17:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.maderalabs.com/?p=1124#comment-704</guid>
		<description>Great advice! Often in development the focus is on what *can* be done rather than what *should* be done. You need a user advocate at the table who understands the big picture of how people use the software. Talk to users early and often, without preconceived notions of how things work, and you&#039;ll end up with a stronger design and feature set. That&#039;s not saying that users&#039; feedback should always be followed -- just that it should frequently be sought.</description>
		<content:encoded><![CDATA[<p>Great advice! Often in development the focus is on what *can* be done rather than what *should* be done. You need a user advocate at the table who understands the big picture of how people use the software. Talk to users early and often, without preconceived notions of how things work, and you&#8217;ll end up with a stronger design and feature set. That&#8217;s not saying that users&#8217; feedback should always be followed &#8212; just that it should frequently be sought.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
