<?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: 14 quotes and explanations</title>
	<atom:link href="http://webusability-blog.com/14-quotes-and-explanations/feed/" rel="self" type="application/rss+xml" />
	<link>http://webusability-blog.com/14-quotes-and-explanations/</link>
	<description>Tips, insights and meandering thoughts about usability and information architecture</description>
	<lastBuildDate>Tue, 13 Dec 2011 15:34:27 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tristan Naramore</title>
		<link>http://webusability-blog.com/14-quotes-and-explanations/comment-page-1/#comment-2477</link>
		<dc:creator>Tristan Naramore</dc:creator>
		<pubDate>Mon, 11 Jan 2010 17:21:08 +0000</pubDate>
		<guid isPermaLink="false">http://webusability-blog.com/?p=222#comment-2477</guid>
		<description>There&#039;s a point in EVERY project with any type of customer where issues like these crop up. As a professional consultant, I must make a call between making my client happy  and sleeping well at night knowing I&#039;ve stuck to my principles. 

When these kind of comments come up (especially coming from those in positions of authority), I usually &lt;em&gt;gently&lt;/em&gt; push back by asking probing questions, in order to understand the situation and the underlying (often hidden) assumptions. Sometimes, this leads to a-ha! moments. Sometimes, I just need to back down and swallow my professional pride (&quot;aren&#039;t they paying me to be the usability expert here?!&quot;).</description>
		<content:encoded><![CDATA[<p>There&#8217;s a point in EVERY project with any type of customer where issues like these crop up. As a professional consultant, I must make a call between making my client happy  and sleeping well at night knowing I&#8217;ve stuck to my principles. </p>
<p>When these kind of comments come up (especially coming from those in positions of authority), I usually <em>gently</em> push back by asking probing questions, in order to understand the situation and the underlying (often hidden) assumptions. Sometimes, this leads to a-ha! moments. Sometimes, I just need to back down and swallow my professional pride (&#8221;aren&#8217;t they paying me to be the usability expert here?!&#8221;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Els Aerts</title>
		<link>http://webusability-blog.com/14-quotes-and-explanations/comment-page-1/#comment-1326</link>
		<dc:creator>Els Aerts</dc:creator>
		<pubDate>Thu, 22 Oct 2009 15:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://webusability-blog.com/?p=222#comment-1326</guid>
		<description>@Scott: Never heard that one myself, but hey, there&#039;s a first time for everything. I&#039;m sure they can come up with even weirder stuff. :)</description>
		<content:encoded><![CDATA[<p>@Scott: Never heard that one myself, but hey, there&#8217;s a first time for everything. I&#8217;m sure they can come up with even weirder stuff. <img src='http://webusability-blog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Dugger</title>
		<link>http://webusability-blog.com/14-quotes-and-explanations/comment-page-1/#comment-1323</link>
		<dc:creator>Scott Dugger</dc:creator>
		<pubDate>Thu, 22 Oct 2009 12:34:16 +0000</pubDate>
		<guid isPermaLink="false">http://webusability-blog.com/?p=222#comment-1323</guid>
		<description>One we just got slapped in the face with recently:  &quot;It&#039;s too risky.&quot;
?? What??</description>
		<content:encoded><![CDATA[<p>One we just got slapped in the face with recently:  &#8220;It&#8217;s too risky.&#8221;<br />
?? What??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan Dermaut</title>
		<link>http://webusability-blog.com/14-quotes-and-explanations/comment-page-1/#comment-19</link>
		<dc:creator>Johan Dermaut</dc:creator>
		<pubDate>Mon, 08 Jun 2009 07:22:19 +0000</pubDate>
		<guid isPermaLink="false">http://webusability-blog.com/?p=222#comment-19</guid>
		<description>Hello,

Here are some more.

Why do you want a new website? 
- Because the competition has a new one.
- Because we have a new manager and (s)he doesn&#039;t like the one we have now. 

Interactivity is very important to us. 
So, you will have a forum on your website? No way, people could post links to &quot;those special&quot; websites. 

New technologies are very important to us. 
So, you will encourage twittering, blogging and the like? No, because the boss thinks that is a waste of time and bad for the image of the company. 

Content is very important.
So, do you adapt the texts from your brochures, press releases and other info the public reads for your website where people rather scan than read? No, we do not have the time nor the man power to do that. 

Another problem is that a lot of people talk about &quot;the customer&quot;. The customer thinks ..., the customer wants ..., the customer would like to .... &quot;The customer&quot; doesn&#039;t exist, that is why you develop personas. 

Some decisions unfortunately are based on personal stories. 
A feature is implemented or not because someone&#039;s mother-in-law, brother, friend or colleague had a bad or good experience somewhere on the Web. Because ONE person had a good or bad story to tell, a feature is sometimes not implemented. 

Sales are important. 
We do not put contact information on the website because people might contact us with their technical questions and problems. 

...

Johan</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>Here are some more.</p>
<p>Why do you want a new website?<br />
- Because the competition has a new one.<br />
- Because we have a new manager and (s)he doesn&#8217;t like the one we have now. </p>
<p>Interactivity is very important to us.<br />
So, you will have a forum on your website? No way, people could post links to &#8220;those special&#8221; websites. </p>
<p>New technologies are very important to us.<br />
So, you will encourage twittering, blogging and the like? No, because the boss thinks that is a waste of time and bad for the image of the company. </p>
<p>Content is very important.<br />
So, do you adapt the texts from your brochures, press releases and other info the public reads for your website where people rather scan than read? No, we do not have the time nor the man power to do that. </p>
<p>Another problem is that a lot of people talk about &#8220;the customer&#8221;. The customer thinks &#8230;, the customer wants &#8230;, the customer would like to &#8230;. &#8220;The customer&#8221; doesn&#8217;t exist, that is why you develop personas. </p>
<p>Some decisions unfortunately are based on personal stories.<br />
A feature is implemented or not because someone&#8217;s mother-in-law, brother, friend or colleague had a bad or good experience somewhere on the Web. Because ONE person had a good or bad story to tell, a feature is sometimes not implemented. </p>
<p>Sales are important.<br />
We do not put contact information on the website because people might contact us with their technical questions and problems. </p>
<p>&#8230;</p>
<p>Johan</p>
]]></content:encoded>
	</item>
</channel>
</rss>

