<?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: Balsamiq Mockups</title>
	<atom:link href="http://nebula-rnd.com/blog/tech/2009/05/balsamiq1.html/feed" rel="self" type="application/rss+xml" />
	<link>http://nebula-rnd.com/blog/tech/2009/05/balsamiq1.html</link>
	<description>Welcome to the Nebula</description>
	<lastBuildDate>Wed, 23 Jun 2010 22:19:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: JoeMayo</title>
		<link>http://nebula-rnd.com/blog/tech/2009/05/balsamiq1.html/comment-page-1#comment-325</link>
		<dc:creator>JoeMayo</dc:creator>
		<pubDate>Tue, 02 Jun 2009 18:20:35 +0000</pubDate>
		<guid isPermaLink="false">http://Nebula-RnD.com/blog/tech/2009/05/balsamiq1.html#comment-325</guid>
		<description>&lt;p&gt;Tony, You had me at &quot;alienated&quot;; I couldn&#039;t resist further&#160;reading in anticipation of the next insult. ;) I agree with Kevin&#039;s assessment.&#160; To the customer, the user interface is the application and showing them a working&#160;prototype will often give them the false impression that the project is much further along than it really is.&#160;There are some exceptions and what-ifs that can be applied (i.e. the customer is adamant about having a working prototype), but generally this&#160;is the case.&lt;/p&gt;
&lt;span lang=&quot;EN&quot;&gt;
&lt;p&gt;Sometimes customers don&#039;t want to see a mockup because they don&#039;t perceive it as real work or something they don&#039;t want to pay for. They want you to show them something they can actually use. Look at the customer&#039;s face when you show them a mockup and the difference between that and a prototype they can play with. Sometimes it doesn&#039;t matter how well you explain it or how right you are; they know they are the customer and will demand what they want. Sometimes a mockup is good and has real value, but other times, it can be perceived as a theoretical idea and won&#039;t be applicable.&lt;/p&gt;
&lt;/span&gt;
&lt;p&gt;&#160;Joe&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Tony, You had me at &quot;alienated&quot;; I couldn&#8217;t resist further&nbsp;reading in anticipation of the next insult. <img src='http://nebula-rnd.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  I agree with Kevin&#8217;s assessment.&nbsp; To the customer, the user interface is the application and showing them a working&nbsp;prototype will often give them the false impression that the project is much further along than it really is.&nbsp;There are some exceptions and what-ifs that can be applied (i.e. the customer is adamant about having a working prototype), but generally this&nbsp;is the case.</p>
<p><span lang="EN"></p>
<p>Sometimes customers don&#8217;t want to see a mockup because they don&#8217;t perceive it as real work or something they don&#8217;t want to pay for. They want you to show them something they can actually use. Look at the customer&#8217;s face when you show them a mockup and the difference between that and a prototype they can play with. Sometimes it doesn&#8217;t matter how well you explain it or how right you are; they know they are the customer and will demand what they want. Sometimes a mockup is good and has real value, but other times, it can be perceived as a theoretical idea and won&#8217;t be applicable.</p>
<p></span></p>
<p>&nbsp;Joe</p>
]]></content:encoded>
	</item>
</channel>
</rss>
