<?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: Design Last Design</title>
	<atom:link href="http://www.designinginteractive.com/design/design-last-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.designinginteractive.com/design/design-last-design/</link>
	<description>Usable Web Applications with Web Standards</description>
	<lastBuildDate>Tue, 27 Jul 2010 20:50:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Josh Walsh</title>
		<link>http://www.designinginteractive.com/design/design-last-design/comment-page-1/#comment-1096</link>
		<dc:creator>Josh Walsh</dc:creator>
		<pubDate>Sat, 16 Jan 2010 21:20:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=832#comment-1096</guid>
		<description>Matt. - I&#039;m really interested to talk to you some more about this.  We&#039;ve had awesome success with it so far.</description>
		<content:encoded><![CDATA[<p>Matt. &#8211; I&#8217;m really interested to talk to you some more about this.  We&#8217;ve had awesome success with it so far.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Becker</title>
		<link>http://www.designinginteractive.com/design/design-last-design/comment-page-1/#comment-1095</link>
		<dc:creator>Matt Becker</dc:creator>
		<pubDate>Fri, 15 Jan 2010 20:56:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=832#comment-1095</guid>
		<description>Awesome. Awesome. I love hearing other folks using this method and having it work well for them. I&#039;ve taken the same approach with great success – giving clients grayboxes to start out with and design around the site&#039;s content, gather feedback and work on its structure and layout. It also aids my process of doing more information designing in the browser, which helps cut down on the time making adjustments later.

I&#039;m amazed you were able to keep this so short, because I could go on about the benefits of this method forever. And probably will, now that I think about it.

Great article, Josh. =)</description>
		<content:encoded><![CDATA[<p>Awesome. Awesome. I love hearing other folks using this method and having it work well for them. I&#8217;ve taken the same approach with great success – giving clients grayboxes to start out with and design around the site&#8217;s content, gather feedback and work on its structure and layout. It also aids my process of doing more information designing in the browser, which helps cut down on the time making adjustments later.</p>
<p>I&#8217;m amazed you were able to keep this so short, because I could go on about the benefits of this method forever. And probably will, now that I think about it.</p>
<p>Great article, Josh. =)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny</title>
		<link>http://www.designinginteractive.com/design/design-last-design/comment-page-1/#comment-1074</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Tue, 12 Jan 2010 19:14:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=832#comment-1074</guid>
		<description>Although I confess that I am the first to let the client dictate the process (often a huge mistake), I really like the &quot;Design Last&quot; model. Old habits die hard, but this one might be the resolution I was looking for this year. Thanks Josh! :)</description>
		<content:encoded><![CDATA[<p>Although I confess that I am the first to let the client dictate the process (often a huge mistake), I really like the &#8220;Design Last&#8221; model. Old habits die hard, but this one might be the resolution I was looking for this year. Thanks Josh! <img src='http://www.designinginteractive.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Walsh</title>
		<link>http://www.designinginteractive.com/design/design-last-design/comment-page-1/#comment-1062</link>
		<dc:creator>Josh Walsh</dc:creator>
		<pubDate>Mon, 11 Jan 2010 03:10:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=832#comment-1062</guid>
		<description>Joe - Yes, I&#039;ve read that article and really enjoyed it.

The main difference here is that my whole user interface stays lo-fi until the end of the project rather than just in the planning stages.  While you can get some great feedback from lo-fi wireframes in the beginning, the best feedback comes from interacting with the real mccoy.  By staying lo-fi through the initial build, we can use that feedback to make changes inexpensively.

Thanks for the comment.</description>
		<content:encoded><![CDATA[<p>Joe &#8211; Yes, I&#8217;ve read that article and really enjoyed it.</p>
<p>The main difference here is that my whole user interface stays lo-fi until the end of the project rather than just in the planning stages.  While you can get some great feedback from lo-fi wireframes in the beginning, the best feedback comes from interacting with the real mccoy.  By staying lo-fi through the initial build, we can use that feedback to make changes inexpensively.</p>
<p>Thanks for the comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Fiorini</title>
		<link>http://www.designinginteractive.com/design/design-last-design/comment-page-1/#comment-1060</link>
		<dc:creator>Joe Fiorini</dc:creator>
		<pubDate>Sat, 09 Jan 2010 18:12:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=832#comment-1060</guid>
		<description>Interesting method. I highly recommend Jeff Patton&#039;s &quot;Twelve emerging best practices for adding UX work to Agile development&quot; (http://www.agileproductdesign.com/blog/emerging_best_agile_ux_practice.html)for further reading. It&#039;s somewhat similar in that the pattern he&#039;s noticed is having low-fi mockups for as long as possible before producing something final.</description>
		<content:encoded><![CDATA[<p>Interesting method. I highly recommend Jeff Patton&#8217;s &#8220;Twelve emerging best practices for adding UX work to Agile development&#8221; (<a href="http://www.agileproductdesign.com/blog/emerging_best_agile_ux_practice.html)for" rel="nofollow">http://www.agileproductdesign.com/blog/emerging_best_agile_ux_practice.html)for</a> further reading. It&#8217;s somewhat similar in that the pattern he&#8217;s noticed is having low-fi mockups for as long as possible before producing something final.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Goerlich</title>
		<link>http://www.designinginteractive.com/design/design-last-design/comment-page-1/#comment-1059</link>
		<dc:creator>Dave Goerlich</dc:creator>
		<pubDate>Wed, 06 Jan 2010 21:17:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=832#comment-1059</guid>
		<description>I&#039;ve seen first hand how effective this is.  Meetings with the client remain focused on the interface and the underlying business process, rather than getting bogged down discussing the merits of #3366ff versus #3366fe.  Even internally I&#039;ve seen us remain much more focused on the core of the application.  In the end, I&#039;m confident this is going to be a very successful experiment!</description>
		<content:encoded><![CDATA[<p>I&#8217;ve seen first hand how effective this is.  Meetings with the client remain focused on the interface and the underlying business process, rather than getting bogged down discussing the merits of #3366ff versus #3366fe.  Even internally I&#8217;ve seen us remain much more focused on the core of the application.  In the end, I&#8217;m confident this is going to be a very successful experiment!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
