<?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>Five Sketches™ &#187; customers</title>
	<atom:link href="http://fivesketches.com/tag/customers/feed/" rel="self" type="application/rss+xml" />
	<link>http://fivesketches.com</link>
	<description>Ideation, design, and usability for development teams</description>
	<lastBuildDate>Mon, 31 Jan 2011 04:24:42 +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>Customers can&#8217;t do your job</title>
		<link>http://fivesketches.com/2008/11/customers-wont-have-the-design-answers/</link>
		<comments>http://fivesketches.com/2008/11/customers-wont-have-the-design-answers/#comments</comments>
		<pubDate>Tue, 11 Nov 2008 15:10:48 +0000</pubDate>
		<dc:creator>JeromeR</dc:creator>
				<category><![CDATA[Design, process, business]]></category>
		<category><![CDATA[customers]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[Five Sketches™]]></category>
		<category><![CDATA[software development]]></category>

		<guid isPermaLink="false">http://fivesketches.com/?p=78</guid>
		<description><![CDATA[Agile methodology can produce usable products, as long as you know what you’re doing. A common pitfall in agile is this incorrect assumption that you&#8217;ll get a usable product simply by building what the client tells you to build.
When there is some question about how to make a feature usable, customers may have something to say, but [...]]]></description>
			<content:encoded><![CDATA[<p>Agile methodology can produce usable products, as long as you know what you’re doing. A common pitfall in agile is this <span style="color: #993300;"><strong>incorrect</strong></span> assumption that you&#8217;ll get a usable product simply by building what the client tells you to build.</p>
<p>When there is some question about how to make a feature usable, customers may have something to say, but their answers are more likely based on opinion and emotion rather than on design experience and behavioural observation.</p>
<p>Brazilian blogger and computer-science- and <a href="http://www.google.com/search?q=define:HCI&amp;rls=com.microsoft:*:IE-SearchBox&amp;ie=UTF-8&amp;oe=UTF-8&amp;sourceid=ie7&amp;rlz=1I7ADBR" target="_blank">HCI</a> expert, <a href="http://blog.franktrindade.com/about/" target="_blank">Francisco Trindade</a>, gives this illustration: If you had asked people how they would like to search for Web pages in the pre-Google era, how many would have asked for a blank page with a text box on it…?</p>
<p><img style="FLOAT: right;" src="http://fivesketches.com/wp-content/uploads/2009/03/blog-whatcustomerswant.jpg" alt="Can customers design? Probably not." />Trindade says that, regardless of whether this ask-the-client behaviour is laziness or a responsibility-avoidance strategy, people who design software need to &#8221;stop pretending that the client has all the answers, and trust a little bit more in themselves to create solutions.&#8221;</p>
<p>Creating solutions? That&#8217;s a job for developers and the <a title="Read about Five Sketches™" href="http://fivesketches.com/?page_id=8">Five-Sketches™ method</a>, or any other design method they&#8217;re comfortable with.</p>
]]></content:encoded>
			<wfw:commentRss>http://fivesketches.com/2008/11/customers-wont-have-the-design-answers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

