<?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: So you want to prototype?</title>
	<atom:link href="http://www.jeremyjohnsononline.com/2009/02/24/so-you-want-to-prototype/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jeremyjohnsononline.com/2009/02/24/so-you-want-to-prototype/</link>
	<description>Jeremy Johnson writes about User Experience, Design, technology, mobile, and all things the Internet. He also enjoys art, photography, travel, and gaming. This is his home on the Internet.</description>
	<lastBuildDate>Sun, 15 Jan 2012 22:29:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Rustem</title>
		<link>http://www.jeremyjohnsononline.com/2009/02/24/so-you-want-to-prototype/comment-page-1/#comment-74590</link>
		<dc:creator>Rustem</dc:creator>
		<pubDate>Mon, 13 Dec 2010 07:28:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremyjohnsononline.com/?p=86#comment-74590</guid>
		<description>Interesting review, thanks!
Can you add GUI Machine (http://www.gui-machine.com) - new powerful prototyping tool for desktop and web applications - into your list, please?</description>
		<content:encoded><![CDATA[<p>Interesting review, thanks!<br />
Can you add GUI Machine (<a href="http://www.gui-machine.com" rel="nofollow">http://www.gui-machine.com</a>) &#8211; new powerful prototyping tool for desktop and web applications &#8211; into your list, please?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Smith</title>
		<link>http://www.jeremyjohnsononline.com/2009/02/24/so-you-want-to-prototype/comment-page-1/#comment-47359</link>
		<dc:creator>Dan Smith</dc:creator>
		<pubDate>Wed, 29 Apr 2009 12:33:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremyjohnsononline.com/?p=86#comment-47359</guid>
		<description>Good post, I&#039;d like to add ForeUI to your tool list.  The most interesting thing is that it allow switching the look and feel of the prototype, the prototype with native look and feel is more suitable to be used in design documents.</description>
		<content:encoded><![CDATA[<p>Good post, I&#8217;d like to add ForeUI to your tool list.  The most interesting thing is that it allow switching the look and feel of the prototype, the prototype with native look and feel is more suitable to be used in design documents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paula Thornton</title>
		<link>http://www.jeremyjohnsononline.com/2009/02/24/so-you-want-to-prototype/comment-page-1/#comment-42364</link>
		<dc:creator>Paula Thornton</dc:creator>
		<pubDate>Wed, 25 Feb 2009 16:09:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremyjohnsononline.com/?p=86#comment-42364</guid>
		<description>Prototyping is a means to an end. The problem lies in its being the &#039;focus&#039; towards that end.

It is simply one element in a larger Design Thinking realm, a means by which to illustrate the possibilities. In the frame of this larger construct, it is more clear how far to take &#039;prototype&#039; -- typically through successive means.

One of the failures I see among practitioners is the inability to effectively weigh the value of the results to the effort. FAR too often colleagues go down a prototype path by &#039;rote&#039;, investing far too much time where the real potential return is not that great.

As practitioners we either need to take direction from others who understand this difference (which is also lacking) or learn the differences ourselves.

Hint: Practitioners who are best at this typically have a business degree and/or have studied economics.</description>
		<content:encoded><![CDATA[<p>Prototyping is a means to an end. The problem lies in its being the &#8216;focus&#8217; towards that end.</p>
<p>It is simply one element in a larger Design Thinking realm, a means by which to illustrate the possibilities. In the frame of this larger construct, it is more clear how far to take &#8216;prototype&#8217; &#8212; typically through successive means.</p>
<p>One of the failures I see among practitioners is the inability to effectively weigh the value of the results to the effort. FAR too often colleagues go down a prototype path by &#8216;rote&#8217;, investing far too much time where the real potential return is not that great.</p>
<p>As practitioners we either need to take direction from others who understand this difference (which is also lacking) or learn the differences ourselves.</p>
<p>Hint: Practitioners who are best at this typically have a business degree and/or have studied economics.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck Konfrst</title>
		<link>http://www.jeremyjohnsononline.com/2009/02/24/so-you-want-to-prototype/comment-page-1/#comment-42350</link>
		<dc:creator>Chuck Konfrst</dc:creator>
		<pubDate>Wed, 25 Feb 2009 13:20:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremyjohnsononline.com/?p=86#comment-42350</guid>
		<description>Great post.  I think one thing to keep in mind is that the tools you mention are really great for visualization.  By that I mean visualization helps the business focus and define their needs, desires and requirements without needing any development resources.   Expensive and busy developers can be involved in other projects while the business is still getting its act together.  In large organizations this is very valuable.

As for fidelity, I&#039;ve used tools like iRise to create extremely high-fidelity visualizations that looks, feels, functions and smells like the real thing.  I routinely use the high-fidelity visualizations to prove requirements, test concepts, and conduct usability activities.</description>
		<content:encoded><![CDATA[<p>Great post.  I think one thing to keep in mind is that the tools you mention are really great for visualization.  By that I mean visualization helps the business focus and define their needs, desires and requirements without needing any development resources.   Expensive and busy developers can be involved in other projects while the business is still getting its act together.  In large organizations this is very valuable.</p>
<p>As for fidelity, I&#8217;ve used tools like iRise to create extremely high-fidelity visualizations that looks, feels, functions and smells like the real thing.  I routinely use the high-fidelity visualizations to prove requirements, test concepts, and conduct usability activities.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark vernon</title>
		<link>http://www.jeremyjohnsononline.com/2009/02/24/so-you-want-to-prototype/comment-page-1/#comment-42295</link>
		<dc:creator>mark vernon</dc:creator>
		<pubDate>Wed, 25 Feb 2009 02:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremyjohnsononline.com/?p=86#comment-42295</guid>
		<description>Please can you add iplotz.com into the list of online and offline tools for wireframing and mockups.
thanks
mark</description>
		<content:encoded><![CDATA[<p>Please can you add iplotz.com into the list of online and offline tools for wireframing and mockups.<br />
thanks<br />
mark</p>
]]></content:encoded>
	</item>
</channel>
</rss>

