<?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: Not so much is wrong with wireframes</title>
	<atom:link href="http://www.designitsimple.de/2010/01/not-so-much-is-wrong-with-wireframes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.designitsimple.de/2010/01/not-so-much-is-wrong-with-wireframes/</link>
	<description>if it doesn&#039;t make sense it doesn&#039;t make cents</description>
	<lastBuildDate>Wed, 21 Dec 2011 19:56:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: japatu</title>
		<link>http://www.designitsimple.de/2010/01/not-so-much-is-wrong-with-wireframes/comment-page-1/#comment-186792</link>
		<dc:creator>japatu</dc:creator>
		<pubDate>Wed, 21 Dec 2011 19:56:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.designitsimple.de/?p=92#comment-186792</guid>
		<description>I have read Christina&#039;s book and it has some valuable information contained therein - well worth a read for those who are looking for a book on web IA (chapter 11 are rules to live by.)

Moving on however, I think that wireframes are best done as a team with good communication between the BA, IA and the Designer as everyone needs to understand and interpret the brief from the client. In cases where the IA is also the designer, this is not so much a problem.

I do agree that wireframes need to take the client and context into perspective as lo-fi wireframes are not useful in all cases as clients cannot always visualise the final product. Combined with hi-fi wireframes, they might prove to be much more useful to the client. The key is to effectively communicate what you are trying to visualise to the client in whatever form that is manageable and understandable for them.

Nice follow up to http://ux4dotcom.blogspot.com/2010/01/why-and-why-not-wireframing.html</description>
		<content:encoded><![CDATA[<p>I have read Christina&#8217;s book and it has some valuable information contained therein &#8211; well worth a read for those who are looking for a book on web IA (chapter 11 are rules to live by.)</p>
<p>Moving on however, I think that wireframes are best done as a team with good communication between the BA, IA and the Designer as everyone needs to understand and interpret the brief from the client. In cases where the IA is also the designer, this is not so much a problem.</p>
<p>I do agree that wireframes need to take the client and context into perspective as lo-fi wireframes are not useful in all cases as clients cannot always visualise the final product. Combined with hi-fi wireframes, they might prove to be much more useful to the client. The key is to effectively communicate what you are trying to visualise to the client in whatever form that is manageable and understandable for them.</p>
<p>Nice follow up to <a href="http://ux4dotcom.blogspot.com/2010/01/why-and-why-not-wireframing.html" rel="nofollow">http://ux4dotcom.blogspot.com/2010/01/why-and-why-not-wireframing.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

