<?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: Wireframes vs No Wireframes</title>
	<atom:link href="http://www.johnnyjuice.com/blog/2010/02/16/wireframes-vs-no-wireframes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.johnnyjuice.com/blog/2010/02/16/wireframes-vs-no-wireframes/</link>
	<description></description>
	<lastBuildDate>Thu, 29 Sep 2011 17:06:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Andrea</title>
		<link>http://www.johnnyjuice.com/blog/2010/02/16/wireframes-vs-no-wireframes/comment-page-1/#comment-667</link>
		<dc:creator>Andrea</dc:creator>
		<pubDate>Tue, 23 Feb 2010 16:41:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnnyjuice.com/blog/?p=1039#comment-667</guid>
		<description>Hi John,

I stumbled across this post and find your take on wireframes very interesting - in a good way - more like educational. I&#039;m always interested in how people incorporate wireframes and prototypes into their processes.

Thinking back to my project management days, I can think of several clients who would have been completely lost if presented a wireframe - even with solid explanations - but I can also think of client projects that would have gone a lot more smoothly if we had presented them the wireframes to nail down functionality and structure before going into the evolution of design. Besides educating the client, I think it&#039;s also a case-by-case basis.

I do like the idea of using the wireframes internally and presenting both the wireframe and design next to each other so the client can understand the functionality and rationale behind the design. This is a method I have not yet heard of. Thanks for the new perspective!

Cheers,
Andrea</description>
		<content:encoded><![CDATA[<p>Hi John,</p>
<p>I stumbled across this post and find your take on wireframes very interesting &#8211; in a good way &#8211; more like educational. I&#8217;m always interested in how people incorporate wireframes and prototypes into their processes.</p>
<p>Thinking back to my project management days, I can think of several clients who would have been completely lost if presented a wireframe &#8211; even with solid explanations &#8211; but I can also think of client projects that would have gone a lot more smoothly if we had presented them the wireframes to nail down functionality and structure before going into the evolution of design. Besides educating the client, I think it&#8217;s also a case-by-case basis.</p>
<p>I do like the idea of using the wireframes internally and presenting both the wireframe and design next to each other so the client can understand the functionality and rationale behind the design. This is a method I have not yet heard of. Thanks for the new perspective!</p>
<p>Cheers,<br />
Andrea</p>
]]></content:encoded>
	</item>
</channel>
</rss>

